[Bug]: iOS navigation breaks after closing a full-screen video opened from a file link

Aperta
  • Qualcosa non va?
#33,998 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
ios, typescript
Ambito
mobile

Direzione di ricerca

Start in apps/mobile/modules/t3-native-controls/ios/T3NativeVideoPresentation.swift, especially present and finish, and trace how the embedded player is attached to the source view’s UIViewController. Reproduce the linked MP4 flow on an iPhone and inspect navigation state after dismissing the player; the issue’s responder-chain explanation is unverified. Done means dismissing the video leaves the thread and navigation stack usable, including switching threads and going back.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Before submitting
  • I searched existing issues and did not find a duplicate.
  • I included enough detail to reproduce or investigate the problem.
Area

apps/mobile

Steps to reproduce
  1. On an iPhone, open a thread whose assistant message links a local video file, for example Watch it: [clip.mp4](/path/to/clip.mp4).
  2. Tap the link. The video opens in the native full-screen player and plays.
  3. Close the player by swiping it down. It shrinks back into the thread.
  4. Go back to the thread list (swipe from the left edge or tap Back), then open any thread.
Expected behavior

Closing the video returns to the thread as it was. Back and opening other threads then work normally.

Actual behavior

From a screen recording of the steps above, about 18 s long:

  • Right after the player closes, the thread is scrolled to a different position, and within a second the app is back on the thread list.
  • The navigation stack no longer matches what is on screen. The list shows a Back button in its header. Tapping a thread row changes the header title to that thread, but the content stays the thread list, and rows can still be tapped through it.
  • Tapping Back then shows the original thread's content.
  • Going back once more turns the whole screen black, apart from the status bar. The app has to be force-quit.

It looks like navigation breaks as soon as the video closes: the native header and the visible screen stay out of sync from then on.

Impact

Major degradation or frequent failure

Version or commit

Current App Store iOS build on 2026-11-10 (exact build number not captured). The code below is from main at 047d4927.

Environment

iPhone (physical device), current iOS release. The video was an MP4 file on the host, linked from an assistant message.

Logs or stack traces

No crash log. The app doesn't terminate: it stays running with a broken screen until force-quit.

Screenshots, recordings, or supporting files

I have a screen recording. It isn't attached because it shows private thread content.

Workaround

Force-quit and reopen the app.

Additional context

Possible cause, from reading the code. I haven't verified this on a device.

When the tapped link's source view is on screen, T3NativeVideoPresentation.present takes the embedded path in T3NativeVideoPresentation.swift#L80-L95. It walks the source view's responder chain to the nearest UIViewController, which is the thread's react-native-screens RNSScreen. It then adds the AVPlayerViewController as a child of that screen controller, puts the player's view inside the link chip, and calls AVKit's private enterFullScreenAnimated:completionHandler:. On exit, finish() removes the child (L149-L156).

expo-video uses the same AVKit entry point, but it doesn't add the player controller as a child of the react-native-screens controller. Adding a child to an RNSScreen inside the native stack, and having AVKit present and dismiss full screen from it, may leave the stack's transition or view state inconsistent. That would fit the header and content disagreeing afterwards. The other path (presenter.present(controller, animated: true), used when there is no on-screen source) doesn't change the screen's child controllers.

Related, but not the same bug: #26662 and #32795 (Quick Look image previews failing to open), #26831 (inline videos no longer opening full screen).

Lingua principale
TypeScript
Stelle
24.8k
Fork
6.4k
Merge medio
10h 56m
PR unite (30g)
226

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di pingdotgg/t3code

Tutte le issue di pingdotgg/t3code

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.