Cumulative release notes for Android mobile library.
To find the current library version, turn on debug logging.
The Android SDK version 4.13.4 (Feb 16, 2017) includes the following changes:
Fixed an issue preventing the proper app version to be used when determining an audience. This issue occurred when a user had an app version upgrade without a new Lifecycle launch.
Fixed an issue that could prevent an app version upgrade from being properly reported.
Fixed a bug that was causing deferred deep links to not be triggered on the first launch.
The Android SDK version 4.13.3 (Jan 19, 2017) includes the following changes:
Fixed an issue that prevented the display of alert messages with no click-through button.
Improved handling of read-only database access.
Fixed a bug that was causing deferred deep links attached to acquisition data to fire on successive launches.
The Android SDK version 4.13.2 (Nov 10, 2016) includes the following changes:
Visitor ID Service
Added timestamp and Marketing Cloud Organization ID to adobe_mc parameter.
When calling trackAdobeDeepLink , variables prefixed with " adb " and " ctx " are now handled properly.
The Android SDK version 4.13.1 (Oct 20, 2016) includes the following changes:
|The SDK now supports custom acquisition data to be returned appropriately by AdobeDataCallback invocations.|
|The SDK now stores Google Play Referrer variables and custom variables and returns them appropriately in AdobeDataCallback invocations.|
|Visitor ID Service parameters are now passed in Target requests via mboxParams .|
- Fixed a bug where data requests to the phone would sometimes timeout.
The Android SDK version 4.13.0 (Sept 15, 2016) includes the following changes:
New feature: Added a new message type that opens a deep link URI.
Tracking Deep Links
New feature: Added the ability to enable tracking of 3rd party deferred deep links.
The Android SDK version 4.12.0 (Aug 18, 2016) includes the following changes:
Visitor ID Service
Added new method to append visitor identity to a given URL in order to transfer identity to a web-based implementation.
The Android SDK version 4.11.0 (June 22, 2016) includes the following changes:
You can now use the following new Target method:
The Android SDK version 4.10.0 (May 20, 2016) includes the following changes:
Added new syntax and example for the loadRequest method.
Added the following new Target methods:
The Android SDK version 4.9.0 (May 5, 2016) includes the following changes:
|Opt-out and privacy settings|
You can implement deep linking in your applications to drive users to app or web link destinations.
The Android SDK version 4.8.3 (February 18, 2016) includes the following changes:
|Opt-out and privacy settings|
Starting with Android SDK 4.8.3, privacy settings set via the setPrivacyStatus method affect activity from Analytics , Target , and Audience Manager .
The Android SDK version 4.8.0 (November 2, 2015) includes the following changes:
|New Marketing Cloud Visitor ID Service methods|
Added the following methods:
|New ADBMobile JSON Config variable|
Added the following variable:
|PhoneGap Plugin methods|
Added the following new methods
Audience Manager Methods
Visitor ID Service Methods
The Android SDK version 4.6.1 (September 24, 2015) includes the following changes:
Android SDK version 4.6.1
SDK 4.6.0 or earlier supports Android 2.2(API 8) - Android 5.1.1 (API 22)
SDK 4.6.1 or later supports Android 2.3(API 9) or later
The Android SDK version 4.6 (September 17, 2015) includes the following changes:
Push Messaging to Analytics Segments
Adobe Mobile Services and the Adobe Mobile SDK allow you to send push messages to Analytics segments. The SDK also allows you to easily report users that have opened your app as a result of opening the push message.
Allows developers to start an app acquisition campaign as if the user had clicked a link. This is helpful for creating manual acquisition links and handling the app store redirect yourself.
Postbacks let you send data collected by the SDK to a separate third-party server. Leveraging the same triggers and traits you use to display an in-app message, you can configure the SDK to send customized data to a third-party destination.
Added the following new identifiers:
The Android SDK version 4.5 includes the following changes:
Android Wearable Extension
Starting in Android SDK version 4.5, a new Android extension lets you collect data from your Android Wearable app.
The Android SDK version 4.4 includes the following changes:
Custom data with lifecycle metrics
You can now include custom context data variables with lifecycle metrics.
Beacon tracking support in PhoneGap
The trackBeacon and clearCurrentBeacon calls are now available in PhoneGap .
Release Date: November 24, 2014
- New - Adobe Marketing Cloud ID integration
- Improved debug logs for clarity
- Resolved potential crash when checking for in-app messages
Release Date: October 16, 2014
- New - In App Messaging Capabilities.
- New - Location for config file can now be specified during app startup.
- New - Points of Interest can now be updated automatically without requiring a new config file.
- New - Analytics calls are now sent as HTTP POST requests.
- Resolved issue that could cause app crashes to not be tracked in certain scenarios.
- Cleared up log messages, added more verbose logging when debugLogging is enabled.
- Multiple performance and stability enhancements.
Release Date: August 4, 2014
- Resolved issue that could cause Lifecycle hit to not get sent when referrer timeout was >= 5 seconds and offline tracking was disabled.
Release Date: July 17, 2014
- Added protections around exceptions that occur if the database become corrupted, or could not be created.
- Added protections for issues that could occur when config cannot be loaded (generally due to a null context).
- Added protections for exceptions that could occur when updating the context data of a timed action.
Release Date: April 23, 2014
- Fixed a potential issue that could occur if referrer tracking is enabled and a tracking call is made prior to lifecycle.
Release Date: April 17, 2014
- New - Bluetooth beacon tracking.
- New - Apps that are timestamp enabled, crash hits are backdated to the correct session.
- New - Apps that are timestamp enabled, previous session is sent in a hit that is backdated to the correct session. (no longer previous session).
- New - Hit batching.
- Fixed google play referrer tracking with a configurable timeout to allow for delayed google referrer data.
- Resolved StrictMode warnings that could occur in specific scenarios.
- Resloved an issue that could very rarely cause the library to lock if certain methods were called in a specific order.
Release Date: February 24, 2014
- Resolved issue that could cause extended media time played if stop was called and close was called later with no calls in between.
- Resolved issue where a media close hit was sent even if the media was not played for any length of time.
Release Date: February 20, 2014
- Added safety to network code to prevent crash caused by Android bug: https://code.google.com/p/android/issues/detail?id=54072
Release Date: January 30, 2014
- Resolved issue that could cause multiple hits to be sent when database was corrupted.
- Resolved issue that could cause large session length averages if a device had incorrect time settings.
Release Date: 30 January, 2014
- Added protections against corrupted databases causing hits to repeat.
- Added max session length limit to avoid extremely large sessions when device times are incorrect.
Release Date: 14 November, 2013
- Resolved incorrect formatting of trackLocation data in specific locales.
Release Date: 27 September, 2013
Android SDK 4.x for Marketing Cloud Solutions is now available providing the following new features:
- Significant performance enhancements. All processing is performed on background threads, the SDK is fully thread safe.
- Geo-location & points-of-interest
- Lifetime value
- Timed events
- Opt-in/opt-out management
- Audience Manager Support
- Lifecycle metrics passed to Target as mbox parameters
- Standardized on context data and processing rules
Release Date: 23 September, 2013
- Fixed a bug in Audience Manager not allowing null values or keys in parameter.
Release Date: 12 September, 2013
- Fixed a bug where media events in linkTrackEvents were not added to the request.
- Fixed a potential exception related to ContextData being modified after being passed into a track call.
Release Date: 16 August, 2013
- SSL Connections now use strict host validation
- Fixed bug where hits would rapidly retry for a few seconds when network connection was lost and offlineTracking was disabled.
Release Date: 6 August, 2013
- Added support for Adobe Audience Manager.
- Lifecycle data is now sent with Target Mbox requests when lifecycle tracking is enabled.
- Resolved an issue that could cause SQLite to force close cursors, resulting in unnecessary log entries.
Release Date: 13 June, 2013
- Updated offline storage to use SQLite.
- Fixed a bug where offline limit could reset to default (1000).
- Updated startActivity to now accept an Activity or Application context.
- Fixed a bug where setting lifcycleSessionTimeout to 0 would result in multiple launch events throughout the app.
Release Date: 18 April, 2013
- Fixed encoding issue with some UTF8 characters.
Release Date: 18 April, 2013
- Fixed an issue that was causing previous session length to sometime be calculated incorrectly.
- New visitor IDs will no longer be based off of deviceID or subscriberID.
- Fixed a potential crash when encoding special characters in variables.
Release Date: 21 March, 2013
- Fixed issue where visitorID could not be read without setting it first.
- Changed naming conventions in some error log messages for clarity.
- Changed accessibility of multiple base classes to avoid confusion.
- Multiple performance enhancements
Release Date: 21 February, 2013
- Deprecated offlineThrottleDelay as the setting is no longer necessary due to thread optimization. The setting still exists to preserve backwards compatibility, but no longer has any effect.
- Fixed potential synchronization issue on offline hit cache.
- Clarified warning message when setting hierarchical vars over #5.
- Fixed issue that could cause OSVersion to be misreported on versions of Android > 4.0.
- Multiple performance enhancements.
- Resolved a potential exception that could be caused by a malformed url.
Release Date: November 2012
- Added a lifecycleSessionTimeout configuration variable that lets you specify the length of time, in seconds, that must elapse between app launches before the launch is considered a new session.
- Added ability to set the timeout value for the session length calculation, using a lifecycleSessionTimeout configuration setting.
- Fixed security issues.
Release Date: October 2012
- Added support for Google Play Campaign Tracking .
Release Date: September 2012
- Resolved an issue where close hits could sometimes cause a loop condition in media monitor.
Release Date: August 2012
- Context override parameters are now sent in as Hashmap<String, Object> (they were formerly Hashmap<String, String> ).
Release Date: July 2012
Previous Android Version (1.x)
The following release notes apply to the 1.x version of AppMeasurement for Android. We recommend customers upgrade to the 3.x version when possible.
Release Date: March 2012
- Fixed an issue that caused an exception in some circumstances when passing data using Context Data.
Release Date: February 2012
Fixed an issue that caused link tracking calls to double-URL-encode the pev1 - pev3 values.
Added time stamp to variables used with light tracking calls (trackLight).
Release Date: January 2012
- Added Android 3.x and 4.x compatibility.
- Implemented a UUID for visitor ID on Android devices that do not have SIM cards (For example, Kindle Fire).
Release Date: June 2011
- Updated the library to use the device ID for the visitor ID value when no SIM card is inserted in the device. By default the library uses the subscriber ID as the visitor ID which is not present if no SIM card is inserted.
Release Date: April 2011
- Support for all tablets including the Xoom.
- Ability to search report suites and metrics when running a report.
- Support for contextData that drives server-side processing rules (v15 only).
- Support for light server calls (currently in beta).