Mobile SDK Release Notes

All methods

The version is available for all methods, including Carthage, CocoaPods, and manual. For more information, see SDK Installation for iOS.

IOS

Minor updates to prevent crashes reported by a user. 

iOS

We changed our SDK structure from .framework to .xcframework to support the new arm64 architecture for the ios simulator (in Macs with the M1 processor). 

Action Needed: If you are using Push Notifications, reimport the Dynamic Yield framework (it is now DYAPI.xcframework instead of DYAPI.framework. For details see "Add Notification Content Extension" and "Add Notification Service Extension" in Enabling Push Notifications. 

Android

To resolve a bug in which the app's icon is not showing, you can add the icon to your project's drawable folder. The icon should have a transparent background and be named dy_notification_small_icon.png.

Android

We do not recommend using synchronized APIs, even though they are still supported. Therefore, we have marked them all as deprecated in the documentation. 

iOS

Fixed an issue in which clicking a native image template sometimes caused the client app to crash.  

Android

Fixed an issue in which push notifications were being sent to opted out users. 

iOS

Fixed an issue in which the SDK was sometimes crashing. 

iOS

Fixed an issue in which the SDK was sometimes crashing because of a memory issue. 

Fixed an issue in which the getUserAffinityProfile API was not working for EU customers

Fixed an issue in which users were not included in audiences even when the conditions were met. 

Android and iOS

sendRecommendationItem

Enhances the recommendation API to allow you to filter the results using data from the current session.  

Fixes an issue in which getProductActivityData API sometimes did not send the timeframe and interest parameters.

All synchronous APIs now have the ability to run asynchronously as well using a callback function. 

Fixes an issue where overlays were rendering in the wrong position. 

Removed a deprecated class (UIWebViewDelegate) from the SDK 

You can now run the Dynamic Yield SDK on mobile applications using the React Native framework.

Note: This only supports data collection, recommendation campaigns, and variable sets. 

Learn more about how install the SDK for iOS and Android. 

Fixes a bug that causes recommendation callbacks to not be triggered when the recommendation request is invalid.

pageView

trackEvent

setEvaluator

Before:

-(BOOL)loadWebView:(UIWebView* _Nullable)webView 
withSmartObject:(NSString* _Nonnull)smartObjID 
fallbackURL:(NSURL* _Nullable)fallBackURL;

After:

-(BOOL)loadWebView:(WKWebView* _Nullable)webView 
withSmartObject:(NSString* _Nonnull)smartObjID 
fallbackURL:(NSURL* _Nullable)fallBackURL;

What does this mean for you?

Dynamic Yield supports both parameter types, but as Apple will probably remove UIWebView in the future, you should start using WKWebView as soon as possible.

What does this mean for you?

This will result in fewer nullability warnings. 

• pageView
• trackEvent
• loadWebView
• loadImageView
• setEvaluator
• setSecretKey
• sendRecommendation
  Request

What does this mean for you? 

This allows you to write code in-line, that runs when the method operation has been completed instead of using a listener class.

• trackPageView
• trackEvent
• loadSmartObject
• loadSmartObject – image content
• setEvaluator
• setContextAndSecret

What does this mean for you? 

This allows you to write code in-line, that runs when the method operation has been completed instead of using a listener class.

Enhancement

• trackSmartObjectImpression
• trackSmartObjectClick

The structure of the return value has been changed

“cannot find symbol method setAutoPageViewsTracking”

Replace any calls to this API with the trackPageView API that does not contain the name and section parameters:

public boolean trackPageView(java.lang.String uniqueID, DYPageContext context)

Calling the deleted API will result in the following compile error:
“Method trackPageView in class DYApi cannot be applied to given types”

public boolean setEvaluator(String evaluatorID, JSONArray params, boolean saveBetweenSessions)

Calling the deleted API will result in the following compile error:
“Method setEvaluator in class DYApi cannot be applied to given types”

Implementing the deleted method will result in the following compilation error:
“Error: method does not override or implement a method from a supertype”

-(BOOL)pageView:(NSString*)uniqueId context:(DYPageContext*)DYContext;

Calling the deleted API will result in the following compilation error:
“No visible @interface for ‘DYApi’ declares the selector ‘pageView:name:section:context:'”

-(BOOL)setEvaluator:(NSString*)evaluatorID forParams:(NSArray*)params saveBetweenSessions:(BOOL)save;

Calling the deleted API will result in the following compile error:
“No visible @interface for ‘DYApi’ declares the selector ‘setEvaluator:forParams:'”

-(void) experimentsReadyWithState:(ExperimentsState)
state

Implementing this method will cause a compilation error in Swift, but only a warning in Objective-C.

Swift error: Type ‘YOUR_CLASS’ does not conform to protocol ‘DYDelegateProtocol’

Objective-C warning: Class ‘YOUR_CLASS’ does not conform to protocol ‘DYDelegateProtocol’

-(void)onRecommendationResult:(NSArray* _Nullable)recommendations forWidgetID:(NSString* _Nonnull)widgetID;

Implementing this method will cause a compilation error in Swift, but only a warning in Objective-C.

Swift error: Type ‘YOUR_CLASS’ does not conform to protocol ‘DYDelegateProtocol’

Objective-C warning: Class ‘YOUR_CLASS’ does not conform to protocol ‘DYDelegateProtocol’

Android: setContextAndSecret

consentOptout