3.15.4 Release

In-App Message fixes and DB transaction fix

• Fixed In-App Message where redisplay option did not work with session duration
  • PR #1149
• Fixed In-App Message display under Activity issue when pressing back button
  • PR #1171
• Fixed rare IllegalStateException exception when SDK would internally end the transaction
  • PR #1178

4.0.0 Beta2

Major Release 4.0.0 Beta2

⚠️ This is a major beta release which contains breaking API changes.
See the full list of changes along with step-by-step guides to upgrade.
https://documentation.onesignal.com/docs/mobile-2020-api-migration-guide

❓ Please provide feedback and bug reports with the beta version included in the title to this repo's issue tracker.
https://github.com/OneSignal/OneSignal-Android-SDK/issues

Changes from 4.0.0-Beta1

• Fixes from 3.15.2 and 3.15.3 Release
• Fix In-App Message not being redisplay by session duration
  • PRs #1149 & #1171
• Fixed In-App Message displaying issues when back button pressed
  • PR #1171
• setEmail, NPE fixed if called before SDK was initialized
  • PR #1168
• Fixed foreground detection with Activity used with initWithContext
  • PR #1174
• Fixed rare SQL IllegalStateException exception
  • PR #1178
• Updated OSPermissionState & OSSubscriptionState property names to match OSDeviceState names
  • PR #1177
• Removed getPermissionSubscriptionState, use getDeviceState instead
  • PR #1187
• Fixed wrong boolean logic with disablePush
  • PR #1177
• Added Support for FireOS 7 (only supported up to FireOS 6 before this)
  • Issue #890
  • PR #1184
• Background location support for Android API 29 (Android 10)
  • PR #1185
• Removed getVibrate and getSoundEnabled
  • Create Notification Categories instead to customize via the OneSignal dashboard or via the native Android Notification Channels API.
  • PR #1188

4.0.0 Beta1

Major Release 4.0.0 Beta1🛠️

⚠️ This is a major beta release which contains breaking API changes.
See the full list of changes along with step-by-step guides to upgrade.
https://documentation.onesignal.com/docs/mobile-2020-api-migration-guide

❓ Please provide feedback and bug reports with the beta version included in the title to this repo's issue tracker.
https://github.com/OneSignal/OneSignal-Android-SDK/issues

3.15.3 Release

Fixes for SQLiteDatabaseLockedException, getDisplayPosition NPE, Badges for Asus

• Additional fixes for SQLiteDatabaseLockedException. PR #1109
• Fix for rare crash when pressing back button while dismissing an In-App Message.
  • Fixes null getDisplayPosition error. PR #1119
• Fixes issue with badges not working on Asus if you enable proguard / R8. PR #1111

3.15.2 Release

Fixes for Background Location Update, Misleading Email Id Log, Class Detection for Proguard Optimize, ANR on_focus from MainThread, Android 6 API 23 IAM bug

• Fix InterruptedException from background location update #1008
  • InterruptedException was due to a circular initialization of the JobScheduler
  • Avoid reschedule an already scheduled or running service, but instead do it in jobFinished
  • Fix misleading email id log, email id can be null, downgrade log to info level, keep error level for user id
• Modify class detection for proguard optimize
  • Added a method call to prevent it from incorrectly optimizing, class.getName()
• Fix ANR due to on_focus call being called from MainThread
  • All remote calls now get a MainThread check
• Fix bug when showing an IAM on Android 6 API 23 devices #930
  • Elevation must be removed before animating IAM and then added back on animation end

3.15.1 Release

Added HMS bridging methods

• Please make sure to follow Step 6 - Compatibility with other HMS push libraries or your own HmsMessageService class if it applies to your app.
• Added HmsMessageService bridging methods.
  • If you use another HMS push sdk / library you or have your own HmsMessageService please forward these events to
    OneSignalHmsEventBridge
  • PR #1077

3.15.0 Release

Huawei (HMS) Push Support

Follow the OneSignal - Huawei SDK Setup guide to get started!

3.14.1 Release

Fixed 3.14.0 SQLite migration & Lock issues, Fixed IAM Direct Outcome detection

• Fix SQL migration issues
  • Fix DB migrations not applying in 3.14.0 when coming from 3.11.0 or older.
    • Issue #1033
    • PR #1053
  • SQLite migration failure handling.
    • PR #1056
• Fixes for SQL DB lock issues
  • Issue #988 & #1039
  • PR #1050
• Fixed issue where an IAM could be counted as Direct outcome when it should not. PR #1049
• Fixed NPE with OneSignalCacheCleaner. PR #1047

3.14.0 Release

DB Lock Issue Fix, Location Permission Prompt Warning, Location Settings Prompt, IAM Redisplay Count on Failure Fix, Rare IllegalThreadStateException Fix, IAM Outcome Tracking

• DB Adjustments for Lock Issue #988
• Fixed IAM ANR with getSync to get on OneSignalRestClient. PR #1015
• Location Permission Prompt Warning
  • Warn the user through preview IAMs when location permission setting is not added to the application's AndroidManifest.xml.
• Add Settings option to denied location prompt
  • When user selects "Do not show again" in permission prompt, we show a settings prompt in replace on next action.
• IAM Redisplay Count on Failure
  • When IAM request fails we should not increment redisplay count.
• Rare IllegalThreadStateException start()
  • When calling Thread.start() there is no guarantee that the thread has started after finishing or that is may have already completed.
• IAM Outcome Tracking
  • SDK now tracks Push Notifications and In-App Messages in regard to outcomes

3.13.2 Release

deviceType iOS Issue Fixed, WritePrefHandlerThread startThread Issue Fixed, SQL DB Issue Fixed

• Fix for Android deviceType being marked as iOS because of init not being called before a player sync (on_session) was occurring and in cases where notification opens (opened) occurred. So in this case we fixed two bugs.
• WritePrefHandlerThread startThread Issue Fixed #917
  • Creating a RuntimeException using the Throwable signature to throw without having to attach Exceptions all the way up the stack.
• SQL DB Issue Fixed #988
  • We open a DB instance and leave it open across the whole application and let the system handle closing it when necessary