Use Both Displays to Explain the Missing Code
When a Ledger Live iPhone pairing code does not appear, inspect the Ledger screen and phone together. The application is now Ledger Wallet. A connection can be waiting before code comparison, reconnecting through an existing association or failing after another confirmation. The absence of one expected screen does not identify which case applies.
Do not approve a request blindly to see whether the next screen looks familiar. For a new code comparison, you need the matching information on both intended devices.
Make a Two-Screen Record
| Phone observation | Hardware observation to record |
|---|---|
| Still scanning | Power, lock and Bluetooth state. |
| Device selected, waiting | Any code or approval already displayed. |
| Existing device reconnects | Whether the requested app action completes. |
| A code is shown | The corresponding code on the intended Ledger. |
This makes a support report more useful than saying that no number arrived. Do not confuse an on-device PIN request with the Bluetooth comparison code; they have different purposes and input locations.
Decide Whether This Is New Pairing
A retained usable association need not repeat its original code exchange at every connection. Try the intended nonfinancial hardware interaction through the app. If it succeeds, the missing new-code screen is not by itself a fault.
If this is genuinely a fresh association, follow Ledger’s model-specific connection instructions. Touchscreen Stax and Flex interactions differ from Nano X button controls. Nano S Plus cannot produce a Bluetooth pairing code because the model has no radio.
Remove Ambiguity From the Request
Use one phone, the Ledger in your hand and one app-led attempt. Close competing ordinary wallet sessions and cancel old outstanding requests through their normal controls. Keep the hardware unlocked and nearby, with Bluetooth enabled.
Inspect the app’s relevant iOS access using Apple’s hardware permission guidance. Permission denied before discovery is not the same outcome as a selected device waiting for a code.
After selection, watch both displays instead of moving between several settings screens. Complete only the confirmation actually requested. If codes disagree, cancel that exchange; recognizing the device name does not resolve a numeric mismatch.
Escalate a Reproducible Missing Step
If the same step repeatedly fails after ordinary readiness checks, consult current pairing troubleshooting. A stale relationship may need coordinated removal, but use the exact model’s pairing command rather than the wallet’s factory-reset controls.
For example, a phone showing a selected device while the Ledger still displays its lock screen is a different record from two unlocked devices with no response. Preserve that distinction and the app, iOS and Ledger OS versions.
Finish progressing device OS installation before connection cleanup or app restart. Pairing repair should not require recovery words in the phone, a backup photograph or an on-chain validation payment.
Note whether the system pairing sheet is still visible behind another app screen. A prompt awaiting attention can explain a stalled sequence without establishing a device defect. Recover the intended screen before starting another request.
Pairing-Code Questions
Should I pair in iPhone Settings first?
Use the current Ledger app-led procedure. Starting another system pairing at the same time can make prompts hard to attribute. Follow the selected model’s instructions rather than combining unrelated tutorials.
Can I accept only the phone’s code?
For a requested comparison, read both devices before confirming. Missing information is a reason to resolve the stage, not permission to approve an unverifiable exchange.
Does a visible balance prove no code is needed?
No. Public account information can remain visible without hardware. Judge whether a live device action succeeds and whether you are reconnecting or creating a new relationship.
Comments are closed