Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • B B4S-Android-SDK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Francois Reboursier
  • B4S-Android-SDK
  • Wiki
  • Migration guide

Migration guide · Changes

Page history
Upgrade guide to 1.8 added authored Jan 15, 2016 by Eric Kok's avatar Eric Kok
Show whitespace changes
Inline Side-by-side
Migration-guide.md
View page @ 6ef8ebf9
...@@ -5,6 +5,12 @@ Please refer to each individual version step when migrating to a newer SDK. .x r ...@@ -5,6 +5,12 @@ Please refer to each individual version step when migrating to a newer SDK. .x r
The [[main integration document|Integration-guide]] always describes the most up-to-date integration requirements. The [[main integration document|Integration-guide]] always describes the most up-to-date integration requirements.
## Upgrade to 1.8.1
A Play Services support library was added in case you want to upgrade to the Play Services 8.4. Just use the `b4s-android-sdk-playservices840.aar` or -`.jar` file instead of the existing `playservicesXXX` variant.
Local logging was changed from a level-based to a feature-based distinction. To enable logging, now use the `B4SSetting.setShouldLogScan(boolean)` and `B4SSetting.setShouldLogMatching(boolean)` methods instead of `setShouldLogDebug` and `setShouldLogVerbose`. Scanning-related logs are reported using the `B4SSCN` tag, which campaign matching logs are still using the `B4S` tag. For example, to get all logs, use `adb logcat -s B4SSCN:* B4S:*` or to only get info and higher priority logs about campaign matching you can use `adb logcat -s B4S:I`.
## Upgrade to 1.7.0 ## Upgrade to 1.7.0
The dependencies were updated for stability and additional functionality. Note that there is now an additional `cupboard` dependency. For Eclipse builds, the required jar files can be found in the `/sample-eclipse/libs` folder. For Gradle builds, ensure you refer to the correct versions: The dependencies were updated for stability and additional functionality. Note that there is now an additional `cupboard` dependency. For Eclipse builds, the required jar files can be found in the `/sample-eclipse/libs` folder. For Gradle builds, ensure you refer to the correct versions:
...@@ -119,4 +125,3 @@ The `B4SSettings.storeCustomerFields()` method was slightly changed, as it is no ...@@ -119,4 +125,3 @@ The `B4SSettings.storeCustomerFields()` method was slightly changed, as it is no
android:exported="false" /> android:exported="false" />
``` ```
For push messaging integration itself, please refer to the [full integration document](https://github.com/ezeeworld/B4S-Android-SDK/blob/master/README.md#configure-the-sdk). For push messaging integration itself, please refer to the [full integration document](https://github.com/ezeeworld/B4S-Android-SDK/blob/master/README.md#configure-the-sdk).
Clone repository
  • Home
  • Installation with Eclipse Ant
  • Installation with Gradle
  • Integration guide
  • Migration guide