Recheck the Connection Conditions After iOS Maintenance
If Ledger Live finds no devices after an iOS update, compare app permission, hardware readiness, and saved association state before blaming the update itself. The mobile app is now Ledger Wallet. The timing is useful evidence, but it does not prove that every phone on that iOS release has a Bluetooth defect.
Confirm that the phone’s system update finished normally and ordinary apps are usable. Then perform one deliberate Ledger discovery attempt with both screens available. Avoid combining account resets, phone-network resets, and hardware pairing changes at once.
Check Radio and Permission Independently
Verify Bluetooth is enabled on the phone and on the supported Ledger model. Unlock the hardware and keep it nearby. Inspect app-specific access under Settings, Privacy & Security, Bluetooth rather than assuming the phone radio setting grants every app permission.
Apple’s Bluetooth access guide explains the separate authorization. If access is disabled, correct that setting and repeat the same scan. If the app is absent from the list, initiate its connection feature so iOS can request access, as described in Apple’s privacy guidance.
Do not grant unrelated camera, contacts, or location access as an undirected repair. Each permission concerns a capability; more enabled switches do not necessarily improve Bluetooth discovery.
Review What the App Calls the Device
Open the current device-connection or My Ledger flow and select the actual model. A firmware or app change can shorten a default device label, so compare available entries carefully. An unfamiliar abbreviation is evidence to inspect, not permission to select the first nearby device.
If another phone still has an active Ledger session, end it before testing. A competing connection is a different explanation from an iOS regression. Keep only one pairing attempt visible so every request can be tied to your action.
Test Existing Associations Before Removing Them
An iPhone can remember a device while the app cannot complete a live session. Conversely, a valid association may reconnect without displaying a fresh code. Test an intended hardware-management action rather than judging solely by a system entry or cached portfolio.
If the old relationship remains unusable after normal checks, consult Ledger’s current pairing recovery. Follow the model’s coordinated app, phone, and hardware pairing removal procedure. Clearing pairings must not be confused with factory-resetting the signer.
For a new exchange, compare the codes on both displays and cancel any mismatch. Do not accept an unexplained request because the device name resembles your old entry.
Record a Useful Before-and-After Comparison
Report the iPhone model, iOS build, app version, Ledger model, and first unsuccessful stage. Include whether app permission existed and whether another supported phone can discover the same hardware. That comparison helps narrow the scope without asserting an unsupported cause.
If Ledger OS installation is still progressing on any host, preserve it before restarting applications or changing connections. A failed device update follows its own model-specific recovery, not generic post-iOS discovery experiments.
A useful comparison is whether another Bluetooth-capable Ledger appears in the same app scan under equivalent conditions. Keep ownership and permissions clear; a result from an audio accessory does not test this discovery workflow.
Post-Update Questions
Should I Delete the App Immediately?
No. Establish the permission and session state first. Full removal can discard local account organization without explaining why the scan is empty.
Could Nano S Plus Be Missing Because of iOS?
It has no Bluetooth and does not support the wired iPhone Ledger route. Updating iOS cannot add that unsupported hardware workflow.
Does Re-pairing Require Wallet Recovery?
No. Keep the initialized hardware and backup intact; never type the phrase into the phone to authorize Bluetooth after an update.