You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Exception java.lang.IllegalStateException: SharedPreferences in credential encrypted storage are not available until after user is unlocked
at android.app.ContextImpl.getSharedPreferences (ContextImpl.java:562)
at android.app.ContextImpl.getSharedPreferences (ContextImpl.java:547)
at android.content.ContextWrapper.getSharedPreferences (ContextWrapper.java:196)
at com.google.android.gms.internal.appset.zzl.zzf (com.google.android.gms:play-services-appset@@16.0.0:1)
at com.google.android.gms.internal.appset.zzl.zzd (com.google.android.gms:play-services-appset@@16.0.0:1)
at com.google.android.gms.internal.appset.zzh.run
at java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1137)
at java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:637)
at java.lang.Thread.run (Thread.java:1012)
Expected Behavior
No Crash
Additional Info
It seems like this is happening when the notification system signs up during boot, before the user unlocked his device. (source). Looking at the manifest of this it is exactly what is happening (here, and here)
Is it possible to disable these manifest values without forking the whole repository?
The text was updated successfully, but these errors were encountered:
Is it somehow possible to disable the "directBoot" awareness without forking the whole repository? Nobody else having an production app and is seeing this issue?
Bug Report
Plugin(s)
Capacitor Version
Platform(s)
Current Behavior
The following Crash is reported to the Google Play Console
with the stacktrace
Expected Behavior
No Crash
Additional Info
It seems like this is happening when the notification system signs up during boot, before the user unlocked his device. (source). Looking at the manifest of this it is exactly what is happening (here, and here)
Is it possible to disable these manifest values without forking the whole repository?
The text was updated successfully, but these errors were encountered: