Closed edent closed 8 years ago
Use this tool: https://beaufortfrancois.github.io/sandbox/web-bluetooth/eddystone-url-config/index.html
You may need Chrome 53 and you will have to enable web bluetooth
That works on Android Chrome! Many thanks.
Any reason why it isn't part of the app? Very confusing!
The app is a place for us to try experimental features, and now that we have a primary configuration utility (the web tool) there's no need for a configuration feature in the prototype app.
I get that - and it's your app to do with as you please - but how was I supposed to find that link?
The documentation still shows configuring in app. If I hadn't read the changelog in Play Store, I'd have thought my tokens were broken.
Thats a good point, we should have updated the web page to remove that confusion.
On Mon, Sep 12, 2016 at 8:23 PM, Terence Eden notifications@github.com wrote:
I get that - and it's your app to do with as you please - but how was I supposed to find that link?
The documentation https://github.com/google/physical-web/blob/master/documentation/android_client_walkthrough.md still shows configuring in app. If I hadn't read the changelog in Play Store, I'd have thought my tokens were broken.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/google/physical-web/issues/826#issuecomment-246461633, or mute the thread https://github.com/notifications/unsubscribe-auth/ABAbujkTPJUJv9llNLj5Q_ulN_Sbwzuoks5qpabAgaJpZM4J65iN .
@edent FYI http://cf.physical-web.org is the canonical URL
@beaufortfrancois thanks! Is that linked or documented anywhere?
Yes, you can see it in the "Configure beacons" section in https://google.github.io/physical-web/resources
I notice that the latest release of the Android client doesn't allow people to configure Beacons any more.
How do I change the eddystone destination of the V2 beacon Google gave me?