Open SomaKhaos opened 3 months ago
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).
@SomaKhaos Could you share the build number of the Android version that you're running?
@alexbakker sure it's AP21.240216.010
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.
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.
Reopening this issue. This bug just occurred on my Pixel 7 Pro running AP21.240305.005.
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).
Just had it happen to me. Solved by reboot.
Aegis 3.0.1 Pixel 7 AP2A.240605.024
I'm afraid the Google Pixel June update that came out a little over a week ago reintroduced this bug... I'm opening this issue again, although I'm not sure yet whether it's possible to fix this on our end or we'll have to wait for Google to release a fix.
I'm running through this bug and I have the latest app and OS version too: https://github.com/beemdevelopment/Aegis/issues/1398
Nor Updating, nor rebooting worked.
Running into this issue now (on Pixel 6a). Is there any workaround for me to see my tokens in the meantime as I'll locked out without having access to the 2fa tokens
EDIT: A reboot for me (at least for now) fixes the issue
A log captured while reproducing the issue would be much appreciated: https://github.com/beemdevelopment/Aegis/blob/master/CONTRIBUTING.md#capturing-a-log-with-adb
I was able to find a workaround on my Pixel 6 Pro. When the screen goes black, go back to the home screen, then re-open the app. The tokens are then visible.
Attached debug log file. The steps I performed were to launch the app, immediately begin capturing the Aegis debug log, exited biometric unlock, re-initiating biometric unlock, getting the black screen, waiting, going back to the home screen, then re-opening the app which then showed the tokens.
New to the app, and I have experienced this bug twice within the past 2 weeks. Pixel 8 Pro June patch. Restarting my device has worked so far.
@bickman2k Thanks, but we're going to need the full capture without the Aegis filter in order to get enough information. If you're not comfortable sharing the log publicly, feel free to share it with us via email privately.
I can pull another log in a couple of days as I'm camping right now. I can email it when it is pulled.
@alexbakker also got the blackscreen when opening Aegis (v3.1) latest update from he playstore. The previous version had the same issue.
Running lineageos android 14 latest build Ap2a 240605.025 Los: 21-20240626-NIGHTLY-enchilada On my oneplus6
When i open Aegis, unlock it with fingerprint, i got a blackscreen (no info visable)
Force close aegis, clear cache doesn't fix it.
(Tried to open aegis with passwordphrase also does't work, still got a black screen. Also when openening the app en go back to home screen does't solve it.) Only a reboot of the device will allow me to open aegis with succes... But only temporary)
I'm also still receiving this problem
Do you guys still need a log or something?
Yes please.
Just sent one via mail. Let me know if you need anything else.
So either the reboot or the just released and installed July update seems to have fixed it for me, at least for now. Can anybody else confirm that?
I don't have the July update .. but I haven't hit the issue again since the first time.
What I have done differently since the first time is removing usage of fingerprint auth and only using manual password entry.
So either the reboot or the just released and installed July update seems to have fixed it for me, at least for now. Can anybody else confirm that?
There's a big chance the July update fixed the issue. I was running an Android 14 beta update back in april which introduced this bug for me, then suddenly a new beta version fixed it again. Hopefully we're going to see more reports about the July update fixing this weird behaviour.
What I have done differently since the first time is removing usage of fingerprint auth and only using manual password entry.
Yeah I was already expecting the biometrics auth popup causing this issue. Glad you found a workaround!
I was on the June update and it only happened to me twice.
It seems after rebooting the latest aegis update the problem doesn't accure (3days without a problem) fingers crossed
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