Authme not saving newly imported codes from Google Authenticator

[BrandonPotter0]

Before the bug report.

• I have searched the Github Issues for a bug that matches the one I want to file, without success.

Authme/System information

Authme: 6.0.2

Tauri: 2.2.0
Chromium: 131.0.0.0

OS version: Windows x64 10.0.26100
Hardware info: AMD Ryzen 9 9900X 12-Core Processor 31 GB RAM

Release date: 2025. January 08.
Build number: release.250108.170017

Created by: Lőrik Levente

Authme log

authme-2025-01-26-04-42-16.log

Describe the bug

Ive been trying to import some codes from my google authenticator on my phone to Authme, and the transfer completes just fine, and the code appears as normal in the program. But upon rebooting my computer, or shutting it down, I boot Authme back up, and the codes that I had imported as no longer there.

It seems the only way to force Authme to save the codes, was to manually update all of the descriptions for each code, forcing them to save. Its like Authme isnt being prompted to save the newly added codes to a configuration/settings file.

To reproduce

Boot up PC
Add new 2FA code into Authme from Google Authenticator (Patreon seems to be the one doing it for me)
Reboot PC
Reboot Authme
Code will be gone.

Additional information

No response

[Levminer]

Can you send the logs?

Settings >About > Logs > Show logs

[BrandonPotter0]

authme-2025-01-26-15-17-09.log
authme-2025-01-26-07-21-07.log
authme-2025-01-26-07-17-51.log
authme-2025-01-26-04-42-16.log

These are all the logs I have. Been replicating the issue a few times after the reboots, but after I changed all the descriptions, the issue had stopped.

[Levminer]

Can't reproduce

[mmben]

I have the exact same problem.
This is terrible. If you setup a 2FA, you better store the secret given to you somewhere else as well so you can re-do the process.

Here's my workflow:

1. Start the app
2. click on the "import codes" icon.
3. Choose the "Setup a key" option in the TOTP section.
4. Fill in the 3 fields, then click "Confirm"
5. The new 2FA is available on the overview with the rest.
6. Exit the application
7. Start the application

Actual Result:

• The 2FA is gone

Expected Result:

• 2FA was persisted

Log file content: (step 1-6)
[AUTHME LOG] (2025. 06. 28. 8:37:27) Authme 6.1.1 release.250610.204943
[AUTHME LOG] (2025. 06. 28. 8:37:27) Path changed: /confirm
[AUTHME LOG] (2025. 06. 28. 8:37:41) Path changed: /codes
[AUTHME LOG] (2025. 06. 28. 8:37:46) Path changed: /import
[AUTHME LOG] (2025. 06. 28. 8:38:16) Path changed: /codes

Log file content: (after 2nd start / step 7):
[AUTHME LOG] (2025. 06. 28. 8:38:34) Authme 6.1.1 release.250610.204943
[AUTHME LOG] (2025. 06. 28. 8:38:34) Path changed: /confirm
[AUTHME LOG] (2025. 06. 28. 8:38:39) Path changed: /codes

Reproducible every time I start the app until I do what the original reporter stated:
Go to edit and edit all items ones and click on the "Edit" button until you get the prompt: "Do you want to save your changes".
After that adding a new code works and is persisted.

This may or may not be related:
When I click the "Show Logs" button in the "About" section of the settings page, nothing happens, BUT at least I get this error in the logs:
[AUTHME ERROR] (2025. 06. 28. 8:43:10) Unknown runtime error occurred: Scoped command argument at position 0 was found, but failed regex validation ^((mailto:\w+)|(tel:\w+)|(https?://\w+)).+

[Levminer]

I have the exact same problem.
This is terrible. If you setup a 2FA, you better store the secret given to you somewhere else as well so you can re-do the process.

Here's my workflow:

1. Start the app
2. click on the "import codes" icon.
3. Choose the "Setup a key" option in the TOTP section.
4. Fill in the 3 fields, then click "Confirm"
5. The new 2FA is available on the overview with the rest.
6. Exit the application
7. Start the application

Actual Result:

• The 2FA is gone

Expected Result:

• 2FA was persisted

Log file content: (step 1-6)
[AUTHME LOG] (2025. 06. 28. 8:37:27) Authme 6.1.1 release.250610.204943
[AUTHME LOG] (2025. 06. 28. 8:37:27) Path changed: /confirm
[AUTHME LOG] (2025. 06. 28. 8:37:41) Path changed: /codes
[AUTHME LOG] (2025. 06. 28. 8:37:46) Path changed: /import
[AUTHME LOG] (2025. 06. 28. 8:38:16) Path changed: /codes

Log file content: (after 2nd start / step 7):
[AUTHME LOG] (2025. 06. 28. 8:38:34) Authme 6.1.1 release.250610.204943
[AUTHME LOG] (2025. 06. 28. 8:38:34) Path changed: /confirm
[AUTHME LOG] (2025. 06. 28. 8:38:39) Path changed: /codes

Reproducible every time I start the app until I do what the original reporter stated:
Go to edit and edit all items ones and click on the "Edit" button until you get the prompt: "Do you want to save your changes".
After that adding a new code works and is persisted.

This may or may not be related:
When I click the "Show Logs" button in the "About" section of the settings page, nothing happens, BUT at least I get this error in the logs:
[AUTHME ERROR] (2025. 06. 28. 8:43:10) Unknown runtime error occurred: Scoped command argument at position 0 was found, but failed regex validation ^((mailto:\w+)|(tel:\w+)|(https?://\w+)).+

Are you on Windows too?

[mmben]

Yes, Windows 11

[Levminer]

I tried debugging this again but I couldn't replicate it.

Are you using password authentication or no authentication?

[mmben]

Thank you for re-opening the issue and giving it another try!
I am using password authentication.

I've tried to replicate the issue again today and it works fine, so I can't reproduce it either at the moment.
So I see this is not easily reproducible.

I've had it two times so far.
When the issue occurrs it is reproducible every time until one changes all codes and saves (as described above).

The first time I thought it was maybe related to a character I used in one of the descriptions, but I don't think this was the issue.
The second time it happened was when I started commenting on here.
Between the two times were several weeks or even months (where I didn't try to add/change codes).
So I don't know yet what triggers it.
Could it be related to an update?
Could it be helpful to add a bit more logging?
I will try to reproduce it again on my side and comment as soon as it happens again.
Please let me know, if there are things I could try to help find the trigger.

[mmben]

Hi,
today I've got the nice blue hint in Authme informing me about an update.
So before updating, I tried to reproduce the problem again to ensure it's still fine and is maybe caused by an update.
And it's happening again, even before the update.
Logs don't show any issue.
I don't see anything related that could have provoked this.

[Levminer]

Thanks, I add more logging in the next update to see what's going wrong because I still have no idea what is causing this.

[Levminer]

Added some logging on the latest update