Login issue on Android

Nobody has claimed this yet.

Describe the bug

On Android only, after the app autolocks (30 seconds), reopening MetaMask from the background causes the app to get stuck on the fox splash screen. The login/unlock page never appears, forcing the user to kill and relaunch the app.

This was first caught by a failing performance test scenario and confirmed manually.

Expected behavior

After the autolock triggers and the user reopens the app, the login/unlock screen should appear so the user can re-authenticate.

Screenshots/Recordings

https://github.com/user-attachments/assets/6c3a278d-bf72-4cf4-8e29-b555f624197b

Steps to reproduce
Open MetaMask on Android
Go to Settings and set Autolock to 30 seconds
Log in to MetaMask
Send MetaMask to the background
Wait more than 30 seconds (autolock triggers)
Reopen MetaMask
Observe the app is stuck on the fox splash screen — the login page never appears
The only recovery is to kill the app and reopen it
Error messages or log output

No error message displayed — app is silently stuck on the splash screen.

Where was this bug found?

Internal release testing

Version

TBD

Build number

TBD

Build type

No response

Device

Android device

Operating system

Android

Additional context
Android only — not reproduced on iOS
Originally detected via a failing performance test scenario
Autolock must be set to 30 seconds to reproduce
Severity

To be filled by internal support / PM

Start by reproducing the Android performance-test scenario with Autolock set to 30 seconds, then trace the app lifecycle and splash-to-login flow when returning from the background. Done means reopening after autolock consistently shows the login/unlock screen without requiring the app to be killed, with the relevant test covering the regression.

Written by the indexing model from the issue text.