Closed BlissChapman closed 11 months ago
@Andrey1994 this will probably also fix the issues that you saw.
Yes, I saw this PR, thanks! At least should not hang in deadlock, and maybe will solve the issue completly
I'm quite mad that I missed that detail in the documentation. Given that they have callbacks for failed connections, it seems dumb that the user has to manually implement their own timeout logic.
Corebluetooth docs:
Attempts to connect to a peripheral don't time out
. SimpleBLE should expose a connectWithTimeout method to handle this flow gracefully for the consumer.