Releases: braze-inc/braze-react-native-sdk
Releases · braze-inc/braze-react-native-sdk
1.11.0
- Updated the native Android bridge to Braze Android SDK 3.2.0.
- Added
AppboyFirebaseMessagingService
to directly use the Firebase messaging eventcom.google.firebase.MESSAGING_EVENT
. This is now the recommended way to integrate Firebase push with Braze. TheAppboyFcmReceiver
should be removed from yourAndroidManifest
and replaced with the following:<service android:name="com.appboy.AppboyFirebaseMessagingService"> <intent-filter> <action android:name="com.google.firebase.MESSAGING_EVENT" /> </intent-filter> </service>
- Also note that any
c2dm
related permissions should be removed from your manifest as Braze does not require any extra permissions forAppboyFirebaseMessagingService
to work correctly.
- Also note that any
- Added
- Updated the native iOS bridge to Braze iOS SDK 3.14.0.
- Dropped support for iOS 8.
1.10.0
1.9.0
Breaking
- Updated the native iOS bridge to Braze iOS SDK 3.11.0.
- Updated the native Android bridge to Braze Android SDK 3.0.1.
- Updated the Android wrapper to use
api
andimplementation
syntax in it'sbuild.gradle
instead ofcompile
. As part of this work, the Android Gradle plugin version was updated to3.2.1
.
Added
- Added
setUserAttributionData()
to theAppboy
interface to allow setting the attribution data for the current user. - Added
getInstallTrackingId()
to theAppboy
interface to allow getting the install tracking id. This method is equivalent to callingAppboy.getInstallTrackingId()
on Android and returns the IDFV on iOS. - Added
setLanguage()
to theAppboy
interface to allow setting a language for the current user. - Added
hideCurrentInAppMessage()
to theAppboy
interface to allow hiding of the currently displayed in-app message.
Fixed
- Fixed an issue where the Android wrapper would include an older version of React Native in test APK builds.
Changed
- Updated our sample projects to use React Native
0.56
.
1.8.1
Changed
- Updated the native iOS bridge to Braze iOS SDK 3.8.4.
1.8.0
- Updated the native Android bridge to Braze Android SDK 2.7.0.
- Important: Note that in Braze Android SDK 2.7.0,
AppboyGcmReceiver
was renamed toAppboyFcmReceiver
. This receiver is intended to be used for Firebase integrations. Please update theAppboyGcmReceiver
declaration in yourAndroidManifest.xml
to referenceAppboyFcmReceiver
and remove thecom.google.android.c2dm.intent.REGISTRATION
intent filter action.
- Important: Note that in Braze Android SDK 2.7.0,
- Updated the native iOS bridge to Braze iOS SDK 3.8.3.
1.7.3
1.7.2
1.7.1
1.7.0
Breaking
- Updated the native iOS bridge to Braze iOS SDK 3.5.1.
- Updated the native Android bridge to Appboy Android SDK 2.4.0.
Added
- Added
Other
,Unknown
,Not Applicable
, andPrefer not to Say
options for user gender. - Updated the
AppboyProject
sample app to use FCM instead of GCM. - Added toasts to provide feedback for user actions in the
AppboyProject
sample app. - Implemented
requiresMainQueueSetup
inAppboyReactBridge.m
to prevent warnings in React Native 0.49+.- See #39. Thanks @danieldecsi!
Changed
- Passing launch options into
launchNewsFeed
is now a no-op.
1.6.0
Breaking
- Updated the native iOS bridge to Braze iOS SDK 3.3.3 or later.
- Updated the native Android bridge to Braze Android SDK 2.2.5.
Added
- Added support for wiping all customer data created by the Braze SDK via
Appboy.wipeData()
.- Note that on iOS,
wipeData()
will disable the SDK for the remainder of the app run. For more information, see our iOS SDK's documentation fordisableSDK
.
- Note that on iOS,
- Added
Appboy.disableSDK()
to disable the Braze SDK immediately. - Added
Appboy.enableSDK()
to re-enable the SDK after a call toAppboy.disableSDK()
.- Note that on iOS,
enableSDK()
will not enable the SDK immediately. For more information, see our iOS SDK's documentation forrequestEnableSDKOnNextAppRun
.
- Note that on iOS,