Releases: Synerise/android-sdk
Releases · Synerise/android-sdk
SDK and Sample 5.16.0
Changed
- Improved mechanism for checking capping in in-app messages. The number of views no longer resets when the account's UUID changes.
SDK and Sample v5.15.0
Added:
- Global Control Group support for in-app messages. From now on, you can use this feature in in-app messaging communication. This lets you take your marketing efforts to the next level and provides a solid foundation for accurate measurement of campaign effectiveness. Read more at https://hub.synerise.com/docs/settings/configuration/global-control-group/.
- We added a new
Client.authenticateWithTokenPayload(TokenPayload tokenPayload, @NonNull String authId)
method. This method signs in a customer in with the provided token payload. - We added a new
Client.getUuidForAuthentication(@NonNull String authId)
method. This method retrieves the current UUID or generates a new one from a seed (authId
). clientId
property in theToken
model.
SDK and Sample v5.14.1
Fixed:
- Added proguard rules for joda.time and retrofit.
- Updated proguard rules for gson.
SDK and Sample v5.14.0
Changed:
Autotracking
is now based ononTouchListener
instead ofonClickListener
.onRegisterForPushRequired
is now triggered on every launch.Client.registerForPush
has now built in cache with 24h expiration time.
SDK and Sample v5.13.1
Changed
- IMPORTANT:
- Due to changes in the handling of actions for URLs and deep links in Synerise campaigns, we strongly recommend comparing your configuration with the SDK documentation. Review the changes from the previous SDK version integrated into your application here:
https://hub.synerise.com//developers/mobile-sdk/campaigns/action-handling/
Fixed
- in
Client.simpleAuthentication
not passing email or customId affected in 412 error. Now it is fixed. IllegalArgumentException
in Mobile-Info header. Issue with character 0xa0.
SDK and Sample v5.12.0
Changed
setRequestValidationSalt
is now optional. Salt is not required for simpleAuthentication, but we recommend using it for improved security (it needs to be enabled in the Synerise portal first).
SDK and Sample v5.11.0
Added
hostApplicationSDKPluginVersion
toSynerise.Builder
. This information will be added to application.Started event only if you use technologies different than native android.
SDK and Sample v5.10.1
Added
shouldSendInAppCappingEvent
setting to decide whether sdk should sendinApp.capping
event or not.
Fixed
- issue with inApp capping. Capping was not working correctly when used together with frequency capping.
- notification priority issue with uppercase (affecting only flutter users)
- workManager conflict. Synerise SDK is now not using default work manager initializer.
SDK and Sample v5.9.0
Added
- minor security improvements.
Changed
- Method
Client.recognizeAnonymous
is now not working for users authenticated with simple authentication process.
Fixed
- issue with inApps not being triggered.
Tracker.sendImmediately
is now included in inApps triggering mechanism. - KeystoreException while generating secret keys. You can now handle this situation in
onInitializationFailed()
insideSyneriseListener
SDK and Sample v5.8.1
Fixed
- issue with saving trigger events from inApp campaigns to triggers database. Before this version please make campaigns with only one trigger. Campaigns with multiple triggers will be shown only on the last trigger.