Skip to content

chore: prepare for 3.5.0 #324

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.

Sign up for GitHub

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 1 commit into from
Mar 13, 2020
Merged

chore: prepare for 3.5.0 #324

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,24 @@
# Optimizely Android X SDK Changelog

## 3.5.0
March 13th, 2020

This release includes an enhancement of SDK initialization API to enable SDK updated on cached datafile change. It also fixes known bugs.

### New Features
* Add an option for **synchronous** initialization to enable SDK immediately updated when a new datafile is cached. Unless this feature is enabled, by default, the cached datafile will be used only when the SDK re-starts in the next session. Note that this option is for **synchronous** initialization only. ([#318](https://github.com/optimizely/android-sdk/pull/318))

```
// enable SDK update when a new datafile is cached
optimizelyManager.initialize(context, R.raw.datafile, true, true)

// by default, this feature is disabled
optimizelyManager.initialize(context, R.raw.datafile)
```

### Bug Fixes
* When datafile download fails or receives 304, the SDK loads a datafile from cache. This loading process is moved to a background thread. ([#321](https://github.com/optimizely/android-sdk/pull/321))

## 3.4.0
January 31st, 2020

Expand Down