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
Import from authy fails #1077
Comments
I'm using Lineage 19.1 (freshly installed, rooted with Magisk), and I encountered the exact same problem. |
I haven't taken a look at this yet, but if you guys indeed have Authy installed, are logged into the app and that file doesn't exist.. It may mean that Authy now stores everything in a different file and perhaps in a different format as well. This'll require a bit of investigation. |
Can confirm I did have Authy installed, logged into it, and couldn't import into Aegis, with the same error as the OP. |
Can confirm that the import does not work. I managed to manually navigate to Edit: A quick look into the code shows that the |
What does it return? |
I did not test or debug this, so maybe my assumption was wrong, but the error message states that it could not find a file under |
i had the same problem as the OP but my experience was a little different than @Trup3s. i ended up copying one of the xml files to my internal sdcard and pointing aegis to that and it worked. my phone is a oneplus 7 pro running oxygen os 11.0.9.1.GM21AA. android version 11. it's rooted with magisk 25.2 with zygisk and ramdisk enabled. i'm running aegis 2.1.3 downloaded from google play with biometric unlock for my vault. the version of authy i have is 24.11.0. |
Just adding that I have the same issue on my Google Pixel 7 on Android 13. However, my previous phone and the one I imported the Android backup was a OnePlus Nord CE 5G with Oxygen OS 12, in case that matters. And the error is also the same
|
Same problem here. This quite simple workaround solved it for me:
|
I also had this problem. It is weird that Authy “does no find” the file when root access is granted and the same file can be verified to exist e.g. via Termux. I wonder if there’s some SELinux shenanigans going on. I’m using Magisk 26.1 and Android 13. I was able to work around the problem by importing via a file, as suggested in the post above. |
Same, here. Galaxy S21 Ultra rooted with Magisk and cannot import from Authy. The error i got when i try to import Authy tokens to Aegis:
|
Oh, it works fine! Thanks for the tip ^^ |
I managed to solve this problem by changing Magisk mount settings to I stumbled upon this while trying to copy the |
We do actually request the root shell to be run in the global mount namespace: Aegis/app/src/main/java/com/beemdevelopment/aegis/ui/tasks/RootShellTask.java Lines 18 to 19 in 224ec25
So I'm not sure what we could be doing wrong here. |
Oh, I see: #1278. |
Version
2.1.2
Source
F-Droid
Vault encryption
Yes (with biometric unlock)
Device
Oneplus 3t
Android version
Android 11
ROM
Havoc OS 4.19
Steps to reproduce
On a rooted phone with authy installed and 2fa codes in it, open aegis, go to settings and then import from app. When authy is selected and ok is pressed, it will give an error message and in more details it will show:
com.beemdevelopment.aegis.importers.DatabaseImporterException: java.io.FileNotFoundException: No such file or directory: /data/user/0/com.authy.authy/shared_prefs/com.authy.storage.tokens.authenticator.xml
What do you expect to happen?
It to import the 2fa codes from authy
What happens instead?
It fails to find the file the tokens are stored in
Log
No response
The text was updated successfully, but these errors were encountered: