... | ... | @@ -30,6 +30,20 @@ If multiple B4S apps are installed, the SDK will now automatically choose the mo |
|
|
|
|
|
## Upgrade to 1.5.0
|
|
|
|
|
|
The dependencies were updated for better compatibility with recent Play Services and stability. For Eclipse builds, the required jar files can be found in the /sdk/libs folder. For Gradle builds, ensure you refer to the correct versions:
|
|
|
|
|
|
```gradle
|
|
|
dependencies {
|
|
|
compile 'de.greenrobot:eventbus:2.3.0'
|
|
|
compile 'com.squareup.retrofit:retrofit:2.0.0-beta1'
|
|
|
compile 'com.squareup.retrofit:converter-jackson:2.0.0-beta1'
|
|
|
compile 'com.google.android.gms:play-services-location:8.1.0'
|
|
|
compile 'com.google.android.gms:play-services-ads:8.1.0'
|
|
|
compile "com.google.android.gms:play-services-gcm:8.1.0"
|
|
|
compile fileTree(dir: 'libs', include: ['*.jar'])
|
|
|
}
|
|
|
```
|
|
|
|
|
|
It is no longer necessary (nor should you) to extend from the `B4SNotificationActivity` or manage a `B4SNotificationPopup` manually. Please remove manual references to these class from your code. Not that, as part of this change, you DO have to supply your `Application` object to the `B4SSettings.init(Application, String)` method.
|
|
|
|
|
|
The deep linking intent extra field constants, such as `INTENT_TITLE` and `INTENT_ACTIONID`, were moved from the `MonitoringManager` to the `NotificationService` class.
|
... | ... | |