@braze/web-sdk - npm Package Versions

4.4.0

Added

• A message is now logged if an IAM is triggered but not displayed because neither automaticallyShowInAppMessages() nor subscribeToInAppMessage() were called.

Changed

• IndexedDB connections now close after a transaction has been completed.

Fixed

• Fixed an issue introduced in 4.0.0 where In-App Message closing animations did not work as expected.

4.3.0

Added

• Added brazeBridge.changeUser(id: string, sdkAuthSignature?: string) to HTML In-App Messages.
• Added the ability to include a custom pathname in the baseUrl initialization option.

4.2.1

Fixed

• Fixed an issue introduced in 4.0.3, where IAM displays could sometimes fail due to an internal race condition.

4.2.0

Added

• Added support for Content Cards to evaluate Retry-After headers.

4.1.0

Added

• Added a method braze.logContentCardImpressions() to log that the user saw the given Content Cards. This method is equivalent to calling braze.logCardImpressions() with parameter forContentCards = true.

Fixed

• Fixed an issue where calling unregisterPush() when the user is already unregistered would fail to execute the success callback function.

4.0.6

Fixed

• Fixed an issue introduced in 4.0.0 that incorrectly failed to display valid IAMs with an unknown Braze Action type error.

4.0.5

Fixed

• Fixed an issue introduced in 4.0.0 that prevented the SDK from running with certain rollup.js configurations.

4.0.4

Changed

• Deprecated and changed the obsolete logContentCardsDisplayed method to a no-op. Card impressions should be logged using logCardImpressions.

Fixed

• Fixed an issue introduced in 4.0.0 that prevented control in-app message impressions from being logged.

4.0.3

Fixed

• Fixed an issue introduced in 4.0.0 where Safari push did not work unless the full baseUrl (e.g. https://sdk.iad-01.braze.com/api/v3) was specified in the initialization options.
• The SDK will now ignore In-App Messages containing a push prompt Braze Action for users who have already registered for push or whose browser does not support push.

4.0.2

Changed

• Cookies set by the Braze Web SDK now expire after 400 days per the recommendation of the HTTP Working Group's draft RFC 6265

Fixed

• Removed usages of the nullish coalescing operator for better compatibility with various webpack configurations.