How do previous versions of the LinkReaderSDK handle unsupported payoffs?

New types of payoffs may be added to the Link Platform to enhance the user experience and support new features. Such payoffs need to be recognized by the LinkReaderSDK so they can be handled appropriately.

Previous versions of the LinkReaderSDK might not be able to handle newly-introduced payoffs. This article will explain the behavior of the LinkReaderSDK when unsupported payoff types are detected. 

One such example is when older LinkReaderSDK versions (below 3.1) are used to scan a Track and Trace mark when anonymous validation is turned on for a given product line. 

We recommend keeping an up-to-date version of the LinkReaderSDK to prevent these and other unwanted scenarios from occurring.

iOS LinkReaderSDK


When unsupported payoff types are detected using an older iOS SDK, you will see issues with the following classes:

- EasyReadingViewController (Basic usage)

The EasyReadingViewController instance will stop scanning and the readerError: method will be called on the object assigned as the delegate of the EasyReadingViewController object. The error object in the readerError: method will be part of the "LRPayoffErrorDomain" domain and an error code will be "LRPayoffErrorMissingOrUnknownPayoffType". You can inform the user about the error and then call the resumeScanning method on the EasyReadingViewController object to continue scanning.

- LRManager and LRCaptureManager (Advanced usage)

The LRCaptureManager shared instance will stop scanning and the errorOnPayoffResolving method will be called on the delegate of the LRDetection shared instance. The error object in the readerError: method will be part of the "LRPayoffErrorDomain" domain and an error code will be "LRPayoffErrorMissingOrUnknownPayoffType". You can inform the user about the error and then call the startScanning method on the LRCaptureManager shared instance to continue scanning.


Android LinkReaderSDK


When unsupported payoff types are detected using an older Android SDK, you will see issues with the following classes:

- EasyReadingFragment (Basic usage)

When the LinkReaderSDK detects an unsupported payoff, the EasyReadingFragment will not be able to present the payoff so the loading screen shown when a trigger is scanned will be dismissed and the EasyReadingFragment will return to scanning mode. No error message is returned or displayed to user. 

- LinkReaderCaptureManager and LinkReaderManager (Advanced usage)

The errorOnPayoffResolving(ResolveError resolveError) method will be called on the object that implements the DetectionCallback. The error will be of type PayoffError and the errorCode attribute of the error object will have a value of UNSUPPORTED_TYPE. You can inform the user about the error and then call the startScanning(DetectionCallback detectionCallback) method on the LinkReaderManager instance to continue scanning.






Feedback and Knowledge Base