Releases: OneSignal/OneSignal-Android-SDK
Releases · OneSignal/OneSignal-Android-SDK
2.5.0 Release
Notifications now restore when removed by the system
- Notifications are now restored to the notification shade when they were cleared by Android itself.
- Includes package upgrades, device reboots, and each time the app is cold started (to restore from the 'force stopped' state).
- Added
clearOneSignalNotifications
andcancelNotification
methods.- You must use them if you need to programmatically dismiss notifications otherwise they will be restored.
- Added
androidNotificationId property
toNotificationExtenderService.OverrideSettings
. - Since notifications are restored this fixes badge count out of sync issues.
2.4.3 Release
Fixed badge and button regression bugs
- Fixed 2.2.0 bug where if no launcher was set (no app icon) a null exception would be thrown.
- Fixed 2.4.0 bug where notification buttons would not work unless a NotificationExtender was setup.
2.4.2 Release
Fixed Rare ConcurrentModificationException error
2.4.1 Release
NotificationExtenderService property fix
- Fixed issue where some properties such as
additionalData
were not getting set.
2.4.0 Release
NotificationExtenderService and misc fixes
- NotificationExtenderService allows omiting of notificaions and overriding specific properties in your app's code. See the Background Data and Notification Overriding documentation section for more details.
- getTags now pulls from OneSignal instead of returning local values.
- Fixed a permissions crash affecting a small number of devices.
2.3.0 Release
Added setEmail, default accent color option, fixed badge issue.
- Added setEmail method.
- Added
com.onesignal.NotificationAccentColor.DEFAULT
manifest option. - Fixed issue a null context error with badge counts.
2.2.0 Release
Added Badge support
- Added support for Android badges. Supported on launchers by Sony, Samsung, LG, HTC, Xiaomi, ASUS, ADW, APEX, and NOVA.
- Counts are automatically set to the number of notifications shown in the Android notification shade.
- Also fixed issue with
com.onesignal.NotificationOpened.DEFAULT
setDISABLE
not skipping url notifications.
2.1.3 Release
Fixed class name conflict with RootTools and target manifest fix
2.1.2 Release
Fixes to deleteTags, getTags, postNotification, and REST calls
- Fixed bug where launch URLs were not opening on a closed app state when OneSignal init was called outside of the Application class.
- Fixed bug where deleting multiple already sync tags after sync would print a null error and local sync state would not save.
- Notification shade now closes when tapping on a notification action button when the app is infocus.
- Now checks for "errors" key and fires onFailure correctly in postNotification.
- getTags no longer throws null exception if called before OneSignal init is called.
- Improved non 200 OK response handling in the REST Client.
- Robolectric tests are now runnable from the command line / terminal and execute much faster.
2.1.1 Release
getTags null fix
- getTags would throw a null exception if tags were not set yet.