iPad ChatGPT 1.2026.230: Remote Control QR pairing always fails while iPhone 1.2026.224 works on same Windows host
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 125k
- Forks
- 19.4k
- PR merge metrics
- PR metrics pending
Description
What version of the Codex App are you using?
Windows ChatGPT/Codex desktop:
- Version
26.825.32147 - Released 2026-08-28
Mobile clients:
- iPad ChatGPT
1.2026.230(32543289983) — fails to pair - iPhone ChatGPT
1.2026.224— already paired and works with the same Windows host
Platform
Host:
- Windows desktop running ChatGPT/Codex Desktop
Remote clients:
- iPad (ChatGPT for iOS/iPadOS 1.2026.230)
- iPhone (ChatGPT for iOS 1.2026.224)
What issue are you seeing?
Remote Control pairing from the iPad always fails immediately after scanning a freshly generated QR code.
The iPad shows:
Pairing failed
Something went wrong while pairing. Try scanning the code again.
The Windows host never adds the iPad to the authorized-device list after the failed attempt.
This is notable because an iPhone on ChatGPT 1.2026.224 is already paired with and can remotely control the exact same Windows host successfully.
This makes the issue look like either:
- an iPad-specific Remote Control pairing bug, or
- a regression introduced in mobile build
1.2026.230.
Steps to reproduce
- On Windows ChatGPT/Codex Desktop
26.825.32147, open Settings -> Connections -> Control this computer. - Confirm Remote connections are enabled.
- Click Add to generate a fresh QR code.
- On iPad running ChatGPT
1.2026.230, open Remote and scan the QR code. - Pairing fails immediately with the error above.
- Return to Windows Settings -> Connections.
- The iPad does not appear in the authorized-device list.
Repeat with fresh QR codes: same result.
Expected behavior
The iPad should be added as a second authorized Remote Control device and be able to connect to the same Windows host alongside the existing iPhone.
Actual behavior
The iPad pairing fails every time and no iPad client record appears on the Windows host.
Troubleshooting already completed
- Confirmed Windows Remote / "Allow connections" is enabled
- Confirmed Windows can generate fresh QR codes
- Existing iPhone Remote pairing remains functional
- Re-generated QR codes multiple times
- Force-quit and restarted ChatGPT on iPad
- Signed out and back in on iPad
- Restarted Windows ChatGPT/Codex Desktop
- Tested after changing network / using a different connection
- Confirmed the iPad app is current at
1.2026.230 - Windows host is current at
26.825.32147
The failure is consistently at the authorization/enrollment stage: the Windows host never shows the iPad as an authorized device.
A/B comparison
| Device | ChatGPT version | Same Windows host | Result |
|---|---|---|---|
| iPhone | 1.2026.224 |
Yes | ✅ Works |
| iPad | 1.2026.230 |
Yes | ❌ Pairing failed |
This version split may be useful for identifying a mobile regression.
Possibly related
- #39959 — iOS Remote Control pairing fails at secure setup (
claimed=false) - #30750 — Codex mobile pairing fails on iPad; QR/manual code both fail
- #22802 — Mobile remote setup fails with “Secure setup failed”
Privacy
No QR contents, tokens, account IDs, device IDs, or other credentials are included here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the pairing failure using the listed Windows and iPad versions, then compare the behavior with related issues #39959, #30750, and #22802. Trace the authorization/enrollment path responsible for adding devices to the Windows authorized-device list; done means the iPad pairs successfully and appears as a second authorized device without regressing the working iPhone pairing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, rust
- Domain
- authentication, desktop-dev, mobile-dev
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100