Ask Which List Is Missing Nano X
If Nano X is not showing in the Ledger Live iPhone device list, identify the list before changing anything. The current software is Ledger Wallet. A newly scanned result, a saved app device and an iPhone system association are related records, but they are not interchangeable evidence of a working session.
Write the screen name beside the exact message. An empty discovery screen means something different from a saved Nano X that produces an error after selection. The latter has already passed a step that the former has not.
Prepare the Hardware You Intend to Select
Use Nano X’s own controls to confirm power, unlock it and check Bluetooth. Ledger’s Nano navigation map helps distinguish the Control Center from a coin application and a short confirmation from a long button hold.
Keep the iPhone nearby and end another phone’s ordinary active session. Do not try to pair from several phones simultaneously. A single intended request makes both the discovered name and the subsequent code exchange easier to identify.
Do not disturb a progressing Ledger OS installation for these checks. A hardware screen still showing installation progress belongs to the update procedure, not an ordinary discovery experiment.
Run a Scan With One Known Permission State
Verify the app’s iOS Bluetooth access and the phone radio separately. Apple’s permission reference explains this boundary. If access is off, correct that specific decision and repeat the scan rather than changing multiple privacy categories.
Choose Nano X in the current app-led connection flow. Read available labels carefully: a renamed or shortened label should be investigated against the hardware you prepared. Do not select the first similar-looking result simply because an older screenshot used a longer name.
Read the Result as a Progress Report
- A result appears after access is enabled: discovery has advanced.
- A result appears but pairing times out: preserve the later-stage error.
- Two screens show codes: compare them before approval.
- The list stays empty with correct conditions: preserve models, versions and hardware state.
Cancel mismatched codes or a request unrelated to your current action. A familiar name cannot make an inconsistent exchange acceptable. After a successful connection, use an intended device-dependent action rather than a previously loaded balance as the proof of communication.
Use Association Repair for an Association Problem
If the phone remembers Nano X but the app cannot use that relationship, consult Ledger’s pairing repair. Follow the Nano X branch and coordinate the relevant app record, phone association and hardware pairing state where directed.
This is a narrower operation than resetting the whole wallet. Preserve configured hardware and useful local account records. If a different supported phone can discover the same Nano X, report that controlled comparison without claiming it proves a particular iOS bug.
Nano X Device-List Questions
Can a Bluetooth entry remain after the device powers off?
A remembered system association can remain visible without live hardware communication. Check a current app operation instead of treating stored text as proof that Nano X is available now.
Will reinstalling restore every missing device entry?
Reinstallation changes application files and can affect local data. It does not supply hardware power or grant every permission automatically. Locate the failed scan or association boundary first.
Does adding Nano X again require its recovery phrase?
No. Connect the initialized hardware through the supported flow. Backup words do not belong in iOS to restore a Bluetooth device list, and an empty list does not imply changed wallet keys.
Comments are closed