fix_ios_serviceUUID_assigned_numbers #258
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
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.
Fix to handle Short UUID and Long UUID... In case the hardware platform returns a Long UUID when we were expecting a Short UUID.
Note Short UUIDs are usually expected when the Service UUID is an Bluetooth Assigned Name...
For some reason (whether due to arduino BLE programming; or, iPhone version) the Assigne Name service UUID was being presented in Long UUID format, whereas BLE plugin was assuming it should be Short UUID.
This change will cause BLE to support Assigned Names as Long or Short UUIDs (regardless of how the platform returns them)