Skip to content
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.

Writing wrong configuration into beacon #258

Open
g-ortuno opened this issue Aug 20, 2015 · 0 comments
Open

Writing wrong configuration into beacon #258

g-ortuno opened this issue Aug 20, 2015 · 0 comments

Comments

@g-ortuno
Copy link
Contributor

From @coomby:

Using CSR1010 Tag board with Physical Web - proven working with Eddystone Android authenticator app.
Using Android 5.1 this is the workaround i have use to change the URL:

This is the only way I can program a URI into the beacon and have it show:-

* Run Eddystone Android Authenticator App first. This ends up putting a https://www. weblink in the beacon which is picked up by the Physical Web Android App...
* Downoad Blesh Physical Web App - https://play.google.com/store/apps/details?id=com.blesh.physicalweb&hl=en_GB
* Continue as Guest then use their Config Uri button to enter new Uri into Beacon
* Revert back to "standard" Physical Web App to view Beacon Uri being shown.
If ever you try to program Url with the Physical Web App alone it ends up not being discovered.

So yes looks like a bug in the Physical Web Android App..
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant