google / beacon-platform

Code samples for Google's beacon platform

Beacon Platform

This repository contains sample apps that demonstrate how to use the Proximity Beacon API.

• Android app
• iOS app
• Python

You can learn more about the beacon platform, the Proximity Beacon API, and Eddystone, an open beacon format from Google.

beacon-platform's Issues

Unsuccessful createAttachment request(Android)

code : 400
message : invalid value at 'attachment.data' (TYPE_BYTES), Base64 decoding failed for "some text"

this happened when i tried to add nearby notification using attachment format from https://developers.google.com/nearby/notifications/attachment_data_format for free form app intent. The namespace and type is okay(com.google.nearby/en) but the data is causing problem. But the URL attachment was successfully added.

Installation failed with message INSTALL_FAILED_OLDER_SDK.

I am using Android Studio version 1.3.2 and getting error "Installation failed with message INSTALL_FAILED_OLDER_SDK." on Run -> Run App after importing as existing project, and if m not wrong importing BeaconServiceDemoApp folder as an existing project is by clicking the option Import project as (Gradle, Eclipse ADT etc)

outdated project files

buildToolVersion, Gradle Wrapper version, dependencies version , android-gradle-plugin version are all outdated.

Data Attachment

When I attach data in json format

{
"title":"Some Title here",
"url":"https://example.com"

}

issue is that it only allows 11 character in title... Anybody can help me please???

Support querying for ibeacon via properties

In the python scripts, when registering an ibeacon, automatically add properties like ibeacon_uuid, ibeacon_maj, ibeacon_min to ease querying on these attributes later.

NearBy Message API not working with iBeacon uploaded on beacon platform

I have uploaded one iBeacon(Kontakt) in my Beacon Platform project . I used python sample to upload the same. I used below call for this
pb-cli --service-account-creds creds.json register-beacon --beacon-json '{"advertisedId":{"type":"IBEACON","id":""},"status":"ACTIVE"}' --no-ibeacon-props

Here Encoded Id is generated by encoding iBeacon UDID + Major(Hex) + Minor(Hex)

My iBeacon is uploaded successfully and I can see it in my Beacon Platform dashboard, however I am not able to receive messages in my app which is developed using NearBy samples.

Please note it's working perfectly fine for beacons using eddystone protocol (Kontakt again) which I uploaded using Beacon Tools mobile app. I am using NearBy Message sample for both Foreground and Background mode, and I am getting messages only for eddystone beacon , not for iBeacon.

Are any additional steps needed for iBeacon ?

Security Policy violation Binary Artifacts

This issue was automatically created by Allstar.

Security Policy Violation
Project is out of compliance with Binary Artifacts policy: binaries present in source code

Rule Description
Binary Artifacts are an increased security risk in your repository. Binary artifacts cannot be reviewed, allowing the introduction of possibly obsolete or maliciously subverted executables. For more information see the Security Scorecards Documentation for Binary Artifacts.

Remediation Steps
To remediate, remove the generated executable artifacts from the repository.

Artifacts Found

• samples/android/BeaconServiceDemoApp/gradle/wrapper/gradle-wrapper.jar

Additional Information
This policy is drawn from Security Scorecards, which is a tool that scores a project's adherence to security best practices. You may wish to run a Scorecards scan directly on this repository for more details.

---

Allstar has been installed on all Google managed GitHub orgs. Policies are gradually being rolled out and enforced by the GOSST and OSPO teams. Learn more at http://go/allstar

This issue will auto resolve when the policy is in compliance.

Issue created by Allstar. See https://github.com/ossf/allstar/ for more information. For questions specific to the repository, please contact the owner or maintainer.

GooglePlacePicker Missing in some files

Hi,

On the following files I had to add the import GooglePlacePicker:

BeaconInfoTableViewCell.m
BeaconRegistrationEditorViewController.m
SearchViewController.m

Otherwise, the build failed.

Now at least the build is ok.

My Xcode is 8.2.1 (8C1002)

Can I run this example in older android version as SDK 19 ?

In this example use android 22 libary. I can use this libary for other version android.

Google Proximity API is not anymore on Google Developer Console

I tried to enable the API in the Google developer console, so I can't enable it.

Instructions not clear for setting up iOS key

To setup the API keys, the iOS sample README mentions:

On the left of the Developers Console, click on "APIs & auth", and then on "Credentials". Press "Create new Key" to create a Public API access key.
Choose 'iOS Key'.

