Releases: braze-inc/braze-unity-sdk
1.21.1
Important: This release has known issues displaying HTML in-app messages. Do not upgrade to this version and upgrade to 1.21.2 and above instead. If you are using this version, you are strongly encouraged to upgrade to 1.21.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.
Note: This release contains Unity packages with the -nosim
option, which remove iOS simulator architectures.
1.20.0
Important: This release has known issues displaying HTML in-app messages. Do not upgrade to this version and upgrade to 1.21.2 and above instead. If you are using this version, you are strongly encouraged to upgrade to 1.21.2 or above if you make use of HTML in-app messages.
Breaking
- Updated the iOS plugin to use Braze iOS SDK 3.18.0.
- Updated the Android plugin to use Braze Android SDK 3.7.0.
- Note: This Braze Unity SDK release updates to a Braze Android SDK dependency which no longer enables automatic Braze location collection by default. Please consult the changelogs for information on how to continue to enable automatic Braze location collection, as well as further information on breaking changes.
- Removes the Feedback feature and all associated methods, classes, and interfaces.
1.19.0
Breaking
- Updated the iOS plugin to use Braze iOS SDK 3.16.0.
1.18.0
Breaking
- Updated the iOS plugin to use Braze iOS SDK 3.14.0.
Note: This release includes a Unity package that uses the Braze Core iOS SDK (no UI). See Appboy-nodeps-core.unitypackage
.
1.17.0
Breaking
- Updated the Android plugin to use Braze Android SDK 3.2.1.
- 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
1.16.0
Breaking
- Updated the iOS plugin to use Braze iOS SDK 3.11.0.
- Updated the Android plugin to use Braze Android SDK 3.1.0.
Fixed
- Fixed an issue where the binding would cache the Appboy singleton instance.
- Fixed
Card.cs
to always returnCardCategory.NO_CATEGORY
in all cases where no valid categories are found.
Changed
- Updated the Appboy configuration editor to use Braze branding.
- By default, native in-app messages on Android no longer show the status bar.
1.15.0
Breaking
- Updated the Android plugin to use 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,
Added
- Added
SetAttributionData
to the Appboy interface.
Other
- This release's no-deps unity package contains only the Core Braze iOS SDK. The Core Braze iOS SDK framework file is also available.
1.14.0
Breaking
- Updates the iOS plugin to use Braze iOS SDK 3.7.1.
- Updates the iOS plugin to use the Braze iOS SDK framework instead of local files.
- As a result, imports using local file syntax (e.g.
"AppboyKit.h"
) must change to framework (e.g.<Appboy_iOS_SDK/AppboyKit.h>
) syntax.
- Updates the Android plugin to use Braze Android SDK 2.6.0.
- Removes Android Support Library artifacts from the Braze Unity Plugin. This is to avoid duplicating the Android Support Library artifacts that are automatically included as part of the Firebase Unity SDK, our recommended push integration. Integrators not using Firebase or importing Android Support Library artifacts through another SDK must include the Android Support Library manually (v4 only).
Fixed
- Fixed an issue that required manual import of non-xib Braze iOS SDK resources into Unity-generated Xcode projects.
Added
- Added
GetInstallTrackingId
to the Appboy interface. This method is currently only implemented on Android and is a no-op on iOS. - Updated the Unity Samples sample app to use FCM instead of GCM.
Changed
- In-app message analytics events on the Appboy interface no longer require using an Appboy Unity player subclass.
Removed
- Removes
showStreamView:
from theAppboyUnityManager.h
interface.
Other
- This release does not contain a no-deps version.
1.13.0
Breaking
- Updates the iOS plugin to use Braze iOS SDK 3.4.0.
- Updates the Android plugin to use Braze Android SDK 2.3.0.
- Removes Windows support.
- Removes
LogSlideupImpression
andLogSlideupClicked
from the Appboy interface.
Added
PostBuild.cs
now adds SDWebImage and FLAnimatedImage to XCode embedded binaries automatically.- See #35. Thanks @nlattessi!
PostBuild.cs
may now run in Unity environments without Unity iOS Build Support.- Added support for wiping all customer data created by the Braze SDK via
Appboy.AppboyBinding.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.AppboyBinding.disableSDK()
to disable the Braze SDK immediately. - Added
Appboy.AppboyBinding.enableSDK()
to re-enable the SDK after a call toAppboy.AppboyBinding.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,