Use the Missing Entry as a Clue
A missing Ledger Live iPhone Bluetooth permission is worth checking at the request stage. Installing the app does not necessarily create every privacy entry immediately. Ledger Wallet, formerly Ledger Live, must reach the feature that requests Bluetooth before its authorization can be assessed.
Begin with the iPhone unlocked and the genuine app open. Note whether you mean the Bluetooth radio screen or the app list under Privacy & Security. Those screens answer different questions, and a saved accessory name is not the app’s permission record.
Three Observations, Three Next Steps
| What you see | What it suggests checking |
|---|---|
| Ledger app absent from the privacy list | Whether its Bluetooth feature has requested access. |
| Ledger app listed with access off | The decision recorded for that capability. |
| Access on but discovery empty | Hardware readiness and the connection workflow. |
Apple’s privacy explanation describes why an application appears after requesting access. Do not erase all privacy preferences just because the first of these observations applies.
Reach the Request Through a Real Device Task
Use the current device-addition or My Ledger flow, select the model you actually own and begin the supported mobile connection. Prepare a Bluetooth-capable Ledger nearby, powered and unlocked. Nano S Plus cannot use this route because it lacks Bluetooth.
Read any iOS request that follows your action. If accepted, revisit the privacy entry and record the new state. A previously absent row becoming visible shows that the request path was reached; it does not establish that pairing has completed.
If no request appears, record the precise navigation and the app and iOS versions. Confirm the installed identity through the official App Store listing. An unavailable feature, unsupported configuration or management restriction deserves an exact report rather than a modified app intended to force a toggle.
Do Not Substitute Another Bluetooth Test
A speaker playing audio does not settle this authorization. Apple distinguishes app Bluetooth access from some audio uses in its Bluetooth permission guide. Similarly, granting camera access for QR scanning does not authorize Ledger discovery.
Once the relevant access is on, return to the same intended scan. If it now finds hardware, continue with the model’s pairing instructions. Inspect both screens when codes are presented, and cancel disagreement. If nothing appears, investigate power, radio state and competing phone sessions instead of enabling unrelated privacy categories.
Keep the Comparison Reversible
For example, an app absent before discovery and present afterward is a useful before-and-after result. An enabled entry with a repeated empty scan is another result entirely. Preserve that distinction for support so the next step concerns the remaining boundary.
Perform ordinary restarts only when no device OS installation is progressing. A permission experiment must not interrupt active Ledger maintenance or require account-data deletion. Recovery words stay outside iPhone settings, app dialogs and any support message.
If the app requested access in a different installation or before removal, describe that history too. Reinstallation and a current permission request are distinct events; an old screenshot cannot establish the authorization now recorded for this installed copy.
Questions About the Absent Permission
Is Bluetooth permission the same as pairing?
Permission lets the app use an iPhone capability. Pairing associates the intended phone and hardware. You can have permission without a usable pairing, and account synchronization is another separate function.
Should I request location access instead?
Use the iPhone workflow. A legacy Android discovery instruction is not evidence that iOS needs the same setting. Report the actual Apple prompt and current Ledger screen.
What if the phone is managed?
Ask its administrator about the specific restriction and intended app. Do not remove management profiles or weaken general phone protection to make a missing privacy entry appear.
Comments are closed