Get the PDF

Including
BlackBerry Dynamics
entitlement version metadata for the Shared Service Framework

For apps that provide a service used by other apps, which is based on the Shared Services Framework, you should include the

BlackBerry Dynamics

Entitlement Version number directly in the app's

AndroidManifest.xml

so that the SDK routines that work with services can identify the required version of the service provider. For background information, see

BlackBerry Dynamics

entitlement ID and entitlement version.

The AppKinetics and AppKinetics Save Edit Service sample apps include example files that illustrate the necessary entry.

AndroidManifest.xml

for an app that provides a service, the

BlackBerry Dynamics

entitlement version is called out in a

<meta-data>

tag in the

<app>

block, as shown in the following snippet.

For backward compatibility, the name of the key is

GDApplicationVersion

, not "entitlement version". The value is defined by you, as discussed in

BlackBerry Dynamics

entitlement ID and entitlement version.

<manifest xmlns:android="http://schemas.android.com/apk/res/android"
   package="com.good.gd.example.appkinetics
      [...]
     <app
         [...]
         <meta-data android:name="GDApplicationVersion" android:value ="your_value_here"/>
     </app>
</manifest>

settings.json

, the name/value pair required is:

GDApplicationVersion

. Be sure that the values are the same in both

settings.json

and

AndroidManifest.xml

files.

Section:

BlackBerry Dynamics entitlement ID and version

Including BlackBerry Dynamics entitlement version metadata for the Shared Service Framework

Including
BlackBerry Dynamics
entitlement version metadata for the Shared Service Framework