Import file does not work

[CrimsonGlory]

FreeOPT+ version: 3.1.1 (23)
Android version: 6.0.1

I wanted to backup the keys in other phone. So I exported the keys to a file and moved the file to an old phone.
Tried to import the keys and FreeOPT+ says the file is malformed. Tried both JSON and URI key format. Verified that the md5 was the same.
Used Little File Explorer in order to lookup the file to import (not sure if this can affect anything). The default file explorer from Samsung just hides the FreeOPT+ backup files for some reason (even if I change the extension to .apk)

I ended up using QR scan one key at a time and that worked.

[licaon-kter]

We've seen reports of the backup malfunction here too: https://forum.f-droid.org/t/freeotp-ignores-a-critical-known-issue/27237

[vdbhb59]

@CrimsonGlory try this: freeotp/freeotp-android#411 (comment)
It works. Also, few entries get malformed, if this happens (tried and tested several times):
Steps to reproduce:

1. Have few entries/more than 1 entry in your FOTP/FOTP+ client.
2. Set authentication method to secure/encrypted (FP also should be fine). This is needed to reproduce (at least for me).
   This can be set even with an empty list, or after having an entry, does not matter for reproduction here.
   Ensure to quit the app post setup of PIN/FP.
3. Now reopen and add an entry which you may remove once setup and backed. Example, any temporary setup.
4. Now take a backup in JSON/TXT format, or both.
5. Remove the authentication temporarily, quit, relaunch and remove that temporary entry, and take a backup now in JSON/TXT format. Do not overwrite (if you are renaming the back up files). Keep both backups.
6. Now open the file (saved during PIN/FP) present via any text editor/viewer (Android, Windows, Linux, Mac, anywhere).
7. You will be able to see the malformed entry (temporary one), which will show as incomplete entry.

[helloworld1]

Hmmm, very weird issue. Thanks for the repo steps. I will see if I can repo.

[CrimsonGlory]

Forgot to mention. In my case the error was without the app authentication method enabled. Haven't tried that feature yet.

[vdbhb59]

I was able to reproduce with the authentication OFF. Same issue. Same steps to reproduce, just ignore steps where there is authentication required. But logically the issue remains same.