@braze/expo-plugin - npm Package Versions

2.1.2

Fixed

• Fixes the sample app to contain examples on configuring app extension build settings for Expo Application Services (EAS).

2.1.1

Fixed

• Tentative fix for code-signing notification extensions on iOS when using Expo Managed Workflow and Expo Application Services (EAS).

2.1.0

Added

• Adds support for Rich Push notifications and Push Stories.
  • Set enableBrazeIosRichPush to true in your app.json to enable Rich Push notifications.
  • Set enableBrazeIosPushStories to true and configure your app group name with iosPushStoryAppGroup in your app.json to enable Push Stories.
  • For further integration details, refer to the native Swift SDK instructions for Rich Push Notifications and Push Stories.

2.0.0

Breaking

• Bumps the iOS minimum platform version to 13.4, per the Expo SDK 50 requirements.
• This version requires version 8.3.0+ of the Braze React Native SDK to fully support Expo SDK 50.

Fixed

• Fixes Android compatibility with Expo SDK 50.
  • This release removes strict dependencies on Java 11 from the build.gradle file.
  • This fix adds namespacing and buildFeatures.buildConfig for compatibility with Android Gradle Plugin 8+.

1.2.0

Added

• Updates the enableBrazeIosPush configuration to use the automatic push handling features from the Braze Swift SDK.
  • This release requires version 8.2.0+ of the Braze React Native SDK, this change allows the Braze Expo plugin to be compatible with incoming iOS notifications from Expo Notifications.
• Adds the iosRequestPushPermissionsAutomatically configuration to control whether iOS push permissions should be requested automatically on app launch.

1.1.2

Added

• Added Android support for the following configuration fields:
  • androidPushNotificationHtmlRenderingEnabled, androidNotificationSmallIcon, androidNotificationLargeIcon, androidNotificationAccentColor
• Added support for configuring a fallback Firebase Messaging Service on Android via androidFirebaseMessagingFallbackServiceEnabled and androidFirebaseMessagingFallbackServiceClasspath.
  • For example, if your fallback Firebase Messaging Service was expo.modules.notifications.service.ExpoFirebaseMessagingService, then your configuration would need to include:

    "androidFirebaseMessagingFallbackServiceEnabled": true,
    "androidFirebaseMessagingFallbackServiceClasspath": "expo.modules.notifications.service.ExpoFirebaseMessagingService",
  

  • You can find the proper fallback classpath in your Android merged AndroidManifest.xml file.
• Updated the sample app with version 6.0.1 of the the Braze React Native SDK.
  • This version demonstrates usage of the New Architecture and the Braze SDK as a Turbo Module.

1.1.1

Fixed

• Fixed an issue where Braze.getInitialUrl() could incorrectly return null.

1.1.0

⚠ Breaking

• Now requires Braze React Native SDK v2.1.0+.
• Updates the default Kotlin version to 1.8.10 for Expo 48 compatibility. This value is overridden by the android.kotlinVersion property in app.json.

Changed

• No longer requires static linkage of frameworks for iOS.

1.0.1

Fixed

• Fixed an issue introduced in 1.0.0 where setting enableAutoLocationCollection to any value in app.json would enable the option on iOS.