Android does not receive the Eddystone URL

[luciofr]

Hi everyone, I'm involved in a Project that uses the EddyStone Protocol, but iOS devices or Androids with the App Physical Web easily receive the notifications, the problem occurs with the native Android Nearby that several times does not receive, I realized that any version 5.xx or 6.xx present the problem further. In all tests I have Location and Bluetooth enabled and Internet access. Is there any extra setting for the native Android Nearby to run as the Physical Web App?

[montelco]

I've also been working on a project that uses the Physical Web for interacting with content and a friend noticed that without the app it wasn't working. It works on my device (Google Pixel), but Samsungs seem to be a particular issue device and seeing as they make up the vast majority of the US Android market, that makes it of particular concern. @scottjenson Is this related to the issue on #882 whatsoever?

[luciofr]

Hi @scottjenson, why the native Android Nearby does not work the same way as the Physical Web application?

[parasitecruncher]

Hi @luciofr I did this a long time back with chrome's physical web enabled and it worked fine. Does Chrome also fail like Nearby?

[luciofr]

The latest Android updates have changed Nearby from Chrome, which has gone down as well in Android 5.xx or 6.xx, my question is that the Physical Web Application never crashes, so because the native Android Nearby does not same thing?

[luciofr]

Hi Mr. @scottjenson, would it be possible to check what might be happening? The Physical Web Application receives the URL, but the same device, by the Nearby Native Android does not. See the screens below: