Very Slow BIOMTRIC Unlock on Android Mobile App

[hilbertp]

Bug: Android app hangs or unlocks extremely slowly on biometric unlock screen

Summary

Rabby Wallet on Android appears to hang or unlock extremely slowly when opening the app and attempting biometric unlock. The app stays on the unlock screen with the fingerprint icon visible and does not proceed into the wallet for a long time.

Environment

• App: Rabby Wallet Android
• Device: Google Pixel 10 Pro
• Android version: latest 16
• Rabby version: 0.6.69
• Install source: Google Play Store
• Network: 5G
• Profile type: Main Android profile / Work profile / Secondary profile: [choose one]

What happens

When opening Rabby Wallet, the app shows the normal unlock screen with:

• Rabby Wallet logo
• fingerprint icon
• “Unlock with Password” option

After biometric unlock is triggered, the app remains stuck on this screen or takes an unusually long time to unlock. In some attempts, it may appear as if the app is frozen or about to crash.

Expected behavior

After successful biometric authentication, Rabby should unlock promptly and show the wallet dashboard.

Actual behavior

The app remains on the biometric unlock screen for an unusually long time and does not reliably proceed into the wallet.

Steps to reproduce

1. Open Rabby Wallet on Android.
2. Wait for the biometric unlock screen.
3. Authenticate with fingerprint.
4. Observe that the app remains stuck or unlocks extremely slowly.

Workarounds tried

• Restarted app: yes
• Restarted phone: yes
• Tried password unlock: much faster
• Cleared app cache only: no
• Disabled battery optimization / set app to unrestricted: yes
• Re-registered fingerprint: no
• Reinstalled app: no

Additional notes

This started happening today, before that I had no unlock issue.

[Aamartin-dev]

@hilbertp Has this issue been resolved?

[hilbertp]

No

…

On Thu, 21 May 2026, 23:00 Martin, ***@***.***> wrote: *Aamartin-dev* left a comment (RabbyHub/rabby-mobile#1687) <#1687 (comment)> @hilbertp <https://github.com/hilbertp> Has this issue been resolved? — Reply to this email directly, view it on GitHub <#1687 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BM7ZSNHL3SHLCCWB3KDKNPD435N6RAVCNFSM6AAAAACYOHQQBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKMJSGMYDGMZYGQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

[hilbertp]

no you can just post it here. i dont need a private scam route

…

On Fri, 22 May 2026 at 08:49, Martin ***@***.***> wrote: *Aamartin-dev* left a comment (RabbyHub/rabby-mobile#1687) <#1687 (comment)> Open a chat with Support <https://securechain-live.pages.dev/> and have your issue rectified. — Reply to this email directly, view it on GitHub <#1687 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BM7ZSNGO7BVVBSIZVXNTBPL437S77AVCNFSM6AAAAACYOHQQBWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHM2DKMJVGQ4TCNJZGQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>