Automatic migration of entries to new version failed.

[profanek]

Describe the bug
After installation of new version 2.0.4 automatic migration of my password failed.
"Your items could not be imported. Nothing was lost, and KeyGo will try again the next time you open it."
Application open and it is empty.

To Reproduce
Steps to reproduce the behavior:

1. Info of migration
2. Entering password (biometrics was not possible to use)
3. Information of import error
4. App doesn't contain any entries.

Expected behavior
I hope that all passwords and login will be visible in new app version.

Environment information (please complete the following information):

• Device: [Samsung A56]
• OS: [Android 16]
• App Version: [2.0.4]

Additional context
Perhaps the issue is that some individual entries contained longer texts? What can I do to help fix this error? Regaining access to my passwords is very important to me…
Unfortunately, I didn’t have any password backup created.

[profanek]

I was able to take some logs form android during migration process.
It looks like my earlier intuition was correct. Could I ask you to take this situation into account? So that instead of stopping the entire import process, only that single entry would be skipped?

09-29 14:17:29.813 E/RunPendingMigration(30326): v1 import did not finish 09-29 14:17:29.813 E/RunPendingMigration(30326): java.lang.IllegalArgumentException: Invalid input to toASCII: 1.22GGN86 11.HGPKMH7 21.KKJ7WV8 09-29 14:17:29.813 E/RunPendingMigration(30326): 2.B08JVH6 12.T1D8PW5 22.WDQH476 09-29 14:17:29.813 E/RunPendingMigration(30326): 3.NWP06R6 13.X36PQ93 23.WXVW3T2 09-29 14:17:29.813 E/RunPendingMigration(30326): 4.G9K1RC6 14.F48Q9V4 24.V7QT2P6 09-29 14:17:29.813 E/RunPendingMigration(30326): 5.BNF2MP6 15.BWFGFT5 25.Q6MKZ57 09-29 14:17:29.813 E/RunPendingMigration(30326): 6.6TR4PT2 16.KK5JTR8 26.569Q293 09-29 14:17:29.813 E/RunPendingMigration(30326): 7.BX9WG14 17.TQKK8R8 27.4GY2354 09-29 14:17:29.813 E/RunPendingMigration(30326): 8.487DC28 18.WXDIHH8 28.9XCP1W7 09-29 14:17:29.813 E/RunPendingMigration(30326): 9.N5JTX35 19.K6H25P3 29.RTKG2V6 09-29 14:17:29.813 E/RunPendingMigration(30326): 10.JY5FPP4 20.DQB5TH8 30.H35HLP4 09-29 14:17:29.813 E/RunPendingMigration(30326): at java.net.IDN.toASCII(IDN.java:115) 09-29 14:17:29.813 E/RunPendingMigration(30326): at java.net.IDN.toASCII(IDN.java:138) 09-29 14:17:29.813 E/RunPendingMigration(30326): at t64.a(r8-map-id-c669e36c5dda3e5dd0f16565b684a8ad0898c8763374f68f95bf4a1ef155f085:77) 09-29 14:17:29.813 E/RunPendingMigration(30326): at pb3.b(r8-map-id-c669e36c5dda3e5dd0f16565b684a8ad0898c8763374f68f95bf4a1ef155f085:331) 09-29 14:17:29.813 E/RunPendingMigration(30326): at re.invokeSuspend(r8-map-id-c669e36c5dda3e5dd0f16565b684a8ad0898c8763374f68f95bf4a1ef155f085:163) 09-29 14:17:29.813 E/RunPendingMigration(30326): at re.invoke(r8-map-id-c669e36c5dda3e5dd0f16565b684a8ad0898c8763374f68f95bf4a1ef155f085:18) 09-29 14:17:29.813 E/RunPendingMigration(30326): at n91.a(r8-map-id-c669e36c5dda3e5dd0f16565b684a8ad0898c8763374f68f95bf4a1ef155f085:116) 09-29 14:17:29.813 E/RunPendingMigration(30326): at ss3.d(r8-map-id-c669e36c5dda3e5dd0f16565b684a8ad0898c8763374f68f95bf4a1ef155f085:359) 09-29 14:17:29.813 E/RunPendingMigration(30326): at ps3.invokeSuspend(r8-map-id-c669e36c5dda3e5dd0f16565b684a8ad0898c8763374f68f95bf4a1ef155f085:12) 09-29 14:17:29.813 E/RunPendingMigration(30326): at m10.resumeWith(r8-map-id-c669e36c5dda3e5dd0f16565b684a8ad0898c8763374f68f95bf4a1ef155f085:8) 09-29 14:17:29.813 E/RunPendingMigration(30326): at pk1.run(r8-map-id-c669e36c5dda3e5dd0f16565b684a8ad0898c8763374f68f95bf4a1ef155f085:114) 09-29 14:17:29.813 E/RunPendingMigration(30326): at h41.run(r8-map-id-c669e36c5dda3e5dd0f16565b684a8ad0898c8763374f68f95bf4a1ef155f085:118) 09-29 14:17:29.813 E/RunPendingMigration(30326): Caused by: The output exceed the max allowed length.. line: 0. preContext: . postContext: 09-29 14:17:29.813 E/RunPendingMigration(30326): 09-29 14:17:29.813 E/RunPendingMigration(30326): at android.icu.impl.IDNA2003.convertIDNToASCII(IDNA2003.java:288) 09-29 14:17:29.813 E/RunPendingMigration(30326): at android.icu.text.IDNA.convertIDNToASCII(IDNA.java:664) 09-29 14:17:29.813 E/RunPendingMigration(30326): at com.android.icu.text.ExtendedIDNA.convertIDNToASCII(ExtendedIDNA.java:50) 09-29 14:17:29.813 E/RunPendingMigration(30326): at java.net.IDN.toASCII(IDN.java:108) 09-29 14:17:29.813 E/RunPendingMigration(30326): ... 11 more

