Lucas

Logs taken right after opening Seedvault and the backup process started: [seedvault-14-4.0-1725061029282.txt](https://github.com/user-attachments/files/16822785/seedvault-14-4.0-1725061029282.txt)

> Did you open the app for backup to start in this log? Yep. I used the log feature inside Seedvault if that's helpful. I can take another log soon...

I do notice a few times backups erroring out which I find weird, not sure if its related...

It has been a while... I don't remember unfortunately.. Usually I see the backup notification showing up right away when I open the app, or at worst 2 seconds later

[seedvault-14-4.0-1725374138847.txt](https://github.com/user-attachments/files/16850465/seedvault-14-4.0-1725374138847.txt) Here I noticed I plugged the drive in, had to open the backup app for it to start "automatically", and in the end it failed and restarted the backup....

Afterwards, I tried opening the backup app in my work profile, and it did not start automatically even when I opened it. [seedvault-14-4.0-1725374499409.txt](https://github.com/user-attachments/files/16850558/seedvault-14-4.0-1725374499409.txt)

Funny thing I just detected when getting logs for #830, if I plug in, eject and disconnect, and THEN open Seedvault, it reports a failed backup.

Fixed with #835

I had this happen a while ago where it seems like F-Droid only published the armv7 version or didn't release ARMv8. This is currently happening at the moment, and then...

This should now be fixed in the main branch for the native app, Firefox Nightly should work soon (https://github.com/bitwarden/android/pull/4450) I originally did not add F Nightly because I honestly thought...