3.11.4 Release

Groupless Notification and In-App Message Dragging Action Fix

• Fixed getActiveNotifications() crash related to NotificationManager 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
  • Regression bug from 3.11.0. Issue #811, PR #825
• Fixed nested sendTags calls.
  • Issue #671
• Fixed In-App Messaging crash when opening preview in rare cases
  • #831
• Fixed crash when rotating the device while an In-App Messaging is about to show
  • #831

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
  • Issue was related to Android's auto grouping feature.
  • Now counts the most recent notification in the group being opened when the summary notification is tapped.
  • Issue #666 and PR #782
• 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

3.11.0 Release

In-App Messages

• See the OneSignal In-App quickstart guide for more details.
• Notification Channels / Categories, added invalid format handling to LED colors.
  • PR #775
• Fixed com.onesignal.PrivacyConsent AndroidManifest.xml check when using newest init method.
  • PR #786
• Fixed location permission prompting and session count / time tracking after privacy consent is accepted.
  • PR #772

3.10.9 Release

Fixes getTags ConcurrentModificationException

• Fixes issue #708

3.10.8 Release

Fixed remote params & WrapperWorkItem.complete issues

• Fixed remote params NPE. Issue #729
• Fixed IllegalArgumentException Thrown from WrapperWorkItem.complete. Issue #644

3.10.7 Release

Restore Logic includes TTL, network optimizations, and misc fixes

• Filter notifications past their TTL when restoring them back to the shade. PR #720
  • Restoring logic happens when the app is cold started, device reboot, or app is updated.
• Caching for REST GET calls by handling 304s. PR #723
• Omit network retries if HTTP 403 is returned. PR #724
• Added SDK-Version HTTP header to all requests PR #721
• Registration retrying now does not require a new session to resume retrying if app was interrupted by an app cold restart.
  • PR #718

3.10.6 Release

Badge Count, Notification Overflow, and getTag Fixes

• Badge count now uses notification count from system
  • Fallback for Pre-Android 6 to use internal count.
• Omits running notification restore if notifications are disabled.
• Fixes new notifications not showing if there were 49 notifications in the shade
  • Now handles removing oldest notifications to make room for new ones.
• Clear notifications methods now works even if provideUserConsent was not accepted.
• Badge counts are now updated after restoring notifications.
• getTags now supports multiple callbacks
• OneSignal.setAppContext is now public.
  • Only needed if you need to call provideUserConsent before initializing OneSignal.

3.10.5 Release

External User ID Support

• This update adds new methods (setExternalUserId(string) and removeExternalUserId) allowing you to target push notifications using your own custom user ID's instead of having to store OneSignal player ID's.

Catch for SecurityException from JobIntentService & Misc Improvements

• Removed ACTION_BOOT_COMPLETED for BOOT_COMPLETED
  • ACTION_BOOT_COMPLETED is invalid, BOOT_COMPLETED is the correct intent action
• Catches security exception from Job Intent Service
  • Fixes issue #673