-
Notifications
You must be signed in to change notification settings - Fork 38
Bring back async init without the datafile. #211
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
Conversation
build |
2 similar comments
build |
build |
build |
got through the build phase, but failed for browserstack credentials reasons https://jenkins.dz.optimizely.com/job/sdk-compatibility-android/29/console |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think your description is wrong. It might also be helpful to mention that by passing in a resource you can guarantee that you will still get an optimizely instance.
* <p> | ||
* An {@link OptimizelyClient} instance will be delivered to | ||
* {@link OptimizelyStartListener#onStart(OptimizelyClient)}. The callback will only be hit | ||
* once. If there is a cached datafile the returned instance will be built from it. The cached |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This will cause the DatafileHandler to do an async task to return the most recent datafile from the cdn. If the file has not changed or there is some error, the cached file is used instead, if there is no cached datafile, then it will fail.
build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Can you make sure compatibility passes? |
build |
No description provided.