Skip to content

1.5.1
Compare
Choose a tag to compare
@thomaszurkan-optimizely thomaszurkan-optimizely released this 03 Nov 02:25
1.5.1
94ee813
This commit was signed with the committer’s verified signature. The key has expired.
thomaszurkan-optimizely Tom Zurkan
GPG key ID: 1F7D91425C572127
Expired
Learn about vigilant mode.

November 1, 2017

  • Release 1.5.1

New Features

  • Numeric metrics
  • Client-side programmatic forced variations.
  • Example of synchronous and asynchronous initialize in test-app

Bug Fixes

  • Remove Espresso dependency
  • Narrow proguard rules
  • Last modified fixed so that multiple project files can be used.
  • Call start listener if there is an exception.
  • Example of overriding Gson and android-logger in test-app gradle file.
  • Fix crash on API 17 (missing annotation).
  • Support for Android O (please see developer docs for details). Basically, Android O and above will use JobScheduler and pre Android O will continue to use AlarmService. This is done through a class called the JobWorkService which allows you to keep your Service and IntentService intact. Developers can piggyback on this method and keep thier IntentServices and use the JobWorkService.
  • Proguard rules were broken and were causing event payload to be stripped to single character keys.

Breaking Changes

  • Same as 1.4.0 see below.
  • Need to add permissions to both receivers in your manifest if you plan on using the EventRescheduler or the DatafileRescheduler (see test_app manifest for example) https://github.com/optimizely/android-sdk/blob/master/test-app/src/main/AndroidManifest.xml
  • Updated build tools and target to API 26 which will cause proguard warnings if you are not using the latest build tools.
  • Also for Android O, you must register for the SUPPLICANT_CONNECTION_CHANGE_ACTION intent filter in code (see the test-app for an example).
Assets 2
Loading