google / physical-web

The Physical Web: walk up and use anything
http://physical-web.org
Apache License 2.0
6k stars 665 forks source link

branch.io dynamic URL doesn't work when used as a physical web link #892

Open chetstriker opened 7 years ago

chetstriker commented 7 years ago

I have a branch.io URL at https://p9o0.app.link/jay if I open it directly on my phone with the app installed then it opens the app at URI viewboost:// like it should. If i open the link and it's not installed then it also works great and directs me to the install page. My problem is that when I add https://p9o0.app.link/jay to my beacon's eddystone url, it just takes me directly to http://bellemachine.com/viewboost to install the app whether the app is installed or not. So I know that the link by itself works fine, only when trying to add it as the eddystone url does it fail. I assume it's trying to reverse lookup the final destination directly from the beacon and broadcasts the URL of the final destination because the beacon doesn't have the app installed and so just gives the end point to the phone clicking on the link instead of the entered address (https://p9o0.app.link/jay) directly. Is there some sort of workaround for this? or are dynamic deep linking addresses from sites like branch.io not possible to use with beacons? And if not, is their another recommended way? It seems like it would be less ideal to have the beacon always broadcasting the install web only and separately writing something else in the app to monitor if a particular beacon is near and create a notification that data is available.