Question: BleErrors being captured by Sentry even when caught

[jcstange]

Prerequisites

• I checked the documentation and FAQ without finding a solution
• I checked to make sure that this issue has not already been filed
• I'm sure that question is related to the library itself and not Bluetooth Low Energy or Classic in general. If that so, please post your question on StackOverflow.
• I'm running the latest version

Question

We are daily getting these errors on Sentry even though we are catching the error on our application:

Sentry says that it is an unhandled Promise rejection. However in our app it is handled correctly and we have no further problems with it besides the insistent logs.

Is there a way to clean up these errors? Or at least route it through our app. Because now it seems that it goes from parseBleError -> _callPromise and it's thrown in https://github.com/babel/babel/blob/0a0dcd8bbe3c25fcfb90973eb29fcb96137ed211/packages/babel-runtime-corejs3/helpers/esm/asyncToGenerator.js#L20

[aliberski]

@jcstange You’re right to flag this.
This is likely caused by an internal promise path in the library (onStateChange(..., true)) that can reject without a handler, which Sentry reports as an unhandled rejection even if your app catches BLE errors elsewhere.

I’ve prepared a patch to handle that rejection internally so it won’t be reported as unhandled.

As a temporary workaround, avoid emitCurrentState: true and call manager.state() separately with your own .catch(...).