Fix issue with null BluetoothDevice field. #359
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The exception was thrown on reading device field which was null. The property hasn't been assigned, because callbacks were invoked in unforeseen order. To fix the issue assigning device was moved to before() callback and to avoid resuming twice the same coroutine the resume() method has been moved to done() callback.
philips77
approved these changes
Feb 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The exception was thrown on reading device field which was null.
The property hasn't been assigned, because callbacks were invoked
in unforeseen order. To fix the issue assigning device was moved
to
before()callback and to avoid resuming twice the same coroutinethe
resume()method has been moved todone()callback.