Releases: BatchLabs/Batch-Android-SDK
Releases · BatchLabs/Batch-Android-SDK
1.20.2
This release backports changes from 1.21.1
Inbox
- Fixed an issue where an inbox fetcher could have a wrong configuration.
1.21.0
BREAKING
- Removed support for optional Play Core library. You should now use the Play In-App Review Library. Please see our documentation for more info.
Core
- Removed automatic collection of AAID (Android Advertising Identifier).
setCanUseAdvertisingID
is now a no-op. You need to collect it from your side and pass it to Batch via the addedBatch.User.editor().setAttributionIdentifier(id)
method.
Push
- To help with FCM v1 API migration, the SDK will send the GCP Project ID associated to the FCM Token to Batch's backend. This is not supported in legacy GCM/FCM Instance ID modes.
1.20.1
User
- Fixed an issue on
BatchUserDataEditor
where data wasn't sent when usingsetEmail
orsetEmailMarketingSubscriptionState
.
1.20.0
Core
- Batch now compiles with and targets SDK 34 (Android 14 'Upside Down Cake').
- Fixed a rare issue where the SDK could trigger an ANR on start when upgraded from an older version.
Push
- Improved notification image by making notifications taller if possible and changing scaling type to Center Fit.
User
- Added
Batch.User.editor().setEmail(email)
method. This requires to have a user identifier registered or to call thesetIdentifier
method on the editor instance beforehand. - Added
Batch.User.editor().setEmailMarketingSubscriptionState(BatchEmailSubscriptionState)
method to subscribe to the email marketing list.
Inbox
- Added the ability to know if a
BatchLandingMessage
has been displayed from the inbox via theisDisplayedFromInbox()
method. - Added the ability to know if a notification has a landing message attached on
BatchInboxNotificationContent
using thehasLandingMessage()
method. - Added the ability to display a landing message attached to a
BatchInboxNotificationContent
using thedisplayLandingMessage(context)
method.
1.19.4
Messaging
- Fixed an issue for In-App Webview format where Batch would get the wrong deeplink url for an image embedded into a hyperlink.
1.19.3
Core
- Fixed an issue where Batch would crash when advertising ID collection is enabled and the Firebase Messaging library is not present
1.19.2
Core
- Batch now compiles with and targets SDK 33 (Android 13).
- Improved support for Android 13 Tiramisu.
- Added a new API:
Batch.Push.requestNotificationPermission(context)
. This allows you to request for the new notification permission introduced in Android 13. See the documentation for more info. - Fixed an issue where
BatchNotificationChannelsManager.openSystemChannelSettings(context)
wasn't working with an application context.
Actions
- Added
batch.android_smart_reoptin
, which asks the user the notification permission or redirect to the notification settings. - Added
batch.android_redirect_settings
, which redirects the user to the notification settings.
1.18.3
Messaging
- Fixed a display issue on Modals with an image but no title.
1.19.1
Core
- Fixed a rare crash on Wiko devices when a high priority push was received in battery saving mode.
Event Dispatcher
- Fixed a crash that could happen when using Batch SDK 1.19+ with ATInternet or Firebase dispatcher plugins < 3.0.
Messaging
- Fixed a display issue on Modals with an image but no title.
1.19.0
Core
- Batch now compiles and targets SDK 32 (Android 12L).
- Important change: Batch now declares to use the
android.permission.POST_NOTIFICATIONS
permission in its manifest. If you want to remove it, add<uses-permission android:name="android.permission.POST_NOTIFICATIONS" tools:node="remove" />
in your app's AndroidManifest. - Fixed some rare ANRs produced when receiving push.
- Identical push messages sent twice by FCM will now only be displayed once.
- Batch will now try to display FCM high priority push notifications directly rather than scheduling a Job.
Event Dispatchers
- Added
getName
andgetVersion
onBatchEventDispatcher
. If you are using a Batch dispatcher plugin, please update it.
Messaging
- Added global frequency capping management for in-app campaigns.
- Improved the way In-App campaigns are triggered.
- Added just-in-time verification for in-app campaigns.
Inbox
- Added the ability to disable the filtering of silent notifications on
BatchInboxFetcher
using thesetFilterSilentNotifications
method. - Important change: Silent notifications are now filtered by default: use the new property if you relied on the previous behaviour.
This brings the Android SDK in line with its iOS counterpart, which has always filtered silent notifications as expected.