Open brandonSc opened 7 years ago
If you could send us a few things, it would help us debug this: 1) What version of GCore you are using (Google play services) 2) unlock your phone, wait 10 seconds, then then take a bug report and upload here
Those two things will help us get a better idea what is going on.
Sure, my Google play services version is 10.0.84, and here is a .zip of the bug report I captured:
Thank you. It's a holiday here in the US, we'll look at this starting tomorrow.
Thanks, enjoy the holiday.
So my Google Play Services auto-updated to version 10.2.91, and now Physical Web notifications are working again.
Great to hear
Hi @scottjenson, I'm involved in a project that uses the Eddystone Protocol, and I have the same problem, much more often with versions of Android 5.xx and 6.0.1, on iOS devices via Chrome I usually get on all devices Androids any version with the App Physical Web installed I get, however by the Nearby Native of Android in the versions above I can not receive. In all tests I have Location and active Bluetooth and Internet access. In some Vendor-Approved Versions, I solve the problem by placing Google Play Services Priority in Notifications. What can be happening with these 5.xx and 6.0.1 versions?
Hi,
After recently updating my Android version to 7.0 on my LG G5, Physical Web notifications have stopped displaying unless I have the Nearby app running. Once I open the Nearby app, the notification shows up (I can "swipe down" on the top of my screen and see the link to the Physical Web page). But if I kill the Nearby app from my app switcher, then the notification disappears again after a few minutes.
Before updating to Android 7.0, I used to see Physical Web notifications consistently without having to open the Nearby app. Other people's devices still pick up the notifications from the same beacon with out having their Nearby app running. Seems like this may be a bug with the new Android version on the LG G5.
Regards, Brandon