1.10.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.

1.10.1

Important: This release has known issues displaying HTML in-app messages. Do not upgrade to this version and upgrade to 1.10.2 and above instead. If you are using this version, you are strongly encouraged to upgrade to 1.10.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.

1.10.0

Important: This release has known issues displaying HTML in-app messages. Do not upgrade to this version and upgrade to 1.10.2 and above instead. If you are using this version, you are strongly encouraged to upgrade to 1.10.2 or above if you make use of HTML in-app messages.

Breaking

• Updated the native iOS bridge to 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.RegisteredForRemoteNotifications:, replace

Appboy.SharedInstance?.RegisterPushToken(deviceToken.ToString());

with

Appboy.SharedInstance?.RegisterDeviceToken(deviceToken);

1.9.0

Important: This release has known issues displaying HTML in-app messages. Do not upgrade to this version and upgrade to 1.10.2 and above instead. If you are using this version, you are strongly encouraged to upgrade to 1.10.2 or above if you make use of HTML in-app messages.

Breaking

• Updated the Android binding to use Braze Android SDK 3.7.0.
• Updated the native iOS bridge to Braze iOS SDK 3.19.0.
• Note: This Braze Xamarin SDK release updates to Braze Android SDK and Braze iOS SDK dependencies which no longer enable automatic Braze location collection by default. Please consult their respective 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 as well as all associated methods, classes, and interfaces.

1.8.0

Changed

• Updated the Android binding to use Braze Android SDK 3.3.0.

Added

• Added C# bindings for Braze Android SDK classes with Firebase Cloud Messaging dependencies.

1.7.0

Breaking

• Updated the Android binding to use Braze Android SDK 3.2.1.
  • Added AppboyFirebaseMessagingService to directly use the Firebase messaging event com.google.firebase.MESSAGING_EVENT. This is now the recommended way to integrate Firebase push with Braze. The AppboyFcmReceiver should be removed from your AndroidManifest 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 for AppboyFirebaseMessagingService to work correctly.
• Updated the native iOS bridge to Braze iOS SDK 3.14.0.
  • Drops support for iOS 8.
  • Removes Cross-Promotion cards from the News Feed.

1.6.0

Breaking

• Updated the native iOS bridge to Braze iOS SDK 3.11.0.
• Updated the Android binding to use Braze Android SDK 3.0.1.

1.5.2

Fixed

• Fixed an issue that caused C# bindings to not be generated for certain classes in the Braze UI library.

Changed

• Updated the Android binding to use Braze SDK version 2.5.0.
• Updated the Android sample app to use Firebase Cloud Messaging (FCM).

1.5.1

Changed

• Updated the iOS binding to use Braze SDK version 3.3.4.
  • Added DisableSDK() and RequestEnableSDKOnNextAppRun() to the Appboy interface to disable and re-enable the Braze SDK.
  • Added WipeDataAndDisableForAppRun() on the Appboy interface to support wiping all customer data created by the Braze SDK.
  • Note that methods that disable the SDK will cause Appboy.SharedInstance to return null. If you have code that uses Appboy.SharedInstance, do not use DisableSDK() or WipeDataAndDisableForAppRun() until your code can safely execute even if Appboy.SharedInstance is null.
• Updated the Android binding to use Braze SDK version 2.2.5.
  • Added DisableSdk() and EnableSdk() to the Appboy interface to disable and re-enable the Braze SDK.
  • Added WipeData() on the Appboy interface to support wiping all customer data created by the Braze SDK.

1.5

Breaking

• Removed the need to include Appboy.bundle manually in iOS integrations. Integrators should remove existing Appboy.bundle files from their iOS integrations.

Added

• Added the ability to report to Braze that the app is running Xamarin to iOS integrations. We strongly recommend reporting this value to allow Braze to calculate accurate usage around different SDK platforms. To enable reporting, add Appboy.SharedInstance.SdkFlavor = ABKSDKFlavor.Xamarin; to your AppDelegate.cs after calling Appboy.StartWithApiKey().
• Braze Xamarin Bindings are now available on Nuget. Check out our iOS Binding and Android Binding. Note that Braze Xamarin SDK version 1.5.0 is the last version to receive a Xamarin component store release. Future releases will be released to Nuget and the open source repo only.

Changed

• Updated the iOS binding to use Braze SDK version 3.3.0.
• Updated the Android binding to use Braze SDK version 2.2.1.