Skip to content

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

Merged
merged 4 commits into from
Jul 31, 2018

Conversation

mikeproeng37
Copy link
Contributor

No description provided.

@mikeproeng37
Copy link
Contributor Author

build

2 similar comments
@tylerbrandt
Copy link

build

@mikeproeng37
Copy link
Contributor Author

build

@tylerbrandt
Copy link

build

@tylerbrandt
Copy link

got through the build phase, but failed for browserstack credentials reasons https://jenkins.dz.optimizely.com/job/sdk-compatibility-android/29/console

Copy link
Contributor

@thomaszurkan-optimizely thomaszurkan-optimizely left a 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
Copy link
Contributor

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.

@tylerbrandt
Copy link

build

Copy link
Contributor

@thomaszurkan-optimizely thomaszurkan-optimizely left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@thomaszurkan-optimizely
Copy link
Contributor

Can you make sure compatibility passes?

@thomaszurkan-optimizely
Copy link
Contributor

build

@mikeproeng37 mikeproeng37 merged commit 08bf693 into master Jul 31, 2018
@mikeproeng37 mikeproeng37 deleted the mng/revive-async-no-datafile branch January 15, 2019 22:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants