Skip to content

Releases: customerio/customerio-android

4.5.0

17 Dec 20:14
Compare
Choose a tag to compare

4.5.0 (2024-12-17)

Features

  • Added ability to disable forwarding screen events to destinations/servers. Apps can still send screen events for local processing and use them for page rules in in-app messages by just updating SDK configuration during initialization. Learn more about screen configuration options here. (#474) (b5ea8e9)

Fixes

  • Handle the case where the user identifier would be set to an empty string, if profile attributes were updated before identifying the profile. #476

4.4.1

29 Nov 08:07
Compare
Choose a tag to compare

4.4.1 (2024-11-29)

Bug Fixes

  • Fixes issue with loading legacy editor messages (#469) (ecd89dd)

4.4.0

13 Nov 10:51
Compare
Choose a tag to compare

4.4.0 (2024-11-13)

Features

  • This release introduces support for displaying larger in-app messages. (#456) (b8331bf)

Internal

  • Updated our SDK to use the v2 version of our in-app messages API. This will provide a more reliable experience for in-app messages. (#461)

Note:

This is only supported for the new in-app editor, if you are using the legacy in-app editor, it is recommended NOT to upgrade to this release for now.

4.3.0

16 Oct 16:23
Compare
Choose a tag to compare

4.3.0 (2024-10-16)

Improvement

  • This release includes changes needed to support for data pipelines in the our React Native SDK. There are no new features for customers utilizing our native Android SDK only.

4.2.0

11 Sep 08:58
Compare
Choose a tag to compare

4.2.0 (2024-09-11)

Features

  • Revamped the in-app messaging module to enhance performance by optimizing local processing, accelerating message loading during page transitions, and implementing a state-driven architecture for better responsiveness and control. (#431) (682ac42)
  • We highly recommend upgrading to the new in-app editor to ensure optimal performance.

Fixes

  • We reduced the chance of duplicate in-app messages by keeping a local store of messages already displayed.
  • Resolves an issue with tracking attributes for certain in-app messages.
  • Fixes an intermittent crash on initialization. #426
  • Resolves an application not responding (ANR) issue. #147

3.11.2

19 Aug 21:03
Compare
Choose a tag to compare

3.11.2 (2024-08-19)

Bug 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)

4.1.0

09 Aug 21:13
Compare
Choose a tag to compare

4.1.0 (2024-08-09)

Features

  • Ability to dismiss current in-app message. Currently displayed message can now be dismissed using CustomerIO.instance().dismissMessage() (#420) (8bfc37d)
  • Improved logs around in-app messaging to provide more clarity on state changes and actions performed on in-app messages (#421) (8bfc37d)

4.0.1

25 Jul 00:06
Compare
Choose a tag to compare

4.0.1 (2024-07-25)

Bug Fixes

  • Resolves an issue that caused the SDK version to be reported as the previous version for versions 3.3.0 - 4.0.0. (#415) (1358719)

4.0.0

24 Jul 17:30
Compare
Choose a tag to compare

4.0.0 (2024-07-24)

⚠ 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.11.1

15 Jul 22:54
Compare
Choose a tag to compare

3.11.1 (2024-07-15)

Bug 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.