Repository navigation
交付群 invite join stuck on Asked to join… — host never seats, no sidebar row (regression after #1082) #1161
Description
Problem
On production FlyBot (c0a3369, social.botawaken.com Bot Social 7a07e1bb), inviting someone into the 交付群 local group via invite link still leaves the joiner stuck:
- Joiner UI stays on Asked to join… / waiting for the host to seat Bots
- Joiner gets no sidebar row for the group
- Host never appears to seat the joiner's Bots
Owner confirmed the stuck step explicitly (2026-10-25 Asia/Shanghai): "Join stuck waiting / no sidebar row" for FlyBot 交付群.
Why this is not just #1064
#1064 described the same symptoms and was closed by #1082 ("Seat a room-link claim without waiting for the knock"). That fix is already in the running prod tip c0a3369 (1082 ≪ c0a3369). The defect is still live on that build for 交付群, so treat this as a regression / incomplete seating path, not a stale-build report.
Steps to reproduce
- On home A (owner of 交付群), open the group → Members / Invite by link → copy
https://social.botawaken.com/r/…. - On home B (invitee), paste/open the link and click Join group (or the join entry that claims the ticket).
- Watch both sides for ~30s+.
Actual
- B remains on Asked to join / waiting copy; group does not appear in B's sidebar.
- A does not seat B's Bots into 交付群.
Expected
- Claim seats B's Bots on A without waiting on a knock that never arrives (the Seat a room-link claim without waiting for the knock #1082 intent).
- B gets a sidebar row and can open the group.
- Clear pending / success / failure feedback (adjacent: Improve the group-link join entry and show feedback when Join group is clicked #1021).
Environment
- Prod FlyBot u-* + canary:
c0a33696740e29a6b8e3fb43ae9b7e9ec364599e - Bot Social:
7a07e1bb1825a16d8cdb27a24becdec872ea1ba9 - Group: 交付群 (local room with invite link)
Related
- Join group stuck on "Asked to join…": host never seats Bots, joiner gets no sidebar row #1064 (closed via Seat a room-link claim without waiting for the knock #1082) — same UI symptom; reopen-as-new because fix is already deployed
- Improve the group-link join entry and show feedback when Join group is clicked #1021 — join entry / click feedback (open)
- A local-room invite link cannot be redeemed by a home that cannot already reach the inviter (cross-repo: claim + connector exception) #853 / assertAddable refuses a remote Bot that a verified ticket admitted, so the invited stranger is seated nowhere #884 / One local-room ticket admits one Bot: a friend and their Bot need two links, and minting a second link kills the first #878 — earlier invite-link seating work (closed)
- Group chat keeps asking Approve for Group update to a friend's Bot #1113 / Clear ordinary group lines once pair Auto-send is on #1117 — Group update approval loops (merged; check whether seating still blocks on an outbound share approval)
Acceptance
- Reproduce (or explain why 交付群 differs) on current main / tip ≥ c0a3369.
- Joiner claim results in host seating without an indefinitely stuck "Asked to join…" state.
- Joiner sidebar shows the room after a successful seat.
- Automated coverage for the failing branch (claim → seat without knock, and the failure that currently leaves "Asked to join…" forever).
- Do not weaken invite / membership / authorization checks.
Activity
Birfy commentedon Oct 25, 2026
Written-by: Dev
Claiming. Branch will be on the PR from the implementer agent.
Repro confirmed by owner on prod tip
c0a3369for 交付群: joiner stuck on Asked to join… / no sidebar row after #1082 already shipped. Investigating seatOpenClaims poll + claim seating path (and whether Bot Social claim listing still feeds the host).Birfy commentedon Oct 25, 2026
Written-by: Dev
Reproduced on box joiner FlyBot
:3091against prod Social, using the owner-provided live link:https://social.botawaken.com/r/@chief.flybot682b8a43.home/AwWkxg8zt7fPMgLSt3Wj1w@chief.flybot682b8a43.homeJoining with that link…→Asked to join "FlyBot 交付组". It opens in your sidebar as soon as their FlyBot seats your Bots.c0a3369already includes Seat a room-link claim without waiting for the knock #1082)Next: host-side
seatOpenClaims/ claim poll onu-682b8a*+ implementer PR for #1161.Birfy commentedon Oct 25, 2026
Written-by: Dev
Host-side evidence (prod u-682b8a4383474b7a9b26433e5b66a8bc, read-only)
Last ~60 minutes (UTC 10:21–11:17 / Asia/Shanghai 18:21–19:17):
[ds-bot] a room link claim was not read: Too many attempts. Try again in 10 minutes.face-rooms.jspreview/callHttp→seatOpenClaims(room-membership.js~1842) →@flybot/socialpollOnceAwWkxg8zt7fPMgLSt3Wj1w/FLYBOT-ROOM-SHARE: 0 hits in u-682 or bot-social logs in that window (claim never successfully read)room share not sent to @chief.flybot98b8ecba.home: Bot Social send_as_member: payload.text (1-4000 chars) requiredviasendTicketShare←sendShareTo(Asia/Shanghai 18:51)Fix direction for implementer
Too many attempts), back offseatOpenClaims(honor Retry-After / 10 min) instead of polling every inbox tick.payload.textonsendTicketShare/sendShareToso a seat knock is not dropped for missing text.Joiner repro on the live link remains as in the prior comment.
Honor the 10-minute claim-read cool-down and fit every room share
Seat an invite-link claim the host poll could no longer read (ThinkFl…