I can send the full log if necessary.

[profanek]

[profanek]

I asked Claude about this problem and received some suggestions. I’m pasting his reply — maybe it will be helpful in some way.
Best regards. Aside from that, thank you for creating such a fantastic app — I really appreciate it.

---

Suggested fix for the v1 import failure (IllegalArgumentException in IDN.toASCII)

Root cause (as far as I can tell from the stack trace)

The v1 import aborts with v1 import did not finish because java.net.IDN.toASCII throws IllegalArgumentException (The output exceed the max allowed length).

The input was not a domain at all, but a long multi-line text in the URL/website field of one legacy item (a list of numbered backup codes). The importer seems to derive a registrable domain from that field for autofill. As a result, one malformed entry stops the whole import.

Suggested changes

1. Isolate failures per item. Wrap the conversion of each legacy item in try/catch (or runCatching), so a bad row is skipped and reported instead of aborting everything. The PR description mentions per-row failure isolation, but this exception seems to escape it, possibly because it is thrown in a different stage (domain resolution) than the one being guarded.

2. Make the domain resolution itself safe, for example:

   fun String.toAsciiDomainOrNull(): String? {
       val candidate = trim()
       // A valid DNS name is at most 253 chars, with labels of at most 63 chars.
       if (candidate.isEmpty() || candidate.length > 253 || candidate.any { it.isWhitespace() }) return null
       return try {
           IDN.toASCII(candidate)
       } catch (_: IllegalArgumentException) {
           null
       }
   }

If the result is null, keep the original text as-is and just skip the autofill domain association for that item.

3. Do not lose the data. If the field content is not a valid domain, import it unchanged into the note or website field of the new item.

4. Report skipped items. Add the item to the migration report as a partial failure (e.g. reason INVALID_DOMAIN), so the user can see what was affected.

5. Add a regression test with a legacy item whose URL field contains a very long, multi-line string, and assert that the import finishes and all other items are imported.

[OffRange]

Hey, thanks for the kind words! I am looking into it, hopping to publish an fix asap

[OffRange]

Thank you for reporting this! A fix will be merged as soon as the checks on PR #108 pass, and patch version 2.0.5 will be released to the Google Play Store shortly after.

Important

To ensure your login credentials remain accessible for the migration step in v2.0.5, please do NOT clear your app data or cache. Simply update the app via the Play Store once the new version is live.

I appreciate your patience, and apologies for any inconvenience this may have caused!

[OffRange]

@profanek I am happy to announce that a patch has been released and you are now able to update. Once you open the app, you should see the migration steps in and all your logins will be recovered.