Repository navigation
[Bug]: Mobile Pulls page flooded with repository read errors while host reconnects #19046
Description
Before submitting
- I searched existing issues and did not find a duplicate.
- I included enough detail to investigate the problem.
Area
apps/mobile
Steps to reproduce
Observed on an iPhone connected to a Mac host with multiple GitHub repositories:
- Open the Pulls tab.
- Select the Open and Your review filters.
- The captured screen shows the host connection reconnecting and a long list of repository read errors.
The exact trigger and repeatability have not been confirmed. The reconnecting state may be relevant, but the screenshot alone does not establish the cause.
Expected behavior
Show pull requests for repositories that can be read. If the host is disconnected, show a clear connection status and a retry path. Repository failures should be compact enough to keep the page usable on a phone.
Actual behavior
The Pulls page is filled with repeated messages in this format:
repo-a: example-org/repo-a could not be read.
repo-b: example-org/repo-b could not be read.
repo-c: example-org/repo-c could not be read.
The screenshot shows more than 20 such entries. The error list occupies almost the entire screen, with no pull request cards visible in the captured area. The header also shows "Reconnecting to [host]...".
Impact
Major degradation of the Pulls page in the captured state. The screenshot does not establish whether the rest of the app is affected.
Version or commit
Unknown for the affected iPhone and Mac host.
Environment
iPhone mobile client connected to a Mac host. Exact iOS, macOS, and app versions are unknown. The Open and Your review filters are selected.
Logs or stack traces
No logs collected. The anonymous messages above are transcribed from the screenshot.
Screenshots, recordings, or supporting files
The original screenshot is intentionally omitted because it contains private organization names, repository names, and a personal host name. All names in this report are anonymous placeholders.
Workaround
None confirmed. Recovery after reconnection or retry has not been tested.
Activity