-
Notifications
You must be signed in to change notification settings - Fork 39
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
Main Thread IO done on SDK initialization #320
Comments
Merged
Thanks for looking into this @thomaszurkan-optimizely! FWIW, this is causing some noticeable jank during our app startup. Is there an ETA for the fix? |
@quibi-jlk we should be doing a patch release soon. |
quibi-jlk
added a commit
to quibi-jlk/mparticle-android-integration-optimizely
that referenced
this issue
Mar 13, 2020
This version fixes a bad strictmode violation with many disk reads on the main thread. optimizely/android-sdk#320. See full diff here: optimizely/android-sdk@3.2.1...3.5.0
willpassidomo
pushed a commit
to mparticle-integrations/mparticle-android-integration-optimizely
that referenced
this issue
Mar 14, 2020
This version fixes a bad strictmode violation with many disk reads on the main thread. optimizely/android-sdk#320. See full diff here: optimizely/android-sdk@3.2.1...3.5.0
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Everytime the SDK initializes we get a bunch of strict mode violations.
It seems like the SDK is doing some IO in onPostExecute of an AsyncTask. It would be great if this IO could be done on a different thread so it doesn't slow down the user experience.
I've added the stack trace below.
The text was updated successfully, but these errors were encountered: