Closed dennisheerwb closed 1 month ago
Unfortunately, we generally don't get any of this information passed back from OS itself.
Android simply returns the state as disconnected (source).
iOS gives an error which is converted into a string and reported back to the caller (source).
While I agree the information would be useful, I don't know what can be done here to improve the situation.
Is your feature request related to a problem? Please describe. For better error investigation on client devices that we do not have access to, it would be helpful to determine the reason why Bluetooth has been disconnected.
Describe the solution you'd like I hereby propose an enhancement to the
onDisconnect
-callback of the connect method to provide the disconnect reason, ideally in alignment with theHCI_DISCONNECT
specification.