google-beacon-platform

问题 I'm using a beacon that can work either with iBeacon or Eddystone, I create a scanner that has a service in the background which scans each 10 secs for beacons, similar to the android-beacon-library, but I was thinking that I could use the NearBy API to get the beacons with out the scan service, Is that possible?, I don't want to use the ProximityAPI to register the beacons because these beacons will be out there with out the need to register them. 回答1: In order to use the Nearby API, your

问题 I am using Nearby messages API for android. I was getting the attachments using API before, till end of January. However, it has abruptly stopped working. I can see the request calls my app making in the google cloud console. However, I am not getting any attachment. Is there anything that has been changed on the API end? 回答1: I work on the Nearby team. We've recently discovered and fixed a problem with the default message filter, which might be what's affecting you (e.g. if you don't provide

问题 Can we detect beacons in app background(Both iOS and Android). I see Eddystone beacon have some problem with background of iOS. How can solve that ? 回答1: iOS does allow background detection of service advertisements like Eddystone, but Eddystone detection times can be slower than iBeacon . The reason iBeacon detections are faster is because Apple has optimized it with hardware filters . Hardware filter slots in the bluetooth chip are activated when you monitor an iBeacon region on iOS. This

问题 The Google's Proximity Beacon API documentation uses Eddystone as an example everywhere: https://developers.google.com/beacons/proximity/register However, documentation mentions two more types of beacons, AltBeacon and iBeacon. If I understand correctly, something like this should be used (adapted from Google's example): { "advertisedId": { "type":"IBEACON", "id":"base 64 of what???"}, "status":"ACTIVE", "latLng": { "latitude": 51.4935657, "longitude": -0.1465538 } } However, what is the

问题 The Google's Proximity Beacon API documentation uses Eddystone as an example everywhere: https://developers.google.com/beacons/proximity/register However, documentation mentions two more types of beacons, AltBeacon and iBeacon. If I understand correctly, something like this should be used (adapted from Google's example): { "advertisedId": { "type":"IBEACON", "id":"base 64 of what???"}, "status":"ACTIVE", "latLng": { "latitude": 51.4935657, "longitude": -0.1465538 } } However, what is the

问题 I have got SENSORO beacon which I have configured using congif tool from Sensoro. Then I have created a project for beacon(Google API). Then I have registered the beacon using Beacon Tool from google, it got registered. But I am unable to see my beacon in Google Beacon Platform. I waited for almost 20 hrs but still not appearing. BTW what is difference between Eddystone and Eddystone URL, because for a single beacon I was getting Eddystone(This got registered) and Eddystone URL(Still

问题 My code snippet below is supposed to return the list of beacons. When having Google API Console generate an API Key I have whitelisted my public IP address and associated with the api key. When the code calls ExecuteAsync() method, I keep receiving an exception with error code 403 (forbidden). What may have I done wrong and how to mitigate the issue? public async void TestApiKey() { var apikey = "739479874ABCDEFGH123456"; //it's not the real key I'm using var beaconServices = new

问题 I have created a service account for my Google Proximity API project and downloaded the key file to use it in my application. But when the very last line of the code snippet below is executed, I receive the following exception: Google.GoogleApiException was unhandled by user code HResult=-2146233088 Message=Google.Apis.Requests.RequestError Unauthorized. [403] Errors [ Message[Unauthorized.] Location[ - ] Reason[forbidden] Domain[global]] And here is the code that is supposed to run on the

问题 I am new to beacons and I'm having some troubles with Google Nearby Message API. I did as it was said on their page (https://developers.google.com/nearby/messages/android/get-beacon-messages) but it doesn't get any attachments from the beacons. It connects to the Google API client, it successfully subscribes but it never gets to "onFound" or "onLost". I am able to successfully register the beacon and sea it in "Beacon Tools" app. 来源： https://stackoverflow.com/questions/55088217/not-able-to

问题 We can make iOS devices act as a iBeacon transmitter and We can locate nearby iBeacons if we know their Proximity UUID. With Google's Proximity Beacon API, It's possible to configure and register real Beacon hardware, and we can locate them with Nearby Messaging API. But is it possible to make iOS devices to broadcast as Eddystone Beacons ? And it needs to be discoverable by apps that scan Eddystone beacons. Thanks in advance. 回答1: Unfortunately, this is not possible. While iOS devices can