-
Notifications
You must be signed in to change notification settings - Fork 27
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
KeePass built-in OTP Secret Issue #62
Comments
Hi, What is the format of the string stored in the |
Thanks for the report. It is now fixed. Can you try the developer version to confirm? |
TOTP.js error, complaining could not find. Fix to totp.js or rename TOTP.js to totp.js. Thanks. P.S. P.S.S. |
I found a bug in the My observation: Please try the latest commit (ff version attached) with some other secrets of yours and see if you can regenerate this issue. |
If you talk about my provided token above, then it maybe not the which one to rely on. It's one of my existing secret only modified. I don't have any issue so far with your plugin and Tray TOTP Plugin. I don't use regularly KeePass {TIMEOTP} parameter with Auto-Type. Thanks. |
Ok, then, please keep using the |
Haven't observed any problems. How long do you think to monitor any issue? Week? |
The new version with the updated OTP module is submitted to the stores. |
belaviyo, great news! |
Hi!
I'm using KeePass built-in OTP Secret TimeOtp-Secret-Base32. When press OTP button, returns “String of HEX type must be in byte increments” error. Can't figure out what's wrong.
Thanks.
The text was updated successfully, but these errors were encountered: