#Swift converter 3.2.0 update#
Calling changeUser() with an SDK Authentication signature will now update the signature when it is called with the current user’s ID.Accessibility improvements to in-app messages with scrollable text.Added getter method appboy.isDisabled() to determine if SDK has been disabled via appboy.disableSDK().Deprecated the appboy.resumeWebTracking() method in favor of using appboy.enableSDK(), which has the same functionality.Deprecated the appboy.stopWebTracking() method in favor of using appboy.disableSDK(), which has the same functionality.
Added appboy.addSdkMetadata() to allow self reporting of SDK Metadata fields via the appboy.BrazeSdkMetadata enum.Added braze.handleBrazeAction() to handle Braze Action URLs when using a custom UI.When displaying In-App Messages and Content Cards through our built-in UI, this feature requires no additional code.
#Swift converter 3.2.0 how to#
See our upgrade guide for more information on how to migrate. As a result of the above changes, many of our method signatures have changed.If you use the Appboy prefix as a filter in your logging tools, you should update it to include Braze. The prefix for SDK logs has changed from Appboy to Braze.If you prefer to continue using a compiled version of the SDK, it can be found through our CDN. For example, if you only use In-App Messages with a custom UI, you can now import our InAppMessage classes and subscribeToInAppMesssage() and Javascript module bundlers such as webpack will remove any unused code. The Braze Web SDK now supports importing individual features and methods as native ES Modules that can be tree-shaken.CDN users must ensure that the URL points to this new file name when upgrading to 4.0. The file name for the bundled version of the SDK has changed to.CDN users must update their loading snippet when upgrading to 4.0. The SDK’s exported object has been renamed from appboy to braze.The appboy-web-sdk, and npm packages are deprecated in favor of the package and will no longer receive updates.See our upgrade guide for more information on how to migrate from v3.Added "type": "module" to the package.json so frameworks like Next.js recognize the SDK as an ES Module.The created field is now set for Card objects when using Content Cards.Removed usages of the nullish coalescing operator for better compatibility with various webpack configurations.Cookies set by the Braze Web SDK now expire after 400 days per the recommendation of the HTTP Working Group’s draft RFC 6265.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.) was specified in the initialization options.
#Swift converter 3.2.0 full#
Fixed an issue introduced in 4.0.0 that prevented the SDK from running with certain rollup.js configurations.Fixed an issue introduced in 4.0.0 that incorrectly failed to display valid IAMs with an unknown Braze Action type error.Fixed an issue where calling unregisterPush() when the user is already unregistered would fail to execute the success callback function.This method is equivalent to calling braze.logCardImpressions() with parameter forContentCards = true. Added a method braze.logContentCardImpressions() to log that the user saw the given Content Cards.Added support for Content Cards to evaluate Retry-After headers.Fixed an issue introduced in 4.0.3, where IAM displays could sometimes fail due to an internal race condition.Added the ability to include a custom pathname in the baseUrl initialization option.Added brazeBridge.changeUser(id: string, sdkAuthSignature?: string) to HTML In-App Messages.
0 kommentar(er)
