Skip to content

Releases: OneSignal/OneSignal-Android-SDK

2.4.3 Release

21 Jun 01:54

Choose a tag to compare

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

17 Jun 22:39

Choose a tag to compare

Fixed Rare ConcurrentModificationException error

2.4.1 Release

02 Jun 18:30

Choose a tag to compare

NotificationExtenderService property fix

  • Fixed issue where some properties such as additionalData were not getting set.

2.4.0 Release

25 May 07:58

Choose a tag to compare

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

11 Apr 21:42

Choose a tag to compare

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

01 Apr 20:53

Choose a tag to compare

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 set DISABLE not skipping url notifications.

2.1.3 Release

02 Mar 06:37

Choose a tag to compare

Fixed class name conflict with RootTools and target manifest fix

2.1.2 Release

29 Feb 19:42

Choose a tag to compare

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

16 Feb 04:47

Choose a tag to compare

getTags null fix

  • getTags would throw a null exception if tags were not set yet.

2.1.0 Release

13 Feb 05:18

Choose a tag to compare

Simpler customization of open action and misc fixes

  • Now supports application meta-tag 'com.onesignal.NotificationOpened.DEFAULT' with the value 'DISABLE' to turn off the launching of the main Activity.
    • No longer need to create a BroadcastReceiver just to have your NotificationOpenedHandler fire in your Application class.
  • Fixed issue with deleteTag not working when the value is a number.
  • Added a number of checks around tag methods to make them consistent to what the REST API supports.
  • Fixed location warning.
  • Reverted back to Robolectric 3.0 as custom shadows in 3.1 were not working.