search

NordicSemiconductor / Android-nRF-Beacon-for-Eddystone

An application with Eddystone GATT Configuration Service & Google Nearby API and Proximity API.
BSD 3-Clause "New" or "Revised" License
48 stars 18 forks source link

Error 403 #2

Closed laurijamsa closed 8 years ago

laurijamsa commented 8 years ago

When I try to register an UID beacon, I get

Error 403 Error message: Unknown error Error status: Unable to register beacon

I'm running https://github.com/NordicSemiconductor/nrf5-sdk-for-eddystone/blob/master/hex/nrf5_sdk_for_eddystone_v0.6.hex and using the latest app version on Galaxy S7 Edge.

Another thing: AFAIK after the slot has been enabled, it cannot be disabled. Only replaced. So maybe you could add one more frame type called "EMPTY"? Or just a trash bin icon. User might also need some help documentation that can be read directly from the app. At the moment it's pretty hard to use if the user is not really familiar with the Eddystone specs. Or at least a link pointing to documentation.

roshanrajaratnam commented 8 years ago

@laurijamsa I am looking at the 403 issue as it is something to do with granting permissions to the proximity api. Were you prompted asking to grant authorization to the proximity API? I bet it must have on the older version. I will debug this and get back to you.

Regarding the second issue, you can clear the existing or a newly created slot by pressing the trash bin icon on the toolbar. This will clear the slot and the UI will show up as an Empty slot. I will look in to some help documentation as well.

laurijamsa commented 8 years ago

Yeah the app asked my permission and I granted it.

Hah, I didn't notice that trash bin icon 👍 It's working great.

roshanrajaratnam commented 8 years ago

Ok so did it not ask you permission before for the beacon platform? did you do anything different than last time?

laurijamsa commented 8 years ago

This was a first time I tried to register a beacon. If I recall correctly, the app asked something about the permissions after updating it yesterday.

roshanrajaratnam commented 8 years ago

Ok, so I suppose we could close the issue. Usually this happens only if you haven't granted authorization to the proximity API and the app will ensure if the permission is granted.