Releases: OneSignal/OneSignal-Android-SDK
Releases · OneSignal/OneSignal-Android-SDK
3.12.5 Release
Minor Bug Fixes: Location Prompt Flicker, Too Many Alarms, Remote Params Crash
- Location Prompt Flicker Fixed #884
- The location prompt uses a
PermissionActivity
and still uses Android default transitions - Now we use to blank fade transitions for in and out animations so that no flickering occurs at all when being shown or dismissing the location prompt
- The location prompt uses a
- Too Many Alarms Fixed #887
- On Samsung device, intent flag
FLAG_CANCEL_CURRENT
sometimes causes a crash - Fixed by changing
FLAG_CANCEL_CURRENT
toFLAG_UPDATE_CURRENT
- On Samsung device, intent flag
- Remote Params Crash Fixed #916
- Customer was seeing an issue where remote params are null and email id is null after changing organization and app id of mobile app
- Crashing is fixed now with null checks to prevent any null exceptions, but the root of the issue was a request being made with a deleted app's app id and in the same session a init with a new app id
3.12.4 Release
Minor Bug Fixes & Updated Unity Proxy
- Sending custom outcome from notification opened handler will use the previous session instead of current
- Fixed now so the opened handler is called LAST when opening a notification so that all OneSignal work can be done first
- Updated Unity Proxy file
- Last release overwrote the Unity Proxy file, causing it to be outdated
3.12.3 Release
3.12.2 Release
SQLite Error on Outcome & Nullable Callback
OutcomeEvent
will now benull
whenOutcomeCallback.onSuccess
is fired to indicate the outcome was cached for retry.- Fixed SQLite DB migration issue when going from 3.12.0 to 3.12.1.
- Fixed dependency ranges in POM;
- Updated
com.google.android.gms:play-services-ads-identifier:[15.0.0, 16.0.99]
- Updated
com.google.android.gms:play-services-location:[10.2.1, 16.0.99]
- Updated
com.google.android.gms:play-services-base:[10.2.1, 16.1.99]
- Updated
com.google.firebase:firebase-messaging:[10.2.1, 17.3.99]
- Updated
com.android.support:cardview-v7:[26.0.0, 27.99.99]
- Updated
com.android.support:support-v4:[26.0.0, 27.99.99]
- Updated
com.android.support:customtabs:[26.0.0, 27.99.99]
- NOTE: Newer versions than above can be used, however you must enable Jetifier in your project
- Updated
3.12.1 Release
Outcome callback changes
- Dropped
onOutcomeFail
fromOneSignal.OutcomeCallback
- Outcomes are cached when offline and are always retried later.
3.12.0 Release
Outcomes & Received Receipts
- New Outcomes feature
- New Confirmed Deliveries
- Upgraded POM dependencies
- Added
com.google.android.gms:play-services-ads-identifier:[10.2.1, 16.1.0)
- Updated
com.google.android.gms:play-services-location:[10.2.1, 16.1.0)
- Updated
com.google.android.gms:play-services-base:[10.2.1, 16.1.0)
- Updated
com.google.firebase:firebase-messaging:[10.2.1, 16.1.0)
- Updated
com.android.support:cardview-v7:[26.0.0, 28.1.0)
- Updated
com.android.support:support-v4:[26.0.0, 28.1.0)
- Updated
com.android.support:customtabs:[26.0.0, 28.1.0)
- NOTE: Newer versions than above can be used, however you must enable Jetifier in your project
- Added
3.11.4 Release
Groupless Notification and In-App Message Dragging Action Fix
- Fixed
getActiveNotifications()
crash related toNotificationManager
class- Similar to issue #422, but for Android 8.0.0 Samsung devices
- Fixed an issue with In App Messaging where a drag would sometimes trigger an action
3.11.3 Release
In-App Messaging and Other Misc Fixes
- Fixed
startLocationUpdate
NPE with the Builder on app focus - Fixed nested
sendTags
calls.- Issue #671
- Fixed In-App Messaging crash when opening preview in rare cases
- Fixed crash when rotating the device while an In-App Messaging is about to show
3.11.2 Release
Android N groups, NPE userPrivacyConsent, Samsung 100 jobs Fixes🔨
- On Android N (7.0)+ devices when 4 or more notifications are shown tapping on the group is now handled
- Fix NPE errors when app is resumed when
setRequiresUserPrivacyConsent(true)
is set- Issue #800
- Fixed "App may not schedule more than 100 distinct jobs" error, mostly affecting Samsung devices in rare cases
- PR #804
3.11.1 Release
In-App Messages & Changing AppId Fixes
- Fixed In-App Messaging resizing on orientation change when
android:configChanges
is used. - When re-initializing with a different AppId the device registers correctly without requiring an app cold start
- Dashboard parameters are now correctly refreshed as well from the new app id.
- Added some extra In-App Message handler methods to make wrapper SDK development simple
removeTriggersForKeysFromJsonArrayString
addTriggersFromJsonString
OSInAppMessageAction. toJSONObject