Releases: Pushwoosh/pushwoosh-android-sdk
Releases · Pushwoosh/pushwoosh-android-sdk
6.7.6
Important
- Default scheme for creating test devices via deep links was changed to
pushwoosh-{}://createTestDevice
. If you use the old scheme, please change it in your AndroidManifest.xml
Changed
minSdkVersion
is reverted to 21- Pushwoosh SDK now waits for an application to be brought to foreground state before sending
getConfig
,getInApps
andregisterDevice
on initialization. Previously these requests were sent when SDK was initializing, even if it was happening in background (i.e. when a push was received) applicationOpen
,messageDeliveryEvent
andpushStat
statistics API requests are now sent with a 30-seconds jitter
Added
Pushwoosh.registerForPushNotificationsWithTags(TagsBundle tags)
method. This method can be used to avoid race condition when setting tags and registering a device simultaneouslyTagsBundle.Builder.removeFromList(String tag, List<String> valuesToRemove)
method. This method can be used to remove multiple values from List Tags
Removed
- Internal
StatusBarNotificationStorage
andPushAnalyticsRequest
classes are removed.
6.7.5
6.7.4
Fixed
- restored default behavior when receiving a push notification in foreground
6.7.3
Added
public void setShowPushnotificationAlert(boolean showAlert)
method added
Changed
- removed unused TLS1.1 code references
6.7.2
Changed
- SDK can now receive failed rich medias sent from Customer Journey with the next postEvent call
6.7.1
Changed
- Roll back changes to minSdkVersion to 23
6.7.0
Important
- SDK now requires
com.google.firebase:firebase-messaging:23.1.+
versions to work properly
Added
pushwoosh-xiaomi
module
Fixed
- Push tokens sometimes invalidating on application's first launch
OutOfMemoryError
crash when migrating old tags (from 5.+ SDK versions)
Changed
- SDK is now built with newer Android Gradle plugin (7.5.0)
- Pushwoosh SDK migrated to maven-publish publishing plugin
6.6.17
Changed
- changed format of
actionParams
in internal Rich Media event tracking - forcibly request new push tokens from FCM if they are not automatically refreshed
6.6.16
Important
pushoosh-inbox-ui
module now requires addingimplementation "androidx.databinding:viewbinding:4.1.3"
manually to your app dependencies
Added
- Android 14 support
Changed
targetSdkVersion
of the library is now 33pushwoosh-inbox-ui
module now uses view binding intstead of deprecated synthetics- All implicit intents are replaced with explicit ones (required for Android 14)
- BroadcastReceivers are registered with
Context.RECEIVER_NOT_EXPORTED
flags (required for Android 14)
6.6.15
Added
- Internal rich media lifecycle event tracking