Treat the Portfolio as a View to Verify
Ledger Live iOS sync problems can make a portfolio look inconsistent with recent activity. The mobile interface is now called Ledger Wallet. To investigate, select one affected account and determine which information is stale instead of deleting the whole setup.
This independent guide distinguishes an absent account, delayed blockchain history, and a transaction that genuinely remains pending. Each can look like a synchronization failure from the home screen, but the evidence and next action differ.
Start With a Specific Discrepancy
Record the account’s blockchain, asset, and expected activity. If comparing desktop and iPhone, confirm the actual public account rather than a similar name. A token on one network should not be compared with a token of the same name on another.
If the account is missing entirely, inspect the supported add-account or Ledger Sync workflow. Ledger Sync concerns account information across installations; it is not the same operation as loading the latest blockchain history. If the account exists but its history is old, continue with data-service diagnosis.
Check the Transaction Outside the Portfolio
For a known transfer, inspect its transaction ID on an appropriate explorer for the correct chain. Establish whether the network shows confirmation, pending status, or no matching transaction. Do not send a replacement simply because the iPhone list has not updated.
Only public information is needed. Keep recovery words and private keys away from explorer sites and support forms. Public account links also disclose financial activity, so avoid posting them widely when a private error description is sufficient.
Check Service Availability and Reachability
Review Ledger’s status dashboard for the relevant explorer or component. An affected service can prevent the app from rebuilding a current account view even though your hardware remains paired and healthy.
Confirm internet access on the phone, including completion of any network sign-in. If no incident explains the failure, compare another trusted connection and note whether the same account refresh works there. A problem confined to one network is useful evidence for filtering or connectivity investigation.
Refresh the Local View After Services Recover
Use the latest compatible app from the verified App Store route. Ledger’s account synchronization guidance describes clearing temporary cache once the relevant service is available. Select the intended in-app control and read its confirmation.
Allow time for the rebuilt account history to load before drawing another conclusion. Deleting the entire iPhone application is a broader action that may remove account listings and preferences. It is not a necessary first response to a service incident.
Keep Hardware Troubleshooting Separate
A public-account refresh can work without an active signing session. If the app communicates with the Ledger but history remains stale, repeated pairing resets target the wrong stage. Updating hardware firmware is also not automatically required to fix an unavailable data service.
If the discrepancy persists, contact official support with the app version, iOS version, network, exact message, and explorer result. Describe the one affected account and the checks performed. A screenshot of the recovery backup must never be part of that report.
Portfolio Questions
Why Might a Total Differ From One Account’s Balance?
Check which accounts, assets, and valuation settings contribute to the total. A pricing or display difference is not necessarily a blockchain synchronization failure.
Can I Verify a Receive Address During a Data Incident?
Follow the supported workflow and verify it on the hardware. Do not substitute an unverified address from a support message just because a service is temporarily unavailable.