Decide Whether the Entire Catalog or One App Is Missing
When the Ledger Live app catalog is not loading, distinguish a blank management page from a working catalog that lacks one expected app. The current application is Ledger Wallet. Those outcomes can involve different causes: an incomplete device session, an unavailable management request, or model and release-specific app availability.
Do not change the hardware’s wallet configuration to make a catalog appear. The list concerns supported software for the signer; its absence is not evidence that the underlying blockchain accounts disappeared.
If No Device Information Appears
Confirm that the intended Ledger is connected through the supported host route, unlocked on hardware, and showing the state requested by My Ledger. The dedicated desktop app uses USB data communication. A phone’s successful Bluetooth pairing does not verify that desktop path.
Read expected secure-connection prompts and close competing wallet sessions while the device is idle. If the operating system cannot detect the signer, start with Ledger’s USB connection guidance. Catalog searching cannot repair a connection the host never established.
Use the genuine current client through Ledger’s download page. If the interface moved, find the current My Ledger entry rather than assuming an old left-sidebar position is mandatory.
If Device Information Loads but the Catalog Does Not
This observation is useful: recognition progressed, while another request may still be failing. Ledger’s secure-channel reference describes online backend involvement in relevant management actions. Do not assume local hardware access proves all management services respond.
Capture the exact online error and check relevant incidents on Ledger’s status dashboard. If permitted, repeat the same non-financial request on a trusted alternate connection. A repeatable failure only behind a work gateway belongs with its administrator, especially if certificate inspection is involved.
Keep normal certificate validation active. Opening inbound ports, disabling protection, or importing an unknown root certificate from a helper is not an appropriate generic catalog repair. A 429 response needs reduced requests and retry guidance; a 503 needs endpoint availability context.
If Only the Desired App Is Missing
Check the exact asset and blockchain rather than searching a token symbol and assuming it has a dedicated app. Some supported tokens use the app for their parent network. Confirm the asset’s current integration and the selected Ledger model.
Compatibility can depend on the device OS and app dependencies. Ledger’s app-update guidance explains why an outdated OS can limit available device-app releases. Follow the supported maintenance order instead of turning on experimental providers to expose a different catalog.
For example, a populated catalog containing Bitcoin but not the name you expected is not the same symptom as every search returning an empty error panel. Give support the app name, model, installed OS, and result rather than the broad phrase catalog broken.
Confirm the Restored Function
After the identified cause is addressed, verify that device information and the intended supported app entry load. Installation is a separate next action; merely seeing an entry does not mean it is installed. Account addition is separate again and should be checked through its appropriate flow.
Preserve any progressing Ledger OS update before ordinary app restarts or connection experiments. A failed firmware state needs the model’s recovery instructions before catalog troubleshooting resumes.
Will Clearing Portfolio Cache Rebuild the App Catalog?
Account-history cache and management availability are different targets. Use cache controls only for the documented symptom, rather than deleting local data as a universal network repair.
Should I Download a Missing App Elsewhere?
Use the supported official catalog and current integration guidance. A privately supplied binary or developer build does not establish ordinary consumer support.
Does Support Need Wallet Secrets to Inspect Availability?
No. The model, component versions, app name, exact error, and network comparison are the relevant evidence. Recovery words and PINs must remain private.