[Bug]: iOS navigation breaks after closing a full-screen video opened from a file link
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 48/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 活発
- 技術スタック
- ios, typescript
- 領域
- mobile
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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
- On an iPhone, open a thread whose assistant message links a local video file, for example
Watch it: [clip.mp4](/path/to/clip.mp4). - Tap the link. The video opens in the native full-screen player and plays.
- Close the player by swiping it down. It shrinks back into the thread.
- 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).
- 主要言語
- TypeScript
- スター
- 24.8k
- フォーク
- 6.4k
- 平均マージ
- 10時間 56分
- マージ済み PR(30日)
- 226
環境構築
このプロジェクトの開発コンテナを、あなたの GitHub アカウントでブラウザ上に起動します。
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートあり
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
pingdotgg/t3code のほかの issue
-
[Bug]: request_secret file delivery has no trailing newline, and the tool text does not say so対応中かも このイシューにリンクされたプルリクエストがオープン中、またはマージ済みです。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 69/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 68/100
メンテナーはふだん 1 日以内に返信
-
[Bug]: Changing the sidebar project filter collapses an expanded Settled shelf back to 10 threadsオープン
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
pingdotgg/t3code#34291 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 83/100
メンテナーはふだん 1 日以内に返信
-
via-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
メンテナーはふだん 1 日以内に返信
pingdotgg/t3code の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
難易度 1/5 1時間未満 初心者へのやさしさ 82/100
lingdojo/kana-dojo#33947 · コメント 1 件 · リアクション 5 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
paperclipai/paperclip#20942 ·
メンテナーはふだん 1 日以内に返信
-
area: documentation good first issue package: rule-data status: accepting prs
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
メンテナーはふだん 1 日以内に返信
-
status: needs triage
難易度 2/5 1〜3時間 初心者へのやさしさ 85/100
mastra-ai/mastra#30109 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信