Skip to content
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

Black Screen after unlocking Database #1342

Closed
SomaKhaos opened this issue Apr 1, 2024 · 7 comments
Closed

Black Screen after unlocking Database #1342

SomaKhaos opened this issue Apr 1, 2024 · 7 comments
Labels
bug A bug report bug-confirmed A confirmed and reproducible bug report

Comments

@SomaKhaos
Copy link

Version

3.0.1

Source

Google Play

Vault encryption

Yes (with biometric unlock)

Device

Pixel 7

Android version

Android 14

ROM

No response

Steps to reproduce

I open the app, use my fingerprint to unlock my vault. It takes like 1-2 seconds and then there's just a black screen instead of my vault. i then have to minimzie the app and then maximize again to aegis again, to see my vault

What do you expect to happen?

Unlock the Vault per fingerprint and showing me my vault.

What happens instead?

Screen turns black and i have to reopen the app to see my vault

Log

No response

@SomaKhaos SomaKhaos added the bug A bug report label Apr 1, 2024
@michaelschattgen
Copy link
Member

michaelschattgen commented Apr 1, 2024

Thank you for the report. I've been seeing the same strange behaviour on my Pixel with Android 14 as well. I'm 100% sure it's because of the Android version but I haven't figured out what the cause is yet.

EDIT: Also would like to add that usually a restart of my phone solves the issue for me (for a while).

@michaelschattgen michaelschattgen added the bug-confirmed A confirmed and reproducible bug report label Apr 1, 2024
@alexbakker
Copy link
Member

@SomaKhaos Could you share the build number of the Android version that you're running?

@SomaKhaos
Copy link
Author

@alexbakker sure it's AP21.240216.010

@SomaKhaos
Copy link
Author

Update: Updated this morning to build AP21.240305.005. So far everything is working as intented again. Seems like the Problem is the other build.

@michaelschattgen
Copy link
Member

I was just about to report the same. Updated this morning too and haven't been able to reproduce this since. I'm closing this issue for now with the assumption that it was caused by the previously mentioned Android build. Feel free to tell us to re-open this issue whenever you run into this again.

@michaelschattgen michaelschattgen closed this as not planned Won't fix, can't repro, duplicate, stale Apr 2, 2024
@michaelschattgen
Copy link
Member

Reopening this issue. This bug just occurred on my Pixel 7 Pro running AP21.240305.005.

@michaelschattgen
Copy link
Member

Closing this issue once again since this hasn't happened to me once after upgrading to AP31.240322.027 3 weeks ago. Please tell us when you're running into the same bug again (on previously mentioned Android beta version or newer).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A bug report bug-confirmed A confirmed and reproducible bug report
Projects
None yet
Development

No branches or pull requests

3 participants