ATS Mobile SDK Events
Learn more about the events exposed by the ATS Mobile SDK that you can leverage in your own application.
Add a delegate to catch events triggered by the SDK. Events listeners allow you to react to different event of interests and error events.
Removes the delegate.
ATS Mobile SDK events are defined with an
|Event Name||Description||Callback Result|
|Fired when AtsManager starts initialization process.|
|Fired when AtsManager is fully initialized.|
|Fired when ATSManager is disabled.|
|Fired after SDK reset is complete.|
|Fired when the automatic sync is disabled and bloom filters need to be synchronized with the backend.|
|Fired when bloom filters synchronization is completed.|
|Fired when the bloom filters synchronization is partially completed.|
|Fired when an error has occurred during the bloom filters synchronization.|
|This status is returned when the Bloom filters could only be partially downloaded.|
|This status is returned when all the Bloom filters are fully downloaded.|
|This status is returned if, for some reason, synchronization of the Bloom filters has failed (|
|This status is returned if filtering is only done partially with all the Bloom filters. This can happen if at that moment all filters are not yet downloaded.|
|This status is returned if filtering is fully done on all bloom filters.|
|This status is returned if there is no internet connection.|
|This status is returned if the ATS SDK is not in a |
Updated about 1 month ago
View useful code snippets and initialization example.