Full crash loop of app until full reset/uninstall (possibly related to forced device restarts)

[Dasnap]

Device Information

• Device: Ayn Thor
• Android Version: Android 13
• Argosy Version: 2.3.0

Bug Description

The app seems to enter a full crash loop after a forced device restart. This can only be remedied via a full wipe and reinstall.

Steps to Reproduce

1. Install app and go through setup process.
2. Trigger normal device restart. Argosy launches as expected.
3. Trigger hard restart of device (hold power button). Argosy will enter a crash loop and will require a reinstall.

Expected Behavior

Argosy launches as expected.

Actual Behavior

Argosy crashes until reinstall / app storage wipe.

Screenshots / Logs

Additional Context

Romm recently had an update so I wondered if communication with the main server could be the cause. Disabling internet access made no change.

[tmgast]

Did you restart during the startup process or after it landed on the home screen? My guess would be that your database got corrupted running migrations and it got stuck trying to write migrations that already were written but not marked as complete, causing it to crash during the migration preflight.

[Dasnap]

This is all after the setup, sitting on a stable homescreen. The first time this happened was with a setup that was about a week old. After that, I went through a fresh setup about 4 times and managed to trigger the corruption/crash loop each time. With my current setup I haven't triggered any forced restarts and haven't had a crash since making this issue.

Is there an easy way to get logs for the app? I'm willing to try and trigger it again to get a clearer cause for this.

[tmgast]

You can enable debug logs, but that's not going to catch this since it only outputs what I write to it... your issue is gonna require using adb to trace the system logs since this is a crash event.

Does it only happen with a forced shutdown or even with the power off option from the android system prompt (if you even have that show up)?

[Dasnap]

Only forced shutdown. Performing a normal shutdown is fine.

Just tested it again now. I've performed a normal shutdown and power on via the GUI, and the app was fine. I've then triggered a forced shutdown by holding in the power button, and the app will no longer open.

[tmgast]

Okay, I'll test doing that and see if I can sort it out.