You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.
If you try these URLs for yourselves, you will notice that no Favicon will be shown.
We haven’t been able to see a clear pattern why this doesn’t work for some websites.
We don’t know the heuristics used by Nearby Notifications and we cannot ask these website owners to change their implementations. So, there’s not much we can do from our side.
Did you have similar issues and can confirm this problem?
The text was updated successfully, but these errors were encountered:
Tested bahn.de on one of my beacons (Eddystone URL mode), then checked result in Nearby app, and favicon did not appear. So I can confirm the problem/issue is the same here in the USA for this specific website.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In our experiments we found a lot of Nearby notifications without a Favicon, even though the configured URLs use Favicons which are shown by browsers.
Our customers find this “branding” very important, hence I’m opening this report here. Additionally, I've send a bug report as described here: https://github.com/google/physical-web/wiki/Taking-a-Nearby-Bug-Report.
Here’s a list of example URLs:
https://www.facebook.com
https://www.xing.com
https://www.bahn.de
https://www.rainbow-parking.de
https://www.awk.de
https://www.imm-hamburg.de
https://isarfunk.de/
If you try these URLs for yourselves, you will notice that no Favicon will be shown.
We haven’t been able to see a clear pattern why this doesn’t work for some websites.
We don’t know the heuristics used by Nearby Notifications and we cannot ask these website owners to change their implementations. So, there’s not much we can do from our side.
Did you have similar issues and can confirm this problem?
The text was updated successfully, but these errors were encountered: