Releases: OneSignal/OneSignal-Android-SDK
Releases · OneSignal/OneSignal-Android-SDK
3.10.4 Release
This release was made in error and contains no changes from 3.10.3. Please use 3.10.5 instead.
3.10.3 Release
Notification Restore Tweaks & Misc Bug Fixes
- Notification Restore Improvements (PR #645)
- Limit number of notification restored to 49
- This is the max visible limit per app, Android omits displaying any more
- Helps mitigate issue #644
- Slowed Restore rate to 5 per second
- Above 2 changes cleans up
NotificationService
warnings from the logcat
- Limit number of notification restored to 49
- GDPR method fixes
- Fixed
IllegalArgumentException
thrown fromJobIntentService
in a specific case- Issue was only happening with high priority notifications that had a remote image with an app setup with a
NotificationExtenderService
and running on Android Oreo+, in some cases. - Fixes issue #649
- Issue was only happening with high priority notifications that had a remote image with an app setup with a
- Fix for
OneSignalSyncServiceUtils
throwingIllegalArgumentException
when boot permission is removed. - Possible fix for rare "Package manager has died" error. PR #658
3.10.2 Release
Notification Channel Fallback, NotificationExtenderService Doze Mode, & Misc Fixes
- Fixed NPE with
ChangeTagsUpdateHandler
when a tag update results in no changes. PR #611 - Fixed
FirebaseInstanceIdService
IllegalArgumentException
exception - Fixed rare NPE Bundle error on
RestoreJobService.onHandleWork
. Issue #591 NotificationExtenderService
now respects FCM High priority to wake from Dose mode. PR #640- Fixed fallback of medium and lower priorities of Notification Channel for pre-Oreo devices. PR #639
- Fixed issue with disabling
enableVibrate
orenableSound
was not respected.- When initializing OneSignal after
Application.onCreate
. - Note, settings only apply to Android 7.0 and older.
- Methods will be deprecated, please migrate to Android Categories / Channels
- When initializing OneSignal after
- Cleaned up GCM related warning in logcat when a push is received. #642
CANCELLED forIntent { act=... flg=0x10000000 pkg=... }
3.10.1 Release
3.10.0 Release
Adds Send/Delete Tags Callback
- Adds a new
ChangeTagsUpdateHandler
parameter for methods that update/delete tags. - Publicly exposes
requiresUserPrivacyConsent()
that indicates if the application is set to require privacy consent and the user hasn't yet given consent - Publicly exposes
onesignalLog()
so that wrapper SDK's can use it - Updated fix for error with
startWakefulService
on Oreo when sending high priority with remote urls.- Issue #498
3.9.3 Release
Fixes FirebaseInstanceId & startWakefulService Errors
- Fixes error with
FirebaseInstanceId
when a default Firebase app is not initialized.- Issue #552
- Fixes error with
startWakefulService
on Oreo when sending high priority with remote urls.- Issue #498
- NOTE: After further investigation we determined this release did not resolve this issue, and we've included an updated fix in our new release (3.10.0)
3.9.2 Release
3.9.1 Release
Proguard, FCM Auth, Location, & Misc Fixes
- Fixed issue with latest Proguard causing FCM and Android Support library report as not found.
- Issue #533
- FCM init error when the Firebase Auth library was added to the project. PR #530
- Fixed GoogleAPIClient not connected yet errors. Issue #509
- Android 7.0
Bad Notification: Couldn't expand RemoteViews for: StatusBarNotification
- Restore on app update disabled to fix issue #263
- NPE on flushBufferToDisk. Issue #513
- Fix did not resolve issue, was fully fixed in 3.9.2
3.9.0 Release
FCM Library support, GDPR methods, & NPE dependValues Fix
- Now supports FCM (Firebase Cloud Messaging) library
- This upgrade is automatic as long as you followed the OneSignal standard setup guide.
- After April 11, 2019 Google will drop the GCM from new versions of their Play Services library
- GCM (Google Cloud Messaging) is still supported in the OneSignal SDK until then
- Issue #507
- Added GDPR privacy consent to postpone initialization of the SDK until the user accepts
- Add
<meta-data android:name="com.onesignal.PrivacyConsent" android:value="ENABLE" />
to yourAndroidManifest.xml
to enable this. - Once the user accepts your GDPR privacy permissions, your application should call
OneSignal.provideUserConsent(true)
- If your user revokes your privacy consent then you should call
OneSignal. provideUserConsent(false)
- Add
- Fixed NPE on
UserState.dependValues
. Issue #503