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
Using any Once method right when the application starts causes the entire thread to freeze. In my case, I'd like to use this library in my MainActivity to know if I should show the user an onboarding screen. However, calling Once.beenDone("seen_onboarding") caused a blank screen to be shown.
I was able to replicate this effect on a sample app quite easily with the following steps:
Call Once.initialise(this) in the app's Application class onCreate().
Call any Once method inside the MainActivity's onCreate().
Doing this will cause a blank screen. It's pretty straightforward but I can provide the sample app code if needed. This only happens in version 1.0.2 of the library. I'm guessing it's because the asynchronous loading never wakes up the thread that called it before it finished loading.
The text was updated successfully, but these errors were encountered:
Using any Once method right when the application starts causes the entire thread to freeze. In my case, I'd like to use this library in my MainActivity to know if I should show the user an onboarding screen. However, calling
Once.beenDone("seen_onboarding")
caused a blank screen to be shown.I was able to replicate this effect on a sample app quite easily with the following steps:
Once.initialise(this)
in the app's Application classonCreate()
.onCreate()
.Doing this will cause a blank screen. It's pretty straightforward but I can provide the sample app code if needed. This only happens in version 1.0.2 of the library. I'm guessing it's because the asynchronous loading never wakes up the thread that called it before it finished loading.
The text was updated successfully, but these errors were encountered: