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

Keys gone after update to 4.2.2 #4528

Closed
r3ps4J opened this issue Dec 28, 2024 · 9 comments
Closed

Keys gone after update to 4.2.2 #4528

r3ps4J opened this issue Dec 28, 2024 · 9 comments
Labels

Comments

@r3ps4J
Copy link

r3ps4J commented Dec 28, 2024

Description

Just updated to auth 4.2.2 and after opening it prompts me with setup your first account. I don't think that's supposed to happen as I had a lot of 2fa keys set up. I'm still logged in as well. Someone please help? Don't want to loose access to all those accounts

Version

v4.2.2

What product are you using?

Ente Auth

What platform are you using?

Desktop - Windows

@r3ps4J r3ps4J added the triage label Dec 28, 2024
@r3ps4J
Copy link
Author

r3ps4J commented Jan 4, 2025

Oh I just moved to this since authy discontinued their desktop app. I really need a desktop app and this one had some good reviews.

@prateekmedia
Copy link
Member

prateekmedia commented Jan 5, 2025

@r3ps4J You can logout and login back to fix the issue, the issue was caused to people who were moving from ente auth v4.0.3 beta 5 on Windows to newer stable releases.

@prateekmedia
Copy link
Member

@netsizen Your issue is offtopic, although you can export the codes to other 2fa auth apps and check if they show the same code or different one. Mostly 2FA showing wrong are due to wrong system time and it is a general solution.

We don't modify the secrets so you will still be able to export codes to check it on other apps.

@r3ps4J
Copy link
Author

r3ps4J commented Jan 5, 2025

@prateekmedia I was pretty sure I updated this issue because that's what I did and it fixed it. But seems like that post did not properly save, sorry! I think I came from v4.0.2. I hope this doesn't happen again in the future because it was pretty scary.

@prateekmedia
Copy link
Member

prateekmedia commented Jan 5, 2025

@r3ps4J Sorry from our side, it was not handled well. Also if someone is visiting the thread in future, they can upgrade to this version to fix it automatically:
#4101 (comment)

@prateekmedia prateekmedia closed this as not planned Won't fix, can't repro, duplicate, stale Jan 5, 2025
@prateekmedia
Copy link
Member

prateekmedia commented Jan 6, 2025

@netsizen Your comment was offtopic to this issue. Again it's your choice to what you choose to use, although if you have a change in mind then you can try the steps told in your original issue and let us know the behaviour.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants
@r3ps4J @prateekmedia and others