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
Updated Migration guide (markdown) authored Dec 14, 2015 by Eric Kok's avatar Eric Kok
Show whitespace changes
Inline Side-by-side
Migration-guide.md
View page @ 2c5cbe45
......@@ -5,6 +5,17 @@ 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.
## Upgrade to 1.6.1
When using the .JAR release with manual declarations in your `AndroidManifest.xml`, ensure that the GCM `permission` and `uses-permission` include your unique package name (instead of the placeholder `<YOUR-PACKAGE-NAME>`):
```
<permission
android:name="<YOUR-PACKAGE-NAME>.permission.C2D_MESSAGE"
android:protectionLevel="signature" />
<uses-permission android:name="<YOUR-PACKAGE-NAME>.permission.C2D_MESSAGE" />
````
The .AAR version (with Gradle) automatically injects the proper application id in the permission name, starting with this release.
## Upgrade to 1.6.0
The SDK was split into a core part and a connection part specific to the Play Services library that the application wants to use. This allows, for example, to stay at Play Services 6.5 while still upgrading to the latest B4S version.
......
Clone repository
  • Home
  • Installation with Eclipse Ant
  • Installation with Gradle
  • Integration guide
  • Migration guide