Skip to content
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

"Invalid Hex Data for Private Key" and "Invalid PIN Code" errors after mobile attempts to be synced with Desktop imported on keycard #21812

Open
VolodLytvynenko opened this issue Dec 12, 2024 · 0 comments

Comments

@VolodLytvynenko
Copy link
Contributor

Preconditions:

  1. Desktop user profile is imported onto the keycard.

Steps to Reproduce:

  1. Generate a sync QR code on Desktop.
  2. Scan the QR code using Mobile. (Now "Invalid hex data for private key" error is shown)
  3. Close and reopen the Mobile app.
  4. Attempt to log in.

Actual Result:

  • "Invalid hex data for private key" error appears initially.
  • After reopening the app, the synced user appears in the profile list.
    However, login is not possible, and an "Invalid PIN code" error is displayed consistently.
sync_ios.mp4

Expected Result:

Syncing the user via QR code works seamlessly.
The synced user is added to the profile list with full login functionality.

Devices:

Android, IOS

Logs:

logs (7).zip

ENV:

Release 2.33

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

1 participant