Ville Hakulinen
Ville Hakulinen
Sorry for the delay, I'm busy with other urgent things at the moment. I'll continue this once I'm able to.
There. Rebased, added docs and applied the iOS stubs.
In 62ac6221eb574a966152e618b38769fc52467c94, you removed the `BleManagerCompanionPeripheral` event. This causes diverge between code thats using "normal" methods of connecting, which have the `BleManagerConnectPeripheral` event available. Can you consider adding either the...
Oh sorry, my bad. You're right, it doesn't automatically connect. So same argument, but with `BleManagerConnectPeripheral` replaced with discover event.
Thats why it would need to have some flag in the returned object. Or restore the event that was removed.
It is being checked, or did I miss it on some code path?
the `getCompanionDeviceManager` is only called after the API checks. Isn't that enough?
Any chance to get the events removed in 62ac6221eb574a966152e618b38769fc52467c94 back? If its just matter of adding them back, or if you have an alternative design in mind but lack the...
Sorry, I might've been unclear what I'm asking for. What I want is to have a event based solution for discovering a companion device, i.e. `BleManagerDiscoverPeripheral` but for the companion...
I'm witnessing similar behavior. If the peripheral requires pairing before reading something but isn't accepting any pairing requests, the `read` resolves with `null` value.