But there is no 'iOS Key' option on the panel. The user must first choose "API Key" from the dropdown menu and then a "iOS Key" button will be visible.

Registering Nearby Notifications using Proximity Beacon API

I would like to know if it is possible to register/confogure Nearby Notifications of a particular beacon using the Proximity Beacon API.

ld: library not found for -lPods in iOS

I got this issue. I tried hard to overcome but did not found any related help to solve this.

all beacon scanned are locked

i've change multiple namespaceId and instanceId but when scan with demo app i retrieve everytime locked simbol near eddystone beacon. Any solution?

Serving API broken on iOS

inforForObservedBeaconID:APIKey:completionHandler has a few minor bugs in it on iOS. I've sinced fixed and tested this API out. Look for a pull request to fix this.

Does the Android sample app use Volley?

On the README here: https://github.com/google/beacon-platform/tree/master/samples/android it says that the Andorid Sample app uses Volley, yet I couldn't find proof of this inside the code, instead it seems like it uses OKHttp. If so, please update the README file to avoid confusions.

register beacon return 403, permission_denied error

I built the project on my machine.

I configured my G Dev console:

1. enabled proximity API
2. added cred for OAuth2.0 and Client ID. Based on the SHA1 code of my machine.

At the beginning I had wrote the wrong namespace when I added the OAuth2.0 and API key.
but then I fixed it.

I ran the app.
It discovered my android-phone-beacon with status "unregistered".

how can I fix this? the discovery works, but the registration doesn't.

python: Can't list nearby notifications

When I call a --list-attachments it does not show nearby notifications which are attachments created by calling --create-attachment and setting --namespaced-type to com.google.nearby/en

The added problem is that there is no way to delete these attachments because they don't have a name. I do get the attachment name back when I call --create-attachment so if I save it from that call I can perform the delete, but there seems to be no way to query the attachments if they are nearby notifications.

Problem with sample for Android

Hello everybody,

I downloaded this project and set up an API_KEY for it, a json file was also generated. I placed the key in the manifest and the json file inside the app's project folder. But an error is happening and displaying the following message in the log:

GoogleAuthException: com.google.android.gms.auth.GoogleAuthException: UNREGISTERED_ON_API_CONSOLE

This message appears when I press the "SCAN" button of the application. Could someone give me a hint how to solve this problem?

I would greatly appreciate some help with this.

How to integrate beacon proximity api to Web

Hello, I want to integrate beacon proximity api to web.Example: I want to show a message of particular beacon to web so how can i do this

Nearby Message API not found Beacon or attachments

#Hi,
I have been facing an issue related to Nearby Message API and Google Beacon that I have registered Beacon by Google Beacon Tools App with my Project and add attachments to that Beacon. Used Google Codelab to subscribe Beacon in Android App and Beacon is successfully into my Android app but when I was looking for attachments into onFound method then there is nothing to show means NearBy Message API is not able to found attachments from Beacon. There is no problem in Beacon Device because Google Beacon dashboard and proximity beacon api are able to scan for beacon but Nearby is not showing any attachments.
Before 4-5 days., attachments were showing by Nearby but from last 4-5 days Nearby is not showing any attachments.
Please help me out from this issue, Its urgent.

Thanks

Keep seeing Error Domain=com.google.GIDSignIn Code=-1 "

I followed all the steps for iOS instruction, however, I got these errors. I tried to go through all steps again but no luck. Any leads about this error?

2015-12-07 19:29:13.432 BeaconServiceDemoApp[742:501] <GMR/INFO> App measurement v.1201000 started
2015-12-07 19:29:13.570 BeaconServiceDemoApp[742:138981] Error Domain=com.google.GIDSignIn Code=-4 "The operation couldn’t be completed. (com.google.GIDSignIn error -4.)"
2015-12-07 19:29:28.786 BeaconServiceDemoApp[742:138981] Error Domain=com.google.GIDSignIn Code=-1 "A potentially recoverable error occured. You may try again." UserInfo=0x1777fdc0 {NSLocalizedDescription=A potentially recoverable error occured. You may try again.}
2015-12-07 19:29:38.538 BeaconServiceDemoApp[742:138981] Error Domain=com.google.GIDSignIn Code=-1 "A potentially recoverable error occured. You may try again." UserInfo=0x17781cf0 {NSLocalizedDescription=A potentially recoverable error occured. You may try again.}

