-
Notifications
You must be signed in to change notification settings - Fork 812
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
Adding new accounts with manual entry is broken #1262
Comments
Adding further details as I'm also getting issues with manual entry. I have the same versions, so Chrome is 127.0.6533.120 (updated today) and the extension is 8.0.0. I did not have this issue earlier. Problem: clicking ok on manual entry does nothing, so you cannot add new entries manually Replication steps:
Right-clicking the tool does allow me to inspect it and there I can see following error coming up when you click OK:
As far as I could see the issuer and secret values made no difference and modifying the advanced settings also made no difference. |
Thanks for the report! As a workaround, you should be able to do a text backup import using the string |
@mymindstorm is this a regression? I took a quick look but haven't yet identified the root cause. |
Think so but can't investigate until Sunday |
No worry. I will take a look first. |
The root cause is we store encryption map in state, but use it as encryption. https://github.com/Authenticator-Extension/Authenticator/blob/dev/src/models/otp.ts#L91 Data stored in state:
But use it as |
I tried with chrome, edge, firefox and brave; none worked |
Hotfix has been submitted to Google @mymindstorm could you help to submit v8.0.1 to Mozilla and Microsoft, thanks. |
It seems version 8.0.1 fixed this issue, is there a way to upgrade existing the extension (version 8.0.0) to 8.0.1? |
@cipineda I submitted the update to Microsoft, but it is pending review. |
Describe the issue
while doing manual entry it's not showing the code
Browser
Chrome
Browser Version
127.0.6533.120
Extension Version
8.0.0
The text was updated successfully, but these errors were encountered: