Releases: sailthru/sailthru-mobile-android-sdk
Releases · sailthru/sailthru-mobile-android-sdk
v3.8.0
v3.7.2
v3.7.1
v3.7.0
Logging
All logging from the Carnival SDK can now be captured through the Carnival.setLogger(logger) and Logger interface.
Method Restrictions at Push-Time
There are now restrictions in place during Application#onCreate() and CarnivalMessageListener#onMessageReceived(). Method calls that update the device model (User ID, Attributes, etc) cannot be done at these times. Event logging via logEvent() is still safe to do in these methods.
v3.6.1
v3.6.0
Clear Device Data
new clearDevice() method for clearing device messages, attributes, and events accociated with that device.
//Carnival.ATTRIBUTES|Carnival.MESSAGE_STREAM|Carnival.EVENTS
Carnival.clearDevice(Carnival.CLEAR_ALL, new Carnival.CarnivalHandler<Void>() {
@Override
public void onSuccess(Void value) {
}
@Override
public void onFailure(Error error) {
}
});Get Message
New method to get a Message by its ID.
String messageId = getIntent().getStringExtra(Carnival.EXTRA_MESSAGE_ID);
Carnival.getMessage(messageId, new Carnival.CarnivalHandler<Message>() {
@Override
public void onSuccess(Message message) {
formatView(message);
}
@Override
public void onFailure(Error error) {
Log.e(TAG, "Failed to load message: " + error);
}
});Notifications
Optimised notification handing resulting in less network overhead.