-
-
Notifications
You must be signed in to change notification settings - Fork 308
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WinUI Call to DisconnectDeviceAsync
may not complete.
#850
Comments
Hi @axa88, I'm the friendly issue checker. |
Hmm I see this issue has some history perhaps #788 |
Yes I agree #788 is the same... It is quite annoying Windows API doesn't have a disconnect method. I can give it yet another shot before next release. |
@AskBojesen During initial observations of this issue, I note a that after
Unfortunately as a symptom this now unusable device is left in the library cache if you will, and nothing, not even toggling Bluetooth on/off, will remove it. It cant be reacquired/replaced and the result is a catastrophic state. Hopefully you find a solution. |
This doesn't work for me, might you be able to provide any other info/advice to recover from this state? If you hadn't found these references already: |
Call to
DisconnectDeviceAsync
may never complete.The call doesn't take a
CancelationToken
, perhaps it should.It might take several Connect/Disconnect cycles, but eventually
DisconnectDeviceAsync
will hang.Hadn't noticed this behavior in v3.0.0, nor on
Android
Steps to reproduce
Connect/Disconnect
Observe eventually a call to
DisconnectDeviceAsync
will not completeExpected behavior
the call completes
Actual behavior
it doesn't complete
Crashlog
none
Configuration
Version of the Plugin:
3.1 rc1
Platform:
Device:
The text was updated successfully, but these errors were encountered: