Bug Summary
Since we start SdlServices from the RS with the pending intent it is now likely that there could be a potential remote exception of the SdlService not calling startForeground in time. We should add that exception to the handler and keep it moving.
Reproduction Steps
- Connect SDL app normailly via Bluetooth on Androud 12+ device
- Download and install a second SDL app that SdlService will not call to start the foreground.
Expected Behavior:
We would like for the SdlBroadcast receiver's uncaught exception handler to handle it and keep moving.
Observed Behavior:
App crashes, and we get an ANR
Which projects have you seen this bug on?
No response
Android Version(s)
12+
Android Device(s)
Pixel 4a
sdl_java_suite Version
5.6.1
Testing Environment(s)
Relevant log output
No response
Bug Summary
Since we start SdlServices from the RS with the pending intent it is now likely that there could be a potential remote exception of the SdlService not calling startForeground in time. We should add that exception to the handler and keep it moving.
Reproduction Steps
Expected Behavior:
We would like for the SdlBroadcast receiver's uncaught exception handler to handle it and keep moving.
Observed Behavior:
App crashes, and we get an ANR
Which projects have you seen this bug on?
No response
Android Version(s)
12+
Android Device(s)
Pixel 4a
sdl_java_suite Version
5.6.1
Testing Environment(s)
Relevant log output
No response