Android Studio keeps complaining AndroidManifest.xml error

When I import project file to Android Studio (v2.0) and keep seeing this error.
Any hint?

If scan returns no beacons, iOS app still tries to get details and gets weird.

If no beacons are returned, iOS app should just stop there then.

Proximity API permissions

I'm confused about the permissions for registration and monitoring. I setup an unregistered namespace and instance id in order to try the sample Android app here, and picked my google account to use (register/monitor etc.) it. When the app encounters my custom UID, I see the following "Not Authorized" message;

This kind of blocks me from registering my own beacons in the first place, let alone providing other users a provisioning app to use it for monitoring and registering their beacons via my app(through Oauth). Am I missing something?

jars not found for location and placepicker

Hi,
I am getting these issues:
import com.google.android.gms.common.GooglePlayServicesRepairableException;
import com.google.android.gms.location.places.ui.PlacePicker;
in file ManageBeaconFragment.java .
It is unable to find the jars for above mention import in android studio.
Please,suggest me required jar.

Proximity API returns '503 - Service Unavailable' quite frequently

We (Beaconstac) are seeing an increasing number of Proximity API requests returning '503 - Service Unavailable' errors.

For example: <HttpError 503 when requesting https://proximitybeacon.googleapis.com/v1beta1/beacons/3!5dc33487f02e477d4058ac233f25592d/attachments:batchDelete?projectId=beaconstac-1043&alt=json&namespacedType=com.google.nearby%2F%2A returned "The service is currently unavailable.">.

It seems occur at random intervals where all the requests to the API fail at the same time and then start back up normally after a few seconds or so.

Also, we'd like to know when this API will be available in PRODUCTION, as it appears to still be in beta at the moment.

We created a google issue here where the engineer redirected us to file an issue here.

Support iBeacons

Hi,

The sample works only for Eddystone beacons, but I want to use some iBeacons that can't support Eddystone. Could this sample include support for them please?

Also, I must say what to put in "id" here for an iBeacon is not clear as iBeacons have 3 values, not one (an UUID, a major and a minor values).

Parcelable implementation bug

Hello!
In the Beacon.java class, which implements Parcelable, the writeToParcel method writes these values in the beginning of it

@Override
public void writeToParcel(Parcel dest, int flags) {
    dest.writeString(type);
    dest.writeByteArray(id);
    dest.writeString(status);

while the class constructor from a Parcel source tries to read these values

private Beacon(Parcel source) {
    type = source.readString();
    int len = source.readInt();
    id = new byte[len];
    source.readByteArray(id);
    status = source.readString();

The len variable is read from the source as an int that was never set, and a NullPointer exception is caused when source.readByteArray(id); is invoked.

Update python samples to support batch requests

As per documentation here:

https://developers.google.com/beacons/proximity/how-tos/batch

Libproximity on android is using GoogleAuthUtil.getToken is deprecated

Libproximity is using GoogleAuthUtil.getToken which is deprecated.
I was try add the library to my project but because I now use a version of 'com.google.android.gms: play-services' I saw myself in the task of updating the version of the library so that it coincides with my project ,so it marks me that
import com.google.android.gms.auth.GoogleAuthException;
import com.google.android.gms.auth.GoogleAuthUtil;
import com.google.android.gms.auth.UserRecoverableAuthException;
they are not found in the version 'com.google.android.gms: play-services15.0.1'
investigating a bit I found that now the token is obtained in another way.
https://developers.google.com/identity/sign-in/android/migration-guide.

Click SCAN button but no beacon being discovered

Hi,
I just tried out this demo app, but I just cannot discover any beacons around my phone.

I have registered the API key and OAuth 2.0 client ID successfully and turned on Proximity API on the console. And I can actually access to the beacons using my hand-made app, so it should be something wrong with the way I use this demo.

Any advice would be appreciated.

Cannot find the required Google Proximity Beacon API

The instructions specify three API's that must be included from the Google Developer Console. Two of the API's are available, but the Google Proximity Beacon API is not. The application can still be built, but it disappoints at runtime as follows:

2016-01-07 06:59:54.687 BeaconServiceDemoApp[4211:3217071] {
"6e131d09 1c10a9a0 4f2c34b9 ab1cb791" = {
"error_message" = "Project has not enabled the API. Please use Google Developers Console to activate the 'proximitybeacon' API for your project.";
"error_status" = "PERMISSION_DENIED";
};
}