Releases · customerio/customerio-flutter

10 Dec 21:40

2.0.0 Latest

Latest

2.0.0 (2024-12-10)

Data Pipelines Support: Sending your mobile data into our customer data platform (CDP) helps you support Journeys and the rest of your martech stack—analytics, data warehouses, CRMs, and more. (#187)

NOTE: Please follow the migration guide for a seamless upgrade to this version.

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.
New device data: The SDK captures complete device-level context, such as your audience’s screen dimensions, device names, and more.

Resolves an issue where the user agent for events was labeled as coming from the iOS SDK instead of the Flutter SDK.

Assets 2

06 Sep 12:15

1.5.2

Updates Android Native dependency from 3.11.0 to 3.11.2 which includes following improvements.

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. [#139] (b10cc75)

Fixed crash that could occur on some Android devices during asset pre-fetching step in certain situations. [#139] (b10cc75)
Resolved an issue where calling CustomerIO.MessagingInApp().dismissMessage() explicitly would print crash logs on Android. The method can now be called safely without unnecessary logs. [#142] (1635acf)

Assets 2

01 Aug 17:33

1.5.1

Resolved an issue where the native iOS code communicated to the Flutter code on a non-platform thread. This change ensures that platform channel messages are sent on the correct platform thread, preventing potential data loss or crashes. (#134) (bc8704b)

Assets 2

02 Jul 17:00

1.5.0

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.(#131) (a563055)

Assets 2