Skip to content

feat(mobile): browse and join open channels - #6145

Closed
square-tomb wants to merge 4 commits into
mainfrom
tomb/buzz-13-browse-and-join-channels-in-mobile
Closed

feat(mobile): browse and join open channels#6145
square-tomb wants to merge 4 commits into
mainfrom
tomb/buzz-13-browse-and-join-channels-in-mobile

Conversation

@square-tomb

@square-tomb square-tomb commented Aug 17, 2026

Copy link
Copy Markdown
Contributor

Mobile previously exposed no way to browse or join channels.

Users can now browse and join eligible open channels from the Home quick-actions menu. The existing kind 9021 join path refreshes membership after success.

Browse channels Join channel
Browse channels Join channel

How is it tested?

Manually tested (see screenshots) and added tests:

  • channels_provider_test.dart covers directory discovery, access filtering, membership integrity, pagination, repeated-page termination, and the hard page cap.
  • channels_page_test.dart covers browse eligibility, no-discoverable-channel copy, quick-action layout, and joining from the browse sheet.

Signed-off-by: Tom Brow <tomb@block.xyz>
Co-authored-by: Codex <noreply@openai.com>
Ai-assisted: true

Copy link
Copy Markdown
Contributor Author

@builderbot review

Copy link
Copy Markdown
Contributor Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: d2b414627c

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread mobile/lib/features/channels/channels_provider.dart Outdated
Comment thread mobile/lib/features/channels/channels_page/browse_channels_sheet.dart Outdated
Comment thread mobile/lib/features/channels/channels_provider.dart Outdated
Signed-off-by: Tom Brow <tomb@block.xyz>
Co-authored-by: Codex <noreply@openai.com>
Ai-assisted: true
@brow
brow marked this pull request as ready for review August 17, 2026 19:32
@brow
brow requested a review from a team as a code owner August 17, 2026 19:32
brow and others added 2 commits August 18, 2026 09:34
Signed-off-by: Tom Brow <tomb@block.xyz>
Signed-off-by: Tom Brow <tomb@block.xyz>
Co-authored-by: Codex <noreply@openai.com>
Ai-assisted: true
@brow brow closed this Aug 18, 2026
@brow brow reopened this Aug 18, 2026
@brow
brow requested a review from a team August 18, 2026 18:32
@brow

brow commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

🤖 Superseded by #6243, which was recreated under the correct GitHub author.

@brow brow closed this Aug 18, 2026
brow added a commit that referenced this pull request Aug 24, 2026
### What changed?

After a new mobile invite claim succeeds, Buzz now best-effort ensures
membership in the same public starter channels as desktop:

- `#general`
- `#welcome-everyone`

Missing starters use desktop's deterministic per-relay IDs and exact
public channel configuration, so concurrent mobile and desktop setup
converges safely. Setup failures do not invalidate or retry an already
successful invite claim, and failure for one starter does not block the
other.

The success sheet offers **Continue to #welcome-everyone** when that
channel is available. Mobile does not create the private `Welcome`
channel because it cannot provision the desktop Welcome agents that make
that channel useful.

This PR is stacked on #6145 because it deliberately reuses that PR's
open-channel directory and join behavior. Once #6145 merges, this PR can
be retargeted to `main` without changing its BUZZ-12 diff.

Fixes
[BUZZ-12](https://linear.app/squareup/issue/BUZZ-12/bug-community-appears-empty-after-using-invite-link-on-mobile).

### How is it tested?

- Desktop/mobile deterministic starter-ID parity coverage.
- Existing-channel join and missing-channel creation coverage.
- Duplicate-create convergence and per-channel failure isolation
coverage.
- Invite success remains successful when starter setup fails.
- Widget coverage for continuing directly into `#welcome-everyone`.
- Focused invite/deep-link tests: 23 passed.
- `just mobile-check`: passed.
- `just mobile-test`: 1,483 passed.
- Pre-push repository checks: passed.

---------

Signed-off-by: Tom Brow <tomb@block.xyz>
Co-authored-by: Codex <noreply@openai.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants