6.0.1

Fixed

• Updates the native Android bridge from Braze Android SDK 26.1.0 to 26.1.1.

6.0.0

Breaking

• Updates the native Android bridge from Braze Android SDK 25.0.0 to 26.1.0.

Fixed

• Fixes an issue where BrazeContentCard.imageAspectRatio would always return 1 for whole-number int values.
  • The field imageAspectRatio is now a num type instead of a double type. No changes are required.

Added

• Added support for Braze Feature Flags.
  • BrazePlugin.getFeatureFlagByID(String id) - Get a single Feature Flag
  • BrazePlugin.getAllFeatureFlags() - Get all Feature Flags
  • BrazePlugin.refreshFeatureFlags() - Request a refresh of Feature Flags
  • BrazePlugin.subscribeToFeatureFlags(void Function(List<BrazeFeatureFlag>) onEvent)) - Subscribe to Feature Flag updates
  • Feature Flag property getter methods for the following types:
    • Boolean: featureFlag.getBooleanProperty(String key)
    • Number: featureFlag.getNumberProperty(String key)
    • String: featureFlag.getStringProperty(String key)
• Updates the native iOS bridge from Braze iOS SDK 6.0.0 to 6.3.0.

5.0.0

Breaking

• The native Android bridge uses Braze Android SDK 25.0.0.
• The native iOS bridge uses Braze iOS SDK 6.0.0.

4.1.0

Fixed

• Fixes an issue in 4.0.0 where the version in braze_plugin.podspec was not incremented correctly.

Changed

• The native iOS bridge uses Braze iOS SDK 5.12.0.

4.0.0

Starting with this release, this SDK will use Semantic Versioning.

Breaking

• Fixes the behavior in the iOS bridge introduced in version 3.0.0 when logging clicks for in-app messages and content cards. Calling logClick now only sends a click event for metrics, instead of both sending a click event as well as redirecting to the associated url field.
  • For instance, to log a content card click and redirect to a URL, you will need two commands:

  braze.logContentCardClicked(contentCard);
  
  // Your own custom implementation
  Linking.openUrl(contentCard.url);
  

  • This brings the iOS behavior to match version 2.x and bring parity with Android's behavior.
• Removes setBrazeInAppMessageCallback() and setBrazeContentCardsCallback() in favor of subscribing via streams.
  • Reference our sample app for an example on how to use subscribeToInAppMessages() or subscribeToContentCards().

Changed

• The native Android bridge uses Braze Android SDK 24.3.0.
• The native iOS bridge uses Braze iOS SDK 5.11.2.
• Improves behavior when using replayCallbacksConfigKey alongside having subscriptions to in-app messages or content cards via streams.

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 to 3.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.

Added

• Adds the isControl field to BrazeContentCard.

Changed

• Updates the parameter syntax for subscribeToInAppMessages() and subscribeToContentCards().

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 in customConfigs for the BrazePlugin.

Changed

• The native Android bridge uses Braze Android SDK 23.3.0.
• Updates the parameter type for subscribeToInAppMessages() and subscribeToContentCards() to accept a Function instead of a void.

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 to processInAppMessage(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() and subscribeToContentCards(), respectively.

Changed

• Updates the iOS layer to use Swift. BrazePlugin.h and BrazePlugin.m are now consolidated to BrazePlugin.swift.
• Deprecates setBrazeInAppMessageCallback() and setBrazeContentCardsCallback() in favor of the subscribing via streams.