braze_plugin 3.1.0
braze_plugin: ^3.1.0 copied to clipboard
This is the Braze plugin for Flutter. Effective marketing automation is an essential part of successfully scaling and managing your business.
3.1.0 #
Breaking
- The native Android bridge uses Braze Android SDK 24.2.0.
- The native iOS bridge uses Braze iOS SDK 5.9.0.
- The minimum iOS deployment target is 11.0.
3.0.1 #
Fixed
- Updates the
braze_plugin.podspec
file to statically link the iOS framework by default. This prevents the need to do a manual step when migrating to3.x.x
. - Fixes an issue introduced in version
2.2.0
where the content cards callback was not being called when receiving an empty list of content cards.
3.0.0 #
Breaking
- The native iOS bridge now uses the new Braze Swift SDK, version 5.6.4.
- The minimum iOS deployment target is 10.0.
- During migration, update your project with the following changes:
- To initialize Braze, follow these integration steps to create a
configuration
object. Then, add this code to complete the setup:let braze = BrazePlugin.initBraze(configuration)
- To continue using
SDWebImage
as a dependency, add this line to your project's/ios/Podfile
:pod 'SDWebImage', :modular_headers => true
- Then, follow these setup instructions.
- For guidance around other changes such as receiving in-app message and content card data, reference our sample
AppDelegate.swift
.
- To initialize Braze, follow these integration steps to create a
Added
- Adds the
isControl
field toBrazeContentCard
.
Changed
- Updates the parameter syntax for
subscribeToInAppMessages()
andsubscribeToContentCards()
.
2.6.1 #
Added
- Adds support to replay the
onEvent
method for queued in-app messages and content cards when subscribing via streams.- This feature must be enabled by setting
replayCallbacksConfigKey: true
incustomConfigs
for theBrazePlugin
.
- This feature must be enabled by setting
Changed
- The native Android bridge uses Braze Android SDK 23.3.0.
- Updates the parameter type for
subscribeToInAppMessages()
andsubscribeToContentCards()
to accept aFunction
instead of avoid
.
2.6.0 #
Breaking
- The native Android bridge uses Braze Android SDK 23.2.0.
- The native iOS bridge uses Braze iOS SDK 4.5.1.
process(inAppMessage)
is renamed toprocessInAppMessage(inAppMessage)
in the iOS layer.
Added
- Adds the ability to subscribe to data for in-app messages and content cards via streams.
- Use the methods
subscribeToInAppMessages()
andsubscribeToContentCards()
, respectively.
- Use the methods
Changed
- Updates the iOS layer to use Swift.
BrazePlugin.h
andBrazePlugin.m
are now consolidated toBrazePlugin.swift
. - Deprecates
setBrazeInAppMessageCallback()
andsetBrazeContentCardsCallback()
in favor of the subscribing via streams.
2.5.0 #
Breaking
- The native Android bridge uses Braze Android SDK 21.0.0.
- Removes
logContentCardsDisplayed()
. This method was not part of the recommended Content Cards integration and can be safely removed.
Added
- Adds support for the SDK Authentication feature.
- To handle authentication errors, use
setBrazeSdkAuthenticationErrorCallback()
, and usesetSdkAuthenticationSignature()
to update the signature. When callingchangeUser()
, be sure to pass in thesdkAuthSignature
parameter. - Thanks @spaluchiewicz for contributing to this feature!
- To handle authentication errors, use
- Adds
setLastKnownLocation()
to set the last known location for the user.
2.4.0 #
Breaking
- The native Android bridge uses Braze Android SDK 20.0.0.
- Removes
setAvatarImageUrl()
.
Changed
- The native iOS bridge uses Braze iOS SDK 4.4.3.
2.3.0 #
Breaking
- The native Android bridge uses Braze Android SDK 17.0.0.
- The minimum supported Android SDK version is 19.
- Removes support for Android V1 Embedding APIs. Please reference the Flutter migration guide to update to the V2 APIs.
Added
- Custom events and purchases now support nested properties.
- In addition to integers, floats, booleans, dates, or strings, a JSON object can be provided containing dictionaries of arrays or nested dictionaries. All properties combined can be up to 50 KB in total length.
- Adds the ability to restrict the Android automatic integration from natively displaying in-app messages.
- To enable this feature, add this to your
braze.xml
configuration:
<string name="com_braze_flutter_automatic_integration_iam_operation">DISCARD</string>
- The available options are
DISPLAY_NOW
orDISCARD
. If this entry is ommitted, the default isDISPLAY_NOW
.
- To enable this feature, add this to your
Changed
- The native iOS bridge uses Braze iOS SDK 4.4.1.
2.2.0 #
Breaking
- The native Android bridge uses Braze Android SDK 16.0.0.
- The native iOS bridge uses Braze iOS SDK 4.4.0.
- Streamlines the Android integration process to not involve any manual writing of code to automatically register for sessions, in-app messages, or Content Card updates from the native SDK.
- To migrate, remove any manual calls to
registerActivityLifecycleCallbacks()
,subscribeToContentCardsUpdates()
, andsetCustomInAppMessageManagerListener()
. - To disable this feature, set the boolean
com_braze_flutter_enable_automatic_integration_initializer
tofalse
in yourbraze.xml
configuration.
- To migrate, remove any manual calls to
Added
- Adds the ability to set the in-app message callback and content cards callback in the constructor of
BrazePlugin
. - Adds the option to store any in-app messages or content cards received before their callback is available and replay them once the corresponding callback is set.
- To enable this feature, add this entry into the
customConfigs
map in the BrazePlugin constructor:replayCallbacksConfigKey : true
- Thank you @JordyLangen for the contribution!
- To enable this feature, add this entry into the
- Adds
BrazePlugin.addToSubscriptionGroup()
andBrazePlugin.removeFromSubscriptionGroup()
to manage SMS/Email Subscription Groups.
Fixed
- Fixes an issue in the iOS bridge where custom events without any properties would not be logged correctly.
2.1.0 #
Breaking
- The native iOS bridge uses Braze iOS SDK 4.3.2.
- The native Android bridge uses Braze Android SDK 15.0.0.
Added
- Adds
logContentCardsDisplayed()
to manually log an impression when displaying Content Cards in a custom UI.
2.0.0 #
Breaking
- Migrates the plugin to support null safety. All non-optional function parameters have been updated to be non-nullable unless otherwise specified. Read here for more information about null safety.
- Please reference the Dart documentation when migrating your app to null safety.
- Apps that have not yet migrated to null safety are compatible with this version as long as they are using Dart 2.12+.
- Thanks @IchordeDionysos for contributing!
- Passing through
null
as a value for user attributes is no longer supported.- The only attribute that is able to be unset is
email
by passing innull
intosetEmail
.
- The only attribute that is able to be unset is
- The methods
logEvent
andlogPurchase
now take an optionalproperties
parameter. - The native Android bridge uses Braze Android SDK 14.0.0.
- The minimum supported Dart version is
2.12.0
.
Changed
logEventWithProperties
andlogPurchaseWithProperties
are now deprecated in favor oflogEvent
andlogPurchase
.
1.5.0 #
Breaking
- The native iOS bridge uses Braze iOS SDK 4.0.2.
- The native Android bridge uses Braze Android SDK 13.1.2.
- The minimum supported Flutter version is 1.10.0.
Added
- Adds a public repository for the Braze Flutter SDK here: https://github.com/braze-inc/braze-flutter-sdk.
- We look forward to the community's feedback and are excited for any contributions!
1.4.0 #
Breaking
- The native Android bridge uses Braze Android SDK 13.0.0.
- The native iOS bridge uses Braze iOS SDK 3.34.0.
Added
- Adds
BrazePlugin.setGoogleAdvertisingId()
to set the Google Advertising ID and the associated Ad-Tracking Enabled field for Android. This is a no-op on iOS.
Fixed
- Fixes an issue where the Braze Android SDK's
Appboy.setLogLevel()
method wasn't respected.
1.3.0 #
Breaking
- The native Android bridge uses Braze Android SDK 12.0.0.
- The native iOS bridge uses Braze iOS SDK 3.31.0.
Added
- Adds support for the Braze plugin to be used with Android V2 Embedding APIs. Integrations using V1 Embedding will also continue to work.
- Allows the Android Braze plugin to be used with multiple Flutter engines.
1.2.0 #
Breaking
- The native iOS bridge uses Braze iOS SDK 3.30.0.
Added
- Allows the iOS Braze plugin to be used with multiple Flutter engines.
1.1.0 #
Breaking
- The native Android bridge uses Braze Android SDK 11.0.0.
- The native iOS bridge uses Braze iOS SDK 3.29.1.
1.0.0 #
Breaking
- The native iOS bridge uses Braze iOS SDK 3.27.0. This release adds support for iOS 14 and requires XCode 12. Please read the Braze iOS SDK changelog for details.
0.10.1 #
Changed
- The native iOS bridge uses Braze iOS SDK 3.26.1.
0.10.0 #
Breaking
- The native Android bridge uses Braze Android SDK 8.1.0.
- The native iOS bridge uses Braze iOS SDK 3.26.0.
Fixed
- Fixed an issue where
setBoolCustomUserAttribute
always set the attribute totrue
on iOS.
0.9.0 #
Breaking
- The native Android bridge uses Braze Android SDK 7.0.0.
- The native iOS bridge uses Braze iOS SDK 3.22.0.
0.8.0 #
Breaking
- The native iOS bridge uses Braze iOS SDK 3.21.3.
- The native Android bridge uses Braze Android SDK 4.0.2.
- If you are using a custom
IInAppMessageManagerListener
, then you will need to define new methods added to that interface in Braze Android SDK 4.0.0. See theMainActivity.kt
file of our sample app for a reference example.
- If you are using a custom
0.7.0 #
Added
- Added
BrazePlugin.launchContentCards()
andBrazePlugin.refreshContentCards()
to natively display and refresh Content Cards. - Adds a Dart callback for receiving Braze Content Card data in the Flutter host app.
- Similar to in-app messages, you will need to subscribe to Content Card updates in your native app code and pass Content Card objects to the Dart layer. Those objects will then be passed to your callback within a
List<BrazeContentCard>
instance. - To set the callback, call
BrazePlugin.setBrazeContentCardsCallback()
from your Flutter app with a function that takes aList<BrazeContentCard>
instance.- The
BrazeContentCard
object supports a subset of fields available in the native model objects, includingdescription
,title
,image
,url
,extras
, and more.
- The
- On Android, you will need to register an
IEventSubscriber<ContentCardsUpdatedEvent>
instance and pass returned Content Card objects to the Dart layer usingBrazePlugin.processContentCards(contentCards)
.- See the
MainActivity.kt
file of our sample app for a reference example.
- See the
- On iOS, you will need to create an
NSNotificationCenter
listener forABKContentCardsProcessedNotification
events and pass returned Content Card objects to the Dart layer usingBrazePlugin.processContentCards(contentCards)
.- See the
AppDelegate.swift
file of our sample app for a reference example.
- See the
- Similar to in-app messages, you will need to subscribe to Content Card updates in your native app code and pass Content Card objects to the Dart layer. Those objects will then be passed to your callback within a
- Added support for logging Content Card analytics to Braze using
BrazeContentCard
instances. SeelogContentCardClicked()
,logContentCardImpression()
, andlogContentCardDismissed()
on theBrazePlugin
interface.
0.6.1 #
Fixed
- Fixed an issue where the Braze Kotlin plugin file's directory structure did not match its package structure.
0.6.0 #
Changed
- The native Android bridge uses Braze Android SDK 3.8.0.
- Updated the native iOS bridge to Braze iOS SDK 3.20.4.
0.5.2 #
Important: This patch updates the Braze iOS SDK Dependency from 3.20.1 to 3.20.2, which contains important bugfixes. Integrators should upgrade to this patch version. Please see the Braze iOS SDK Changelog for more information.
Changed
- Updated the native iOS bridge to Braze iOS SDK 3.20.2.
0.5.1 #
Important This release has known issues displaying HTML in-app messages. Do not upgrade to this version and upgrade to 0.5.2 and above instead. If you are using this version, you are strongly encouraged to upgrade to 0.5.2 or above if you make use of HTML in-app messages.
Changed
- Updated the native iOS bridge to Braze iOS SDK 3.20.1.
0.5.0 #
Important This release has known issues displaying HTML in-app messages. Do not upgrade to this version and upgrade to 0.5.2 and above instead. If you are using this version, you are strongly encouraged to upgrade to 0.5.2 or above if you make use of HTML in-app messages.
Breaking
- The native iOS bridge uses Braze iOS SDK 3.20.0.
- Important: Braze iOS SDK 3.20.0 contains updated push token registration methods. We recommend upgrading to these methods as soon as possible to ensure a smooth transition as devices upgrade to iOS 13. In
application:didRegisterForRemoteNotificationsWithDeviceToken:
, replace
[[Appboy sharedInstance] registerPushToken:
[NSString stringWithFormat:@"%@", deviceToken]];
with
[[Appboy sharedInstance] registerDeviceToken:deviceToken]];
registerPushToken()
was renamed toregisterAndroidPushToken()
and is now a no-op on iOS. On iOS, push tokens must now be registered through native methods.
0.4.0 #
Breaking
- The native iOS bridge uses Braze iOS SDK 3.18.0.
- The native Android bridge uses Braze Android SDK 3.6.0.
Added
- Added the following new field to
BrazeInAppMessage
:zippedAssetsUrl
.- Note that a known issue in the iOS plugin prevents HTML in-app messages from working reliably with the Dart in-app message callback. Android is not affected.
0.3.0 #
Breaking
- The native iOS bridge uses Braze iOS SDK 3.15.0.
- The native Android bridge uses Braze Android SDK 3.5.0.
- Support for the Android configuration parameter
com_appboy_inapp_show_inapp_messages_automatically
has been removed.- To control whether an in-app message object should be displayed natively or not, create and register an instance of
IInAppMessageManagerListener
in your native Android code and implement decisioning in thebeforeInAppMessageDisplayed
method. SeeMainActivity
in our sample app for an example.
- To control whether an in-app message object should be displayed natively or not, create and register an instance of
- On Android, in-app message objects are no longer sent automatically to the Dart in-app message callback after calling
BrazePlugin.setBrazeInAppMessageCallback()
in your Dart code.- Similar to iOS, you will need to implement a delegate interface in your native app code and pass in-app message objects to the Dart layer for passing to the callback.
- On Android, the delegate interface is
IInAppMessageManagerListener
and the method for passing objects to Dart isBrazePlugin.processInAppMessage(inAppMessage)
. - See the sample
IInAppMessageManagerListener
implementation in theMainActivity.kt
file of our sample app for an example. - This approach gives the integrator more flexibility in deciding when a message should be displayed natively, discarded, or passed into the Dart layer.
Added
- Added support for logging in-app message analytics to Braze using
BrazeInAppMessage
instances. SeelogInAppMessageClicked
,logInAppMessageImpression
, andlogInAppMessageButtonClicked
on theBrazePlugin
interface.
0.2.1 #
Added
- Added the following new fields to
BrazeInAppMessage
:imageUrl
,useWebView
,duration
,clickAction
,dismissType
,messageType
- Added the following new fields to
BrazeButton
:useWebView
,clickAction
.
0.2.0 #
Breaking
- The native iOS bridge uses Braze iOS SDK 3.14.0.
- The native Android bridge uses Braze Android SDK 3.2.1.
Added
- Adds
addAlias()
to the public API interface. - Adds
requestLocationInitialization()
to the public API interface. - Adds
getInstallTrackingId()
to the public API interface. - Adds support for disabling native in-app message display on Android.
- To disable automatic in-app message display, create a boolean element named
com_appboy_inapp_show_inapp_messages_automatically
in your Android app'sappboy.xml
and set it tofalse
. - Note: Disabling automatic in-app message display was already possible for iOS. For instructions, see
README.md
.
- To disable automatic in-app message display, create a boolean element named
- Adds a Dart callback for receiving Braze in-app message data in the Flutter host app.
- Analytics are not currently supported on messages displayed through the callback.
- To set the callback, call
BrazePlugin.setBrazeInAppMessageCallback()
from your Flutter app with a function that takes aBrazeInAppMessage
instance.- The
BrazeInAppMessage
object supports a subset of fields available in the native model objects, includinguri
,message
,header
,buttons
, andextras
.
- The
- The callback should begin to function on Android immediately after being set.
- On iOS, you will additionally need to implement the
ABKInAppMessageControllerDelegate
delegate as described in our public documentation. YourbeforeInAppMessageDisplayed
delegate implementation must callBrazePlugin.process(inAppMessage)
. For an example, seeAppDelegate.swift
in our example app.
0.1.1 #
- Formatted
braze_plugin.dart
.
0.1.0 #
- Removes the unused
dart:async
import inbraze_plugin.dart
. - Makes
_callStringMethod
private inbraze_plugin.dart
. - Adds basic dartdoc to the public API interface.
0.0.2 #
- Updates the version of Kotlin used by the Android plugin from
1.2.71
to1.3.11
.
0.0.1 #
- Initial release.
- The native iOS bridge uses Braze iOS SDK 3.12.0.
- The native Android bridge uses Braze Android SDK 3.1.0.