Skip to content

[Bug]: QR Code Interface for Offline Signing Disappears Permanently, Forcing Restart #15430

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
chenlocus opened this issue May 17, 2025 · 0 comments
Labels
external-contributor type-bug Something isn't working

Comments

@chenlocus
Copy link

Describe the bug

When performing offline signing with QR code, the interface containing the QR code must remain open until the signing is complete. If the interface closes (due to time-out or manual closure), there is no way to retrieve the signed data, requiring a full MetaMask restart to re-initiate the signing process. This creates friction in offline signing workflows.

Expected behavior

No response

Screenshots/Recordings

No response

Steps to reproduce

  1. Initiate an offline signing process that generates a QR code interface

  2. Let the QR code interface close automatically (wait) or manually close it

  3. Complete the offline signing on the air-gapped device

  4. Attempt to retrieve the signed transaction via the original QR code interface

Error messages or log output

Expected Result:

A mechanism to recover/reopen the QR code interface after closure

Persistent session for ongoing signing processes

"Get Signature" functionality remains accessible until process completion

Actual Result:

Once QR interface closes, the signing context is permanently lost

No UI elements or methods to retrieve the signed data

Must restart MetaMask and redo entire signing process

Detection stage

In production (default)

Version

v7.45.2(1810)

Build type

None

Device

google pixle 8

Operating system

Android

Additional context

No response

Severity

This issue significantly impacts usability for air-gapped setups where signing processes may take extended time. The current workflow assumes continuous interaction which isn't always practical for offline devices.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
external-contributor type-bug Something isn't working
Projects
Status: To be fixed
Status: To be triaged
Development

No branches or pull requests

2 participants