-
Notifications
You must be signed in to change notification settings - Fork 485
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
[Help]: onValueReceived not called for writes #608
Comments
it is only called when a value is received, not sent. yes you could call or you could create your own extension function |
But I'm considering changing |
I did call |
Sorry, I don't understand you but normally you should |
pubspec.yaml
|
Ok, I'll try |
@chipweinberger
|
Note that 1.16.12 is fine, but |
There is another problem, when I click to turn off the Bluetooth adapter, turn it on again, and start scanning and connecting, the connection times out.
|
released 1.17.0
Does this still happen on 1.17.0? please open a new issue |
Requirements
FlutterBluePlus Version
1.16.10
Flutter Version
3.3.2
What OS?
Android
OS Version
Android 12
Bluetooth Module
nRF5
Ask your question
I would like to ask the response logic of onValueReceived.
Is it necessary to call "read" after each "write" command, and then "onValueReceived" will receive the message returned by the device?
onValueReceived should have received a message from my device after each write command.
But now after sending the write command several times in a row, onValueReceived may lose the messages returned by the device.
Logs
The text was updated successfully, but these errors were encountered: