Changelog
Check out release history for stable releases of android SDKs. Stable releases have been tested thoroughly and are ready for use in your production apps. Major versions may include breaking changes. See our migration guide for help updating your SDK integration to take advantage of new features and fixes.
Need to upgrade?
Select your current version to see all the features and fixes from your version to the latest release.
Breaking Changes
Features
Bug Fixes
4.x Releases
4.1.0
code changes4.0.1
code changes4.0.0
code changes⚠ BREAKING CHANGES
- Data Pipelines Support: Sending your mobile data into our customer data platform (CDP) helps you support both Journeys and the rest of your martech stack—analytics, data warehouses, CRMs and more. (#412) (772b489)
Features
- Anonymous tracking: You can send anonymous events, and we’ll reconcile anonymous activity with your users when you identify them.
- Built-in lifecycle events: the SDK now automatically captures events like “Application Installed” and “Application Updated” for you, so you better understand your users’ behaviors in your app. (#334) (9d239c8)
- New device data: the SDK captures complete device-level context, like your audience’s screen dimensions, device names, and more. (#341) (7cb17c1)
3.x Releases
3.11.2
code changesBug Fixes
- Resolves an issue that caused the SDK version to be reported as the previous version for versions 3.3.0 - 4.0.0. (38b2815)
3.11.1
code changesBug Fixes
- Messages created in the new drag and drop in-app editor will load much faster and don’t require pre-fetching assets. If you are using the older in-app editor, the initial in-app message may experience a delay. We highly recommend upgrading to the new in-app editor to avoid this issue and ensure optimal performance. (#393) (8c8ee89)
- This update also resolves an issue that was causing crashes during the pre-fetching step in certain situations.
3.11.0
code changesFeatures
- When using page rules and when an in-app messages need a second to load, the in-app message might appear after a user navigates to another page. We made changes to ensure the page-rules are checked after the message is loaded and immediately before it’s displayed in order to resolve this issue.
- We resolved a caching issue that in rare cases, caused users to see the incorrect in-app message when logging out then logging back in as a different user.
3.10.0
code changes3.9.2
code changes3.9.1
code changes3.9.0
code changes3.8.2
code changes3.8.1
code changes3.8.0
code changes3.7.1
code changes3.7.0
code changes3.6.7
code changes3.6.6
code changes3.6.5
code changes3.6.4
code changes3.6.3
code changes3.6.2
code changes3.6.1
code changesBug Fixes
Note: We’ve made updates to our installation instructions. Please refer to them as they reflect our new streamlined process which no longer necessitates a previously required dependency for in-app messages.
3.6.0
code changes3.5.3
code changes3.5.2
code changes3.5.1
code changes3.5.0
code changes3.4.3
code changes3.4.2
code changes3.4.1
code changes3.4.0
code changes3.3.2
code changes3.3.1
code changes3.3.0
code changesFeatures
- add setting a in-app event listener (#147) (5fd9559)
- in-app feature no longer requires orgId (#163) (fc2a08e)
Bug Fixes
- image not shown when image url in notification payload (#172) (0abdc85)
- moved shared wrapper code (#158) (51af98f)
- remove currentRoute parameter in in-app event listener (#159) (688e4a5)
- rename in app listener keys (#164) (f540eaf)
- set gist dependency to use latest 3.X.Y version (#170) (a019c36)
- set gist user token incase identifier exists (#162) (44cc4d1)
- update CustomerIOFirebaseMessagingService to open (#174) (edce7f5)
- upgrade dependencies (#146) (6da8b8d)
- use maven style dependency range syntax (#171) (ba83214)
3.2.0
code changes3.1.1
code changes3.1.0
code changes3.0.0
code changes
2.x Releases
2.1.1
code changesBug Fixes
- parsing exception for expired tasks (440bb13)
2.1.0
code changes2.0.1
code changesBug Fixes
- track opens fcm notification payload (ab3cd18)
2.0.0
code changes⚠ BREAKING CHANGES
- get current FCM token on SDK startup
- register device attributes when set
- create background queue to make API synchronous
Features
- add device and profile attribute setters (789f09f)
- add device_manufacturer device attribute (6a60f39)
- added support for custom track url (b61a64b)
- added support for device attributes (#71) (5fedf26)
- create background queue to make API synchronous (2524460)
- get current FCM token on SDK startup (dda443d)
- register device attributes when set (0f5159e)
- set log level via SDK config (81eea4e)
- support for custom device attributes and config (#77) (a7dbaba)
Bug Fixes
- added java compatibility in public constructors and methods (acdec46)
- added support for big decimal (#56) (58c791b)
- code cleanup (c651ee6)
- delete device token when clear identify (72f9753)
- events are tracked to identified customer (71634ed)
- queue attempts to run all tasks on each run (e180dea)
- register device tokens http request (b1c6872)
1.x Releases
1.0.5
code changes1.0.4
code changes1.0.3
code changes1.0.2
code changesBug Fixes
- added java compatibility in public constructors and methods (2bb73be)
1.0.1
code changes1.0.0
code changes