Our documentation is changing, please click here to enjoy it!

Skip to end of metadata
Go to start of metadata

    Migrate an existing application using Accengage SDK 3.5.x (or earlier) to the SDK 3.6.x

    SDK migration

    AndroidManifest.xml

    You need to remove the A4SService and all meta datas inside it from your application AndroidManifest.xml. This section is already defined for you in AndroidManifest.xml of the SDK.  

    AndroidManifest.xml

    Strings.xml

    Now the SDK configuration parameters (partnerId, privateKey, senderId, etc...) are located in the strings.xml file. So you need to move them from AndroidManifest.xml to strings.xml 

    strings.xml

    In the table presented below you can find string names of SDK parameters:

    Previous Meta-Data
    String name
    Default Value
    com.ad4screen.webview.script_url acc_webview_script_url  
    com.ad4screen.unsecurepush acc_unsecure_push true
    com.ad4screen.tracking_mode acc_tracking_mode normal
    com.ad4screen.senderid acc_sender_id  
    com.ad4screen.privatekey acc_private_key  
    com.ad4screen.partnerid acc_partner_id  
    com.ad4screen.notifications.icon acc_notification_icon  
    com.ad4screen.notifications.accent_color acc_notification_accent_color  
    com.ad4screen.no_geoloc acc_no_geoloc false
    com.ad4screen.logging acc_logging false
    com.ad4screen.location.priority acc_location_priority normal
    com.ad4screen.idsprovider acc_ids_provider  
    com.ad4screen.cache.delay acc_cache_delay 10
    com.ad4screen.advertiser_id acc_advertiser_id true

    Inbox

     Starting with 3.6.x version, Inbox tracking needs to be implemented by your self. If you already use Inbox feature and do nothing, no more statistics will be available. Please see our Inbox documentation.

    Plugins migration

    Beacons

    The new version of Accengage SDK 3.6.x is not compatible with the older version of Accengage Beacon Plugin 1.0.x plugin version. You need to upgrade the plugin to the version 1.1.0 or higher:

    build.gradle

     

     

    Upgrade from version 3.4.x to 3.5.x

    The version 3.5.x Android min-SDK is now 9 (2.3).

    build.gradle

    In your build.gradle, upgrade the android.defaultConfig.minSdkVersion to 9 if necessary:

     

    Using Google Play Services plugin

    The 3.0.1 Google Play Services Plugin is now splitted in 4 parts. AdvertiserId, Location and Push parts do not need any modification.

    If you use Geofences and upgrade from 2.x.x to 3.x.x you need to remove the following lines from your AndroidManifest.xml:

    Previous lines are now in the plugin manifest and will be automatically merged in your own AndroidManifest.

    Using custom notifications template

    If you use custom notifications template, widgets IDs changed:

    • com_ad4screen_sdk_logo -> com_ad4screen_sdk_notification_logo
    • com_ad4screen_sdk_title -> com_ad4screen_sdk_notification_title
    • com_ad4screen_sdk_body -> com_ad4screen_sdk_notification_body
    • com_ad4screen_sdk_picture -> com_ad4screen_sdk_notification_big_picture

     

    Upgrade from version 3.3.x to 3.4.x

    The version 3.4.x now supports only Android Studio. If you are still using Eclipse, please migrate to Android Studio. If it is not possible, please use an older version (like the 3.3.x).

    build.gradle

    Verify the applicationId is set in the project’s build.gradle file:

    Using GCM Push Notifications

    Remove the following lines from your AndroidManifest.xml:

    Previous lines will be automatically merged in your AndroidManifest.xml using the Manifest Merger.

    Using Google Play Services plugin

    The 3.4.x version is not compatible with older 1.6.x plugin versions. You need to upgrade to version 2.0.0. For this, add the following dependency:

    This version uses the InstanceID feature instead of deprecated GCM APIs. It means that you can register yourself to another Sender ID using InstanceID without conflicts with the Accengage Sender ID registration process.

    Using ProGuard

    If you are using ProGuard, the 3.4.x version includes Proguard rules in the AAR. You do not need to include them in your own rules.

    Using Beacons

    The 3.4.x version is not compatible with older 1.0.3 plugin version. You need to upgrade to version 1.0.4. For this, add the following dependency:

    Using Geofences

    Add the following lines in your AndroidManifest.xml file:

    • No labels