marcwan
commented
6 years ago Hey @NikitaGhanwat,
Thanks for the report. So, one of the biggest problems we have w BeaconTools is that the individual beacon vendors have wildly differing implementations of the GATT Configuration protocol that we use to implement EID configuration.
It's highly likely that these minewtech beacons are doing something funny that the BeaconTools apps are not quite able to deal with correctly.
I'll try to get some of them here in London and see if we can't debug them, but until that happens, your best bets would be to:
- Perhaps try a different brand of beacon.
- Contact the beacon vendor and ask if they can make sure their beacons work with the official Beacon Tools iOS / Android apps properly.
Thanks!
NikitaGhanwat
Hi , I am not able to detect EID registered beacons from the sample applications . Do i need to setup anything else for the same . i have integrated the APP_KEY from google console and have enabled the services also .
Reference : 1.I am trying to register Beacon (minewtech Eddystone) through "Beacon Tools" iOS application using Broadcast Profile "EID". But i got error while registering.
2.Same beacon registration succeed from Android version of "Beacon Tools". I have followed all steps in https://developers.google.com/nearby/messages/ios/get-started tutorial but unfortunately application don't found any beacon even if beacons are registered(registered from android app) on google beacon dashboard.
3 .I have downloaded sample application from https://github.com/googlesamples/ios-nearby and run it, but in this app also registered beacon was't detected. Where as in Android app it works fine. I have created APP_Key from console project and used it while creating GNSMessageManager object.
Let me know if any additional setup require for iOS. Please Find attached screenshot for reference.