You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since the channel delete code as added back in last release to address some phones not clearing the notification, a new issue has appeared with Samsung devices. These devices are not properly deleting and recreating the notification channel and therefore it throws a fatal exception. While the code itself in the library should not allow this to happen, it seems the OS has other issues.
Reproduction Steps
Star SDL connection like normal
Disconnect
Restart SDL connection, should crash
Expected Behavior
Notification is displayed and clears properly.
Observed Behavior
Notification is not created, RS not started, app experiences fatal crash
Fatal Exception: android.app.RemoteServiceException
Bad notification for startForeground: java.lang.RuntimeException: invalid channel for service notification: Notification(channel=sdl_notification_channel pri=0 contentView=null vibrate=null sound=null tick defaults=0x0 flags=0x40 color=0x00000000 vis=PRIVATE semFlags=0x0 semPriority=0 semMissedCount=0)
Bug Report
Since the channel delete code as added back in last release to address some phones not clearing the notification, a new issue has appeared with Samsung devices. These devices are not properly deleting and recreating the notification channel and therefore it throws a fatal exception. While the code itself in the library should not allow this to happen, it seems the OS has other issues.
Reproduction Steps
Expected Behavior
Notification is displayed and clears properly.
Observed Behavior
Notification is not created, RS not started, app experiences fatal crash
OS & Version Information
*Devices: Samsung S10+, Note 10+, S10, S9+, S9,
The text was updated successfully, but these errors were encountered: