Entering a closed thread gives an inaccurate error that channel access is denied

(#3957) Bug Open: Needs triage desktop mobile threads-forums-media

Reproduction steps

  1. Go to a text channel.
  2. Tap the threads icon at the top right.
  3. Create a thread.
  4. Tap the title of the thread for the thread menu.
  5. Tap Close thread.
  6. Fully close and reopen the app.
  7. Tap on the message that said you started the thread.
(Workaround)
  1. Tap the threads icon at the top right.
  2. Tap on Closed to get to the closed threads.
  3. Tap on the closed thread you wanted to access.
  4. Now the link in the channel works as well, if you go back.
mobile.mp4 shows step 7 and the workaround. desktop.webm shows what this whole thing looks like on desktop.

Expected behaviour

I'm not really sure. If you do the equivalent to this on desktop, you cannot do step 7, because the thread link is gone. However desktop behavior is also not really that intuitive, so I am more inclined to say behavior for this scenario should change on both mobile and desktop. If mobile were to match desktop's behavior exactly, the link to the closed thread should not be active when you reach step 7. For reference, on Discord a thread's link is clickable even after being closed.

Actual behaviour

A sheet pops up saying "Channel access denied". However, it is very easy to work around, as described in the reproduction steps above.

Build information

Version 2026.10.100, Beta 5, Channel Beta, Build 2666, Android 16 (arm64), Device Google Pixel 9a, Locale en-US, Push fcm, Flutter 3.47.7, Dart 3.13.5 Canary Desktop 2026.1012.194217, Web 2026.1012.194217, Linux 7.2.9-200.fc44.x86_64 (x64), Electron 44.4.1, Chrome 152.0.7977.78, Node 24.21.0, Locale en-US

Platform

macOS, Windows, Linux, Web, Android, iOS

Comments

Sign in with Fluxer to comment and vote.

No comments yet.