Closed luciofr closed 7 years ago
LOC-Place
commented
7 years ago @luciofr: Do you use an URL shortening service? Which one?
As you know, we have the same issues - but as menitiones already under #908 with an intermittently behaviour. Current status is still not good, but we do think that he reascon could be found with the shortening/resolution service communication.
luciofr
commented
7 years ago Hi @ LOC-Place, @mmocny asked me to open another call so someone on his team could talk directly to me, so I created # 909. Regarding the URL shorter, we do not use any, because of the URL byte limitation, we use a concatenation with Major and Minor in Hexa for each Beacon, so each Beacon has a unique URL, and the information that is in our Platform can Be changed at any time, which works perfectly for iOS and the Phisical Web App, but the native Android Nearby has this intermittent problem. Our URLs always go through the validator.
jfarfel
commented
7 years ago Hi @luciofr, sorry about the delay, and about the flaky behavior. I'm on the Nearby team. There's a new version coming out within a week or two that may help, but here's some info to assist in debugging:
adb shell dumpsys activity service com.google.android.gms/.nearby.messages.service.NearbyMessagesService
adb shell dumpsys activity service com.google.android.gms/.nearby.discovery.service.DiscoveryServiceHi @mmocny and @jfarfel, we have members of our Team in San Francisco, is there any way we can schedule a time for our Teams to discuss the matter in person? We have dates available until 08/2017.
luciofr
commented
7 years ago Hi @scottjenson, @mmocny and @jfarfel, I continue with issues related to Nearby, until I received an update from Android, but it seems that nothing has changed. Through Chrome notifications on iOS or through the App Physical Web, everything works perfectly, however, through the native Nearby nothing happens. Nearby has no shortcomings so I can send it to you as requested, it simply seems to look for the near Beacons, but without displaying any URLs. We are in the middle of a Proof of Concept with one of the biggest Players in Latin America with everything already approved, only need to run Eddystone natively on Android. I need your feedback as soon as possible.
luciofr
commented
7 years ago Hi @scottjenson, @mmocny and @jfarfel, we were able to get great results with Nearby native Android, and we'd like to share it with you. 1) we were doing some jumps with our URL, which after reading several posts we realized that it was one of the service failure factors that remained working on Physical Web and iOS via Chorme notifications. 2) We modified in our Beacon the value of the Measured Power Value, which with the values that were set worked perfectly in Physical Web and iOS via Chrome Notifications and that after the last updates of Android stopped . Today, July 3, 2017, we have all our Beacons returning to normal via protocol Eddystone. Thank you very much for the feedback.
jfarfel
commented
7 years ago Hi Lucio, thanks for the updates! Sorry I wasn't available to get back. Glad to hear it's working now. Yes, it could have been due to the URLs used. This FAQ gives some context about why a nearby link may not appear in Google > Settings > Nearby, or why it may appear there but not result in a notification. https://developers.google.com/nearby/notifications/developer_faq
Hi @mmocny, I'm having recurring issues with the Nearby native Android, very intermittent, mostly in versions of Android 5.x.x and 6.x.x, but I've already called called Clients with other versions of Android. What always caught my attention is that the App Physical Web always receives the URLs, almost never fails what I can no longer talk about Android's Nearby. Follow the screen now. I'm from Porto Alegre - RS - Brazil.