Ensure there is a clear divide between the two Bluetooth Data Transfer Modes #67
Labels
bug
Something isn't working
Comments
pr1sm
added a commit
that referenced
this issue
Mar 1, 2018
This commit fixes a bug that could occur when using CB transfers instead of MP. The sendData function runs at the correct time in all cases, but this is only required for MP transfers. During a CB transfer, this don't have a lasting effects, but does produce some red herring error messages. To fix this, a check was added to make sure we are performing a MP transfer before trying to send data. Issue: #67
pr1sm
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There are several places where we branch and perform different behavior based on the transfer mode active (Bluetooth Classic, or Bluetooth Low Energy). Each place should be checked to make sure we are performing the correct behavior based on the mode being used.
That is, if we are using BLE for transferring data, any functions related to BC must have no effect. Similarly, if we are using BC for transferring data, any functions related to BLE must have no effect.
The text was updated successfully, but these errors were encountered: