-
Notifications
You must be signed in to change notification settings - Fork 92
No timer now #267
Comments
|
Instead of taking a picture, go to the console tab and copy and paste everything that is red into here. |
Using version authenticator 4.20. Chrome Version 64.0.3282.119 |
Meaning there isnt any countdown timer in my authenticator. The 6 digit codes stay the same without moving |
Open the extension -> right click the pop-up window -> click inspect -> at the top of the page click console -> copy and paste red stuff here |
Slow network is detected. Fallback font will be used while loading: chrome-extension://bhghoamapcdpbohphigoooaddinpkbai/css/fontawesome-webfont.woff2 |
@GC200 are any of your codes dots (i.e. ******) instead of numbers? @mymindstorm - I had a similar error in my console and found out it was because two of my secrets had become corrupted (the encrypted flag was false but the secret looked encrypted). I guess I used different passwords on different computers or something went wrong when I unset the password - not sure at all. PS: In case it's not clear from the above, the corrupted secret also caused the infamous codes being replaced with dots issue. |
Or wait I'm wrong, scratch that |
Going over this issue again, something is really wrong with it. In the console enter this to get a backup:
Copy and save that somewhere safe. Reinstall the extension to clear it's data. Then copy back into import export box and see of issue still persists. |
I already fixed mine. Deleting the corrupted key from the interface didn't work so I took a regular export, removed the corrupted entries from the JSON, renumbered the indexes, imported the JSON and added the keys I had deleted in the normal way. During all of that my password was 'unset' (i.e. set to empty). |
My blank page authenticator (happened 18 hours ago) issue was resolved 6 hours later. It was running all good and now not a single timer display in all my 8 accounts link to authenticator. I have the frozen codes of 8 accounts. Can you help me??
The text was updated successfully, but these errors were encountered: