search

googlesamples / ios-nearby

69 stars 30 forks source link

Cannot see Eddystone beacons #11

Closed rizzeeb closed 8 years ago

rizzeeb commented 8 years ago

Hello - nearby message pub/sub is working; I've added the GNSStrategy for Beacon scanning and in the console, I see the message that Beacon Scan started, however, I do not see the beacons, and hence do not see the beacon content. In the iOS-nearby code, I've added the same namespace/type combination but am not seeing the beacons even though I can see the Eddystone beacons here - https://github.com/google/beacon-platform/tree/master/samples/ios (under Search using the Attachment-Type filter)... Finally, I've added a URL to the Nearby Notifications (in the Beacon Dashboard), but they do not show up (under the Chrome widget, similar to other Eddystone URL that I see under that widget)..

Thoughts?

dan-webb commented 8 years ago

Hello, Sorry you're having trouble getting beacon scanning working. It can be difficult because so many things have to be set up just right.

Some questions for you:

  1. Are you using the deprecated GNSStrategy to enable beacon scanning? If so, try using deviceTypesToDiscover and GNSBeaconStrategy instead. See the API docs at https://developers.google.com/nearby/messages/ios/get-beacon-messages.
  2. Are your beacons registered with the same Google developer project (https://console.developers.google.com/) that your iOS app is using? Use the new Beacon Tools apps for iOS to register them and attach messages (https://developers.google.com/nearby/messages/ios/get-beacon-messages). In your subscription, don't pass in a namespace or message type, and it should receive all messages from all nearby beacons that have been registered with messages attached.

If this doesn't help, then let me know and we'll debug further.

rizzeeb commented 8 years ago

Thanks.. I modified the code to not use GNSStrategy but still cannot see the beacons – Here is a snippet from the Log Message - “NearbyMessagesExample[224:7450] Report RPC request: 3 token(s), 0 beacon(s), 6 directive(s)"

I did confirm that the beacons are registered under the same project… Let me know of a few time slots that work for you tomorrow and I’ll send a webex/zoom meeting invite.. Thanks for all your help…

From: Dan Webb notifications@github.com<mailto:notifications@github.com> Reply-To: googlesamples/ios-nearby reply@reply.github.com<mailto:reply@reply.github.com> Date: Monday, June 13, 2016 at 10:21 AM To: googlesamples/ios-nearby ios-nearby@noreply.github.com<mailto:ios-nearby@noreply.github.com> Cc: Rizwan Patel ripatel@caesars.com<mailto:ripatel@caesars.com>, Author author@noreply.github.com<mailto:author@noreply.github.com> Subject: Re: [googlesamples/ios-nearby] Cannot see Eddystone beacons (#11)

Hello, Sorry you're having trouble getting beacon scanning working. It can be difficult because so many things have to be set up just right.

Some questions for you:

  1. Are you using the deprecated GNSStrategy to enable beacon scanning? If so, try using deviceTypesToDiscover and GNSBeaconStrategy instead. See the API docs at https://developers.google.com/nearby/messages/ios/get-beacon-messages.
  2. Are your beacons registered with the same Google developer project (https://console.developers.google.com/) that your iOS app is using? Use the new Beacon Tools apps for iOS to register them and attach messages (https://developers.google.com/nearby/messages/ios/get-beacon-messages). In your subscription, don't pass in a namespace or message type, and it should receive all messages from all nearby beacons that have been registered with messages attached.

If this doesn't help, then let me know and we'll debug further.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/googlesamples/ios-nearby/issues/11#issuecomment-225648916, or mute the threadhttps://github.com/notifications/unsubscribe/AJemaWy5BVsJXYqWFnGahdZyuVVCvv_uks5qLZGBgaJpZM4IzFfy.

dan-webb commented 8 years ago

If "0 beacon(s)" is showing in the logs, it means that your app is properly configured to use the Nearby service, but isn't seeing any beacons. Does it always say 0 beacons?

You're scanning for Eddystone beacons, correct? Unlike iBeacon scanning, Eddystone scanning is pretty straightforward, and doesn't require anything in Info.plist or any special permissions. The only thing I can think of is that Bluetooth is turned off on your device. What type of iOS device are you testing on? Nearby requires the iPhone 4S and up, and the iPad 3rd gen. and up.

I don't think a Webex/Zoom meeting will help us debug the problem. If you can send more of the logs, that may help. I've tried to reproduce the problem here, and the only thing that prevents Eddystone scanning from happening is BT being turned off. I'll continue investigating and let you know if I find anything else.

rizzeeb commented 8 years ago

Thanks Dan..

Subset of the logs is included below: 2016-06-15 17:32:50.453 NearbyMessagesExample[305:29793] Server URL: https://www.googleapis.com, path: copresence/v2/copresence 2016-06-15 17:32:50.467 NearbyMessagesExample[305:29793] Device ID: u:XXXXXXX 2016-06-15 17:32:52.172 NearbyMessagesExample[305:29793] Subscribe (mediums: 0, broadcast/scan: 0, beacons: 1/0/1, background: 0) 2016-06-15 17:32:52.173 NearbyMessagesExample[305:29793] Beacon: Start scanning 2016-06-15 17:32:52.205 NearbyMessagesExample[305:29793] Publish (mediums: 3, broadcast/scan: 3, beacons: 0/0/0, background: 0) 2016-06-15 17:32:52.232 NearbyMessagesExample[305:29793] Subscribe (mediums: 3, broadcast/scan: 3, beacons: 0/0/0, background: 0) 2016-06-15 17:32:52.235 NearbyMessagesExample[305:29793] Tokens: 0 good, 0 bad, 0 broadcast 2016-06-15 17:32:52.236 NearbyMessagesExample[305:29793] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2016-06-15 17:32:52.253 NearbyMessagesExample[305:29793] Report RPC request: Publish: 1 2016-06-15 17:32:52.254 NearbyMessagesExample[305:29793] Report RPC request: Subscribe: 2 2016-06-15 17:32:53.082 NearbyMessagesExample[305:29793] Report RPC response: Success 2016-06-15 17:32:53.083 NearbyMessagesExample[305:29793] Report RPC response: 12 directive(s), 0 token(s), 0 message(s), 1 publication results(s), 2 subscription results(s) 2016-06-15 17:32:53.084 NearbyMessagesExample[305:29793] Audio: Token changed to: XXXXXX 2016-06-15 17:32:53.086 NearbyMessagesExample[305:29793] BLE: Ad packet token changed to: XXXXXX 2016-06-15 17:32:53.086 NearbyMessagesExample[305:29793] BLE: GATT token changed to: XXXXXX 2016-06-15 17:32:53.291 NearbyMessagesExample[305:29793] Tokens: 0 good, 0 bad, 3 broadcast 2016-06-15 17:32:53.291 NearbyMessagesExample[305:29793] Report RPC request: 3 token(s), 0 beacon(s), 6 directive(s) 2016-06-15 17:32:53.497 NearbyMessagesExample[305:29793] Report RPC response: Success 2016-06-15 17:32:53.498 NearbyMessagesExample[305:29793] Report RPC response: 0 directive(s), 3 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s) 2016-06-15 17:32:53.511 NearbyMessagesExample[305:29793] Tokens: 0 good, 0 bad, 3 broadcast 2016-06-15 17:32:53.511 NearbyMessagesExample[305:29793] Report RPC request: 3 token(s), 0 beacon(s), 6 directive(s) 2016-06-15 17:32:53.723 NearbyMessagesExample[305:29793] Report RPC response: Success 2016-06-15 17:32:53.723 NearbyMessagesExample[305:29793] Report RPC response: 0 directive(s), 3 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s) 2016-06-15 17:32:55.678 NearbyMessagesExample[305:29793] Audio: No broadcaster detected 2016-06-15 17:32:55.935 NearbyMessagesExample[305:29850] Audio player: Sole output is Speaker 2016-06-15 17:32:55.980 NearbyMessagesExample[305:29793] Tokens: 0 good, 0 bad, 3 broadcast 2016-06-15 17:32:55.980 NearbyMessagesExample[305:29793] Report RPC request: 3 token(s), 0 beacon(s), 6 directive(s) 2016-06-15 17:32:55.991 NearbyMessagesExample[305:29850] Audio: Broadcasting started 2016-06-15 17:32:55.992 NearbyMessagesExample[305:29841] Audio player: Setting volume to 0.271335 2016-06-15 17:32:56.133 NearbyMessagesExample[305:29793] Report RPC response: Success 2016-06-15 17:32:56.134 NearbyMessagesExample[305:29793] Report RPC response: 0 directive(s), 3 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s)

From: Dan Webb notifications@github.com<mailto:notifications@github.com> Reply-To: googlesamples/ios-nearby reply@reply.github.com<mailto:reply@reply.github.com> Date: Wednesday, June 15, 2016 at 2:33 PM To: googlesamples/ios-nearby ios-nearby@noreply.github.com<mailto:ios-nearby@noreply.github.com> Cc: Rizwan Patel ripatel@caesars.com<mailto:ripatel@caesars.com>, Author author@noreply.github.com<mailto:author@noreply.github.com> Subject: Re: [googlesamples/ios-nearby] Cannot see Eddystone beacons (#11)

If "0 beacon(s)" is showing in the logs, it means that your app is properly configured to use the Nearby service, but isn't seeing any beacons. Does it always say 0 beacons?

You're scanning for Eddystone beacons, correct? Unlike iBeacon scanning, Eddystone scanning is pretty straightforward, and doesn't require anything in Info.plist or any special permissions. The only thing I can think of is that Bluetooth is turned off on your device. What type of iOS device are you testing on? Nearby requires the iPhone 4S and up, and the iPad 3rd gen. and up.

I don't think a Webex/Zoom meeting will help us debug the problem. If you can send more of the logs, that may help. I've tried to reproduce the problem here, and the only thing that prevents Eddystone scanning from happening is BT being turned off. I'll continue investigating and let you know if I find anything else.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/googlesamples/ios-nearby/issues/11#issuecomment-226326814, or mute the threadhttps://github.com/notifications/unsubscribe/AJemafmCIrxecAY0HBLelIXfnMto1lwoks5qMG-XgaJpZM4IzFfy.

dan-webb commented 8 years ago

Thanks for the logs. You mentioned that you're using Eddystone URL and Eddystone UID beacons. Which one are you trying to scan for using Nearby Messages? Only Eddystone UID (and EID) beacons are supported by Nearby Messages at this time.

Google recently released Beacon Tools for registering and managing beacons. Can you download the iOS app (https://itunes.apple.com/us/app/beacon-tools/id1094371356?mt=8) and see if it is able to find your Eddystone beacon? The app scans for nearby beacons, and lets you register them with your developer project and attach messages to the Eddystone UID beacons.

rizzeeb commented 8 years ago

Thanks.. Dan, yup, I’ve already done that.. So have already downloaded the Beacons tools app and registered the Eddystone UID through that tool (by clicking on beacons near me and then selecting the UID and then observing that it moved to the Registered State from the UnRegistered state) and then I went to the Beacon Dashboard and added the Nearby Notification URL there, for the registered UID.. (and added the location via the Place, and set the Stability to be Stable). Again, let me know if you a quick 10 mins webex/zoom session works for you sometime next week, and I’ll set that up.. Thanks…

From: Dan Webb notifications@github.com<mailto:notifications@github.com> Reply-To: googlesamples/ios-nearby reply@reply.github.com<mailto:reply@reply.github.com> Date: Friday, June 17, 2016 at 9:50 AM To: googlesamples/ios-nearby ios-nearby@noreply.github.com<mailto:ios-nearby@noreply.github.com> Cc: Rizwan Patel ripatel@caesars.com<mailto:ripatel@caesars.com>, Author author@noreply.github.com<mailto:author@noreply.github.com> Subject: Re: [googlesamples/ios-nearby] Cannot see Eddystone beacons (#11)

Thanks for the logs. You mentioned that you're using Eddystone URL and Eddystone UID beacons. Which one are you trying to scan for using Nearby Messages? Only Eddystone UID (and EID) beacons are supported by Nearby Messages at this time.

Google recently released Beacon Tools for registering and managing beacons. Can you download the iOS app (https://itunes.apple.com/us/app/beacon-tools/id1094371356?mt=8) and see if it is able to find your Eddystone beacon? The app scans for nearby beacons, and lets you register them with your developer project and attach messages to the Eddystone UID beacons.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/googlesamples/ios-nearby/issues/11#issuecomment-226821731, or mute the threadhttps://github.com/notifications/unsubscribe/AJemaahG8dmulE89Mr6vFCCJANwIJ88Xks5qMtBrgaJpZM4IzFfy.

dan-webb commented 8 years ago

Well, this is truly baffling. I'm sorry for the troubles, and I'm determined to help you get to the bottom of it.

Here's a super simple beacon scanner app that uses Nearby Messages: https://github.com/dwebb23/Beacon-Scanning Can you download it, insert your API key (in AppDelegate.m) and bundle ID (in the build settings), and see if it successfully finds your beacon? It may take 10-20 seconds to find any beacons. Please send me the logs.

rizzeeb commented 8 years ago

Thanks.. Still the same result…(I can see the beacon under the Registered Tab of the Beacon Tools, but not within the code below) Logs below..

2016-06-20 13:37:26.254 EddystoneBeaconScanning[628:195171] Server URL: https://www.googleapis.com, path: copresence/v2/copresence 2016-06-20 13:37:26.280 EddystoneBeaconScanning[628:195171] Device ID: u:XXXXXXXx 2016-06-20 13:37:26.282 EddystoneBeaconScanning[628:195171] Subscribe (mediums: 0, broadcast/scan: 0, beacons: 1/0/1, background: 0) 2016-06-20 13:37:26.283 EddystoneBeaconScanning[628:195171] Beacon: Start scanning 2016-06-20 13:37:26.390 EddystoneBeaconScanning[628:195171] Tokens: 0 good, 0 bad, 0 broadcast 2016-06-20 13:37:26.391 EddystoneBeaconScanning[628:195171] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2016-06-20 13:37:26.406 EddystoneBeaconScanning[628:195171] Report RPC request: Subscribe: 1 2016-06-20 13:37:27.248 EddystoneBeaconScanning[628:195171] Report RPC response: Success 2016-06-20 13:37:27.249 EddystoneBeaconScanning[628:195171] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 1 subscription results(s) 2016-06-20 13:37:31.741 EddystoneBeaconScanning[628:195171] Tokens: 0 good, 0 bad, 0 broadcast 2016-06-20 13:37:31.742 EddystoneBeaconScanning[628:195171] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2016-06-20 13:37:31.974 EddystoneBeaconScanning[628:195171] Report RPC response: Success 2016-06-20 13:37:31.974 EddystoneBeaconScanning[628:195171] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s) 2016-06-20 13:37:37.232 EddystoneBeaconScanning[628:195171] Tokens: 0 good, 0 bad, 0 broadcast 2016-06-20 13:37:37.233 EddystoneBeaconScanning[628:195171] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2016-06-20 13:37:37.516 EddystoneBeaconScanning[628:195171] Report RPC response: Success 2016-06-20 13:37:37.516 EddystoneBeaconScanning[628:195171] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s) 2016-06-20 13:37:42.732 EddystoneBeaconScanning[628:195171] Tokens: 0 good, 0 bad, 0 broadcast 2016-06-20 13:37:42.732 EddystoneBeaconScanning[628:195171] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2016-06-20 13:37:43.045 EddystoneBeaconScanning[628:195171] Report RPC response: Success 2016-06-20 13:37:43.046 EddystoneBeaconScanning[628:195171] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s) 2016-06-20 13:37:48.155 EddystoneBeaconScanning[628:195171] Tokens: 0 good, 0 bad, 0 broadcast 2016-06-20 13:37:48.155 EddystoneBeaconScanning[628:195171] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2016-06-20 13:37:48.454 EddystoneBeaconScanning[628:195171] Report RPC response: Success 2016-06-20 13:37:48.455 EddystoneBeaconScanning[628:195171] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s) 2016-06-20 13:37:53.451 EddystoneBeaconScanning[628:195171] Tokens: 0 good, 0 bad, 0 broadcast 2016-06-20 13:37:53.451 EddystoneBeaconScanning[628:195171] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2016-06-20 13:37:53.765 EddystoneBeaconScanning[628:195171] Report RPC response: Success 2016-06-20 13:37:53.765 EddystoneBeaconScanning[628:195171] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s) 2016-06-20 13:37:58.938 EddystoneBeaconScanning[628:195171] Tokens: 0 good, 0 bad, 0 broadcast 2016-06-20 13:37:58.938 EddystoneBeaconScanning[628:195171] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2016-06-20 13:37:59.484 EddystoneBeaconScanning[628:195171] Report RPC response: Success 2016-06-20 13:37:59.484 EddystoneBeaconScanning[628:195171] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s) 2016-06-20 13:38:04.315 EddystoneBeaconScanning[628:195171] Tokens: 0 good, 0 bad, 0 broadcast 2016-06-20 13:38:04.315 EddystoneBeaconScanning[628:195171] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2016-06-20 13:38:04.678 EddystoneBeaconScanning[628:195171] Report RPC response: Success 2016-06-20 13:38:04.679 EddystoneBeaconScanning[628:195171] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s) 2016-06-20 13:38:09.738 EddystoneBeaconScanning[628:195171] Tokens: 0 good, 0 bad, 0 broadcast 2016-06-20 13:38:09.739 EddystoneBeaconScanning[628:195171] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2016-06-20 13:38:10.056 EddystoneBeaconScanning[628:195171] Report RPC response: Success 2016-06-20 13:38:10.057 EddystoneBeaconScanning[628:195171] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s) 2016-06-20 13:38:15.036 EddystoneBeaconScanning[628:195171] Tokens: 0 good, 0 bad, 0 broadcast 2016-06-20 13:38:15.037 EddystoneBeaconScanning[628:195171] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2016-06-20 13:38:15.287 EddystoneBeaconScanning[628:195171] Report RPC response: Success 2016-06-20 13:38:15.288 EddystoneBeaconScanning[628:195171] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s) 2016-06-20 13:38:20.523 EddystoneBeaconScanning[628:195171] Tokens: 0 good, 0 bad, 0 broadcast 2016-06-20 13:38:20.523 EddystoneBeaconScanning[628:195171] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2016-06-20 13:38:20.796 EddystoneBeaconScanning[628:195171] Report RPC response: Success 2016-06-20 13:38:20.796 EddystoneBeaconScanning[628:195171] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s) 2016-06-20 13:38:26.009 EddystoneBeaconScanning[628:195171] Tokens: 0 good, 0 bad, 0 broadcast 2016-06-20 13:38:26.009 EddystoneBeaconScanning[628:195171] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2016-06-20 13:38:26.279 EddystoneBeaconScanning[628:195171] Report RPC response: Success 2016-06-20 13:38:26.279 EddystoneBeaconScanning[628:195171] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s) 2016-06-20 13:38:31.398 EddystoneBeaconScanning[628:195171] Tokens: 0 good, 0 bad, 0 broadcast 2016-06-20 13:38:31.399 EddystoneBeaconScanning[628:195171] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2016-06-20 13:38:31.712 EddystoneBeaconScanning[628:195171] Report RPC response: Success 2016-06-20 13:38:31.712 EddystoneBeaconScanning[628:195171] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s) 2016-06-20 13:38:36.756 EddystoneBeaconScanning[628:195171] Tokens: 0 good, 0 bad, 0 broadcast 2016-06-20 13:38:36.757 EddystoneBeaconScanning[628:195171] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2016-06-20 13:38:37.075 EddystoneBeaconScanning[628:195171] Report RPC response: Success 2016-06-20 13:38:37.076 EddystoneBeaconScanning[628:195171] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s) 2016-06-20 13:38:42.240 EddystoneBeaconScanning[628:195171] Tokens: 0 good, 0 bad, 0 broadcast 2016-06-20 13:38:42.240 EddystoneBeaconScanning[628:195171] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2016-06-20 13:38:42.557 EddystoneBeaconScanning[628:195171] Report RPC response: Success 2016-06-20 13:38:42.557 EddystoneBeaconScanning[628:195171] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 subscription results(s)

From: Dan Webb notifications@github.com<mailto:notifications@github.com> Reply-To: googlesamples/ios-nearby reply@reply.github.com<mailto:reply@reply.github.com> Date: Friday, June 17, 2016 at 2:29 PM To: googlesamples/ios-nearby ios-nearby@noreply.github.com<mailto:ios-nearby@noreply.github.com> Cc: Rizwan Patel ripatel@caesars.com<mailto:ripatel@caesars.com>, Author author@noreply.github.com<mailto:author@noreply.github.com> Subject: Re: [googlesamples/ios-nearby] Cannot see Eddystone beacons (#11)

Well, this is truly baffling. I'm sorry for the troubles, and I'm determined to help you get to the bottom of it.

Here's a super simple beacon scanner app that uses Nearby Messages: https://github.com/dwebb23/Beacon-Scanning Can you download it, insert your API key (in AppDelegate.m) and bundle ID (in the build settings), and see if it successfully finds your beacon? It may take 10-20 seconds to find any beacons. Please send me the logs.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/googlesamples/ios-nearby/issues/11#issuecomment-226886151, or mute the threadhttps://github.com/notifications/unsubscribe/AJemadasWM_oEXnhnp8qZxRbmZlo-AGuks5qMxHHgaJpZM4IzFfy.

dan-webb commented 8 years ago

Thank you for the additional logs. I've consulted the local beacon expert, and he is also stumped. The Beacon Tools app is using the same beacon scanner library that Nearby Messages uses, so they should be able to find the beacon.

However, the version of Nearby Messages you're using is from March, and perhaps it contains a bug that has been fixed since then. This is my best guess at what's causing the problem. I'm planning on releasing a new version fairly soon, although I can't promise a specific date. I'll let you know when it's released.

Again, apologies for the troubles, and I hope the new version will resolve the problem.

rizzeeb commented 8 years ago

Thanks.. The only other thing that is different is that for the beacon tools app, I do no specific the API key, but rather the project itself which is the same project that has the beacons associated with it (it does have the API key associated with it too, which is the key that I used in the code below)… Another thing to mention, that I’d indicated in the thread, was that in the Search menu item, I was able to see the beacons – using this sample code - https://github.com/google/beacon-platform/tree/master/samples/ios…

If you want, I can send the appropriate screen shots – if you send me a non-distribution address…

Thanks, Rizwan

From: Dan Webb notifications@github.com<mailto:notifications@github.com> Reply-To: googlesamples/ios-nearby reply@reply.github.com<mailto:reply@reply.github.com> Date: Tuesday, June 21, 2016 at 1:24 PM To: googlesamples/ios-nearby ios-nearby@noreply.github.com<mailto:ios-nearby@noreply.github.com> Cc: Rizwan Patel ripatel@caesars.com<mailto:ripatel@caesars.com>, Author author@noreply.github.com<mailto:author@noreply.github.com> Subject: Re: [googlesamples/ios-nearby] Cannot see Eddystone beacons (#11)

Thank you for the additional logs. I've consulted the local beacon expert, and he is also stumped. The Beacon Tools app is using the same beacon scanner library that Nearby Messages uses, so they should be able to find the beacon.

However, the version of Nearby Messages you're using is from March, and perhaps it contains a bug that has been fixed since then. This is my best guess at what's causing the problem. I'm planning on releasing a new version fairly soon, although I can't promise a specific date. I'll let you know when it's released.

Again, apologies for the troubles, and I hope the new version will resolve the problem.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/googlesamples/ios-nearby/issues/11#issuecomment-227560404, or mute the threadhttps://github.com/notifications/unsubscribe/AJemaeTKzgQAjsy4E4VCdZzy6cZqTeftks5qOEh4gaJpZM4IzFfy.

dan-webb commented 8 years ago

Thanks for reminding me that it works using the Beacon Platform sample app. That app uses CoreBluetooth directly, and I think this is more evidence that there's a bug in the March version of Nearby Messages. No need for a screenshot, thanks!

dan-webb commented 8 years ago

We just shipped Nearby Messages v1.0.1. Please give it a try and let me know if it solves the problem you're seeing. If not, I'll help you continue to investigate further.

rizzeeb commented 8 years ago

Thanks Dan.. Yup, that worked.. I can now see the beacons and the attachment and when I include the params for include IBeacon, it asks for which IBeacon to scan!! I’ll keep looking for the Nearby Notifications to be released later this year, since that’s going to add a whole new dimension!! "Note: Nearby Notifications will be launching soon along with an updated Beacons Dashboard and Beacon Tools app. Check back later in the summer of 2016 for updates.”

From: Dan Webb notifications@github.com<mailto:notifications@github.com> Reply-To: googlesamples/ios-nearby reply@reply.github.com<mailto:reply@reply.github.com> Date: Thursday, June 23, 2016 at 1:20 PM To: googlesamples/ios-nearby ios-nearby@noreply.github.com<mailto:ios-nearby@noreply.github.com> Cc: Rizwan Patel ripatel@caesars.com<mailto:ripatel@caesars.com>, Author author@noreply.github.com<mailto:author@noreply.github.com> Subject: Re: [googlesamples/ios-nearby] Cannot see Eddystone beacons (#11)

We just shipped Nearby Messages v1.0.1https://cocoapods.org/pods/NearbyMessages. Please give it a try and let me know if it solves the problem you're seeing. If not, I'll help you continue to investigate further.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHubhttps://github.com/googlesamples/ios-nearby/issues/11#issuecomment-228171463, or mute the threadhttps://github.com/notifications/unsubscribe/AJemaXln65t7ieAFbZaLFNZfgfaBI4QCks5qOuqlgaJpZM4IzFfy.

dan-webb commented 8 years ago

That's great! I'm happy it's finally working for you. And again, sorry for the trouble, and if there's anything else you need help with, please let me know.

NikitaGhanwat commented 6 years ago

Hi @dan-webb 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. error

lalittech commented 6 years ago

We are stumbling with Eddystone EID. Please anyone help me out, about Beacon tools app is not detecting my Eddystone EID beacon. Thanks in advance..