googlesamples / ios-nearby

69 stars 30 forks source link

NearbyBeacon App can see beacon in debug, but message handlers do not trigger #38

Open jasorod opened 5 years ago

jasorod commented 5 years ago

Hello,

I'm having an issue with the iOS version of the Nearby messaging library, version 1.1.1. My beacons are a Radius Beacon Dot. I'm currently running both iOS 11.4.1 and iOS 12, one with an iPad Mini, the other on an iPhone 8 Plus. I've registered the beacons with Google, and am successfully getting Nearby messages on my Samsung Galaxy S7 running Android 7. On iOS though, while the debug logs show that both my beacons are being detected, none of the message handlers for finding a device are being triggered. When I take the beacons out of range, the message lost handler isn't being called either.

Here is a sample copy of my debug console output:

2018-11-06 09:34:07.921995-0500 NearbyBeacons[1351:307690] Server URL: https://www.googleapis.com, path: copresence/v2/copresence 2018-11-06 09:34:07.926252-0500 NearbyBeacons[1351:307690] Device ID: (null) 2018-11-06 09:34:07.926276-0500 NearbyBeacons[1351:307690] RegisterDevice RPC request 2018-11-06 09:34:08.423668-0500 NearbyBeacons[1351:307690] RegisterDevice RPC: Success: 2018-11-06 09:34:21.150320-0500 NearbyBeacons[1351:307690] Subscribe (mediums: 0, broadcast/scan: 0, beacons: 1/1/1, background: 1) 2018-11-06 09:34:21.152312-0500 NearbyBeacons[1351:307690] Beacon: Start scanning 2018-11-06 09:34:21.183711-0500 NearbyBeacons[1351:307690] Tokens: 0 good, 0 bad, 0 broadcast 2018-11-06 09:34:21.183782-0500 NearbyBeacons[1351:307690] Report RPC request: 0 token(s), 0 beacon(s), 0 directive(s) 2018-11-06 09:34:21.187622-0500 NearbyBeacons[1351:307690] Report RPC request: Subscribe: 1 2018-11-06 09:34:21.409176-0500 NearbyBeacons[1351:307690] Report RPC response: Success 2018-11-06 09:34:21.409565-0500 NearbyBeacons[1351:307690] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 unpublish results(s), 1 subscription results(s), 0 unsubscribe results(s) 2018-11-06 09:34:21.409905-0500 NearbyBeacons[1351:307690] Beacon: iBeacon UUIDs to scan for: {( )} 2018-11-06 09:34:21.439398-0500 NearbyBeacons[1351:307690] Tokens: 0 good, 0 bad, 0 broadcast 2018-11-06 09:34:21.439528-0500 NearbyBeacons[1351:307690] Report RPC request: 0 token(s), 1 beacon(s), 0 directive(s) 2018-11-06 09:34:21.585952-0500 NearbyBeacons[1351:307690] Report RPC response: Success 2018-11-06 09:34:21.586214-0500 NearbyBeacons[1351:307690] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 unpublish results(s), 0 subscription results(s), 0 unsubscribe results(s) 2018-11-06 09:34:21.779689-0500 NearbyBeacons[1351:307690] Tokens: 0 good, 0 bad, 0 broadcast 2018-11-06 09:34:21.779837-0500 NearbyBeacons[1351:307690] Report RPC request: 0 token(s), 2 beacon(s), 0 directive(s) 2018-11-06 09:34:21.996994-0500 NearbyBeacons[1351:307690] Report RPC response: Success 2018-11-06 09:34:21.997283-0500 NearbyBeacons[1351:307690] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 unpublish results(s), 0 subscription results(s), 0 unsubscribe results(s) 2018-11-06 09:34:23.981802-0500 NearbyBeacons[1351:307690] Tokens: 0 good, 0 bad, 0 broadcast 2018-11-06 09:34:23.981983-0500 NearbyBeacons[1351:307690] Report RPC request: 0 token(s), 2 beacon(s), 0 directive(s) 2018-11-06 09:34:24.121757-0500 NearbyBeacons[1351:307690] Report RPC response: Success 2018-11-06 09:34:24.122043-0500 NearbyBeacons[1351:307690] Report RPC response: 0 directive(s), 0 token(s), 0 message(s), 0 publication results(s), 0 unpublish results(s), 0 subscription results(s), 0 unsubscribe results(s)

farazhaider88 commented 4 years ago

same issue i'm facing any solution for this ?