Skip to content
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

Eddystone URL problem #23

Open
TFoxik opened this issue Apr 20, 2017 · 0 comments
Open

Eddystone URL problem #23

TFoxik opened this issue Apr 20, 2017 · 0 comments
Labels

Comments

@TFoxik
Copy link

TFoxik commented Apr 20, 2017

Hi, Id1 is returning wrong data. The problem is that when you set the beacon for maximum length (which can be up 20 bytes ... it is frame type (1byte), tx power (1byte), URL scheme (1byte) and 1-17 bytes for URL) id1 contains also URL scheme as the first byte. Therefore the last byte of the URL is not shown.

Can you pls test this?

Example:
if you set a beacon for http://aaaabbbbccccdddd.com id1 returns https://aaaabbbbccccdddd instead of aaaabbbbccccdddd.com ("http://" and ".com" can be converted to 1 byte each but the difference is that https:// or other prefixes should be in separate byte flag, not in URL)

I hope it is understandable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants