Match the Scanner to the Code Before Changing the Camera
When a Ledger Live account import QR code is not scanning, the first useful question is whether the phone is in the correct import or synchronization screen. The app is now branded Ledger Wallet. A readable code can still be rejected when presented to a recipient-address scanner instead of the intended account-sharing flow.
There is no universal wallet QR format. A receive address, an encrypted linking invitation, and a historical desktop export serve different purposes. Keep the producing application and receiving screen visible so you can identify the pair.
Check the Source and Session
Create the code yourself inside the genuine desktop or mobile application. Use Ledger’s current Sync instructions rather than treating a screenshot from a message as a valid invitation. Codes authorizing access to account information should not be uploaded to a public decoder.
An invitation may stop being usable when its producing flow has ended or changed. If the app reports that the session is no longer valid, return to the supported linking controls and create a fresh invitation. Merely enlarging an old screenshot cannot re-establish the associated session.
Distinguish No Camera Image From No Recognition
If the scanner shows no live camera view, inspect camera access for the exact installed application. Android’s permission controls explain how to inspect app-specific grants; on iPhone, use its equivalent privacy settings. Grant the camera capability needed for the scanner, without enabling unrelated permissions.
If the live image works but recognition does not, clean the lens, remove strong reflections, and show the full code with its surrounding margin. Hold the phone steady at a distance that allows focus. Avoid digital zoom or display effects that merge the small squares together.
Where a genuine export animates or changes its displayed code, keep its live application screen available and follow that release’s instructions. A cropped still image might omit information expected by the matching importer. Do not infer that every current Sync code uses that older presentation.
Interpret What Happens After Recognition
For example, the camera may detect a code immediately and then display a connection error. That result means optical recognition progressed; the next investigation concerns linking compatibility, the active session, or network reachability. Repeatedly changing camera permissions would address the wrong boundary.
Check both applications are eligible current releases obtained from the official distribution page. Confirm internet access and investigate a specific error rather than deleting the existing account list. If the hardware is required for initial activation, handle that device approval separately from scanning.
Confirm the Imported Information
After completion, compare a known account’s chain and public identity with the source. A successful camera animation is not sufficient proof that the desired account selection was imported. Check any expected name changes only if the applications have an active synchronization relationship.
If scanning continues to fail, retain the app versions, phone model, source workflow, receiving workflow, and exact post-scan message. Report whether there was no camera view, no detection, or rejection after detection. Those three observations lead to different repairs.
Should I Send the QR Image to Support?
Describe the screen and error first. Account-sharing codes may disclose information or authorize linking. Do not publicly post an active invitation, recovery backup, or unredacted portfolio screenshot.
Can a Different QR Scanner Complete the Import?
Use the application’s supported scanner. A generic decoder cannot establish the intended authenticated application session and may expose the code to another service.
Must I Reset the Ledger to Fix Scanning?
No routine camera or import diagnosis requires erasing hardware. Preserve the initialized wallet while resolving the phone’s scanner or the specific linking process.