fix eddystone packet header byte order #4
Merged
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.
I notice that is I set the tx power ,my app was not recognizing the URL in the Eddystone beacon.
Lookin at the spec
https://github.com/google/eddystone/tree/master/eddystone-url
I think the tx_power and url scheme fields are reversed
swapping them seems to work, my App now set the URL with a non-zero tx_power.
before , with tx_power = 0 it was still a "valid" url_scheme so it worked until tx_power was set.
reported by receiving app (IOS Locate Beacon)
before change
after change