5.1.17

🐛 Bug Fixes

• Fix "could not be instantiated" exception when; some modules are omitted AND android.enableR8.fullMode is enabled. (#2136)
• Reverts a breaking change from release 5.1.16 (do not use) that causes a crash when calling requestPermission in a separate thread right after initWithContext. (#2141)

5.1.16 (⛔️ Do not use!)

⚠️ Do not use ⚠️

Please use Release 5.1.17 or newer

Release 5.1.15

🐛 Bug Fixes

• Xiaomi notification click was not foregrounding app #2129
• FCM push token was not being refreshed (#2125, #2118)
• Poll for notification permission changes to detect permission change when prompting outside of OneSignal #2112
• WorkManager fixes when the app uses a custom WorkManager #2122

✨ Improvements

• Cold start creates new session and refreshes the user from the server #2113

Release 4.8.10

🐛 Bug Fixes

• The getter for WorkManager considers the app context in #2123

Full Changelog: 4.8.9...4.8.10

5.1.14

🔧 Maintenance

• Add the ability to immediately discard a notification by calling preventDefault(discard: true) (#2094)
• Bump minimum FCM version to 21.0.0. (#2102)
• Immediately process pending operations when privacy consent goes from false to true. (#2109)

🐛 Bug Fixes

• Fix a bug causing OneSignal.getNotifications().requestPermission with the Java Continuation not firing when permission was already granted. (#2093)
• Fix Operation Model Store adding duplicate operations when the same ones that were previously added to the store and persisted, are re-read from cache. (#2099)
• Fix a bug causing clicking an unexpanded group notification results in only registering the click result for the final notification in the group. (#2111)

5.1.13

🐛 Bug Fixes

• [Fix] grouping skipping opRepoPostCreateDelay, causing operations being applied out of order when multiple login operations are pending. (fixes issue since 5.1.10) (#2087)
• [Fix]: Cancelling permission request dialog does not fire continuation (#2085)
• [Fix] RecoverFromDroppedLoginBug not running in very rare cases (#2084)

5.1.12

🐛 Bug Fixes

• Fixes IndexOutOfBounds exception from the 5.1.11 release. It was thrown from OperationRepo.loadSavedOperations if app was opened offline, some operations done, and then the app is opened again. (#2081)
• Addressed compatibility with AGP (Android Gradle Plugin) 7 and older.
  • Reverted back to using JDK11 for release builds, the 5.1.11 release was built with JDK21 which caused this.

🐛 Bug Fixes and 🔧 Maintenance from 5.1.11 included in this release

• Fix the ANR issue caused by prolonged loading of OperationRepo and potentially by extended holding of the model lock during disk I/O read operations. (#2068)
• Add HTTP header OneSignal-Install-Id that allows the OneSignal's backend know where traffic is coming from (#2072)

Release 5.1.11 (⛔️ Do not use!)

⚠️ Do NOT use this version ⚠️

Contains a runtime bug and a build incompatibility:

• Unintentionally only build compatible with AGP 8 (Android Gradle Plugin) and newer.
• App may crash with IndexOutOfBoundsException on app startup if the device was offline in some cases.

Release Notes:

🔧 Maintenance

• Add HTTP header OneSignal-Install-Id that allows the OneSignal's backend know where traffic is coming from (#2072)

🐛 Bug Fixes

• Fix the ANR issue caused by prolonged loading of OperationRepo and potentially by extended holding of the model lock during disk I/O read operations. (#2068)

Release 5.1.10

🔧 Maintenance

Network call optimizations

• Handle HTTP header Retry-After from responses from OneSignal (#2064)
• Avoid unnecessary user fetchs; on first app open and first login (#2061)
• Further improve batching by restarting OperationRepo's delay on every enqueue call (#2060)
  • Same "let the dust settle" strategy used to combine changes into fewer network calls as 4.x.x

🐛 Bug Fixes

• Handle incorrect 404 responses; add a delay after creates and retries on 404 of new ids (#2059)

📖 Documentation

• Update Readme and Migration_Guide with migration advisory (#2054)

Release 4.8.9

🐛 Bug Fixes

• Rare Android 12 only crash - OSTaskController on LinkedBlockingQueue.poll()
  • 5.x.x versions were never affected by this issue.
• Corrected DeadSystemException handling
  • Note, DeadSystemException is not a root cause crash. These are a red herring so we are omitting them from crash reports.
  • 4.8.8 introduced handling, but was not effective until this version