-
Notifications
You must be signed in to change notification settings - Fork 38
Does not receving any feedback with actions #35
Comments
I'm not sure I understand, what exactly does it say and where? |
In issue #11 . For this reason, I was starting just after click in the button. |
So your problem is the same as #11? Or now that you moved it into a button-click, do you have a different issue? |
It is not the same problem. In #11 the error is been presented to the developer, but I am can not view any error log, but the system is not find any beacon too. So, I want to know if there is any possibility to get a more verbose log to understand what is happening. |
Gotcha, I understand now ^_^ I checked your Cloud account and I can see that you have one beacon tagged as "mil", and no beacons tagged as "copa". The one beacon tagged as "mil" is a pretty old Estimote Beacon, which doesn't support our new Estimote Monitoring technology, and thus won't work with our Proximity SDKs. Your "lemon", "beetroot", and "candy" beacons are a newer model, and these support Estimote Monitoring. You have to enable it, e.g., by connecting to these beacons via the Estimote iOS or Android app. Then, you can tag them, and your proximity zones should start working. I'm going to close this issue, since it doesn't describe a problem with the react-native-proximity plugin. If you have more questions or problems getting Proximity up and running, worry not, I'll be happy to help you further on our forums: https://forums.estimote.com (: |
I was tryng to execute the below code, but it is not working. I was using a Sunsung S7 with Android.
I put the start scan in button, because there is a issue that say it should be launched after app is ready.
How can I check if it is working?
The text was updated successfully, but these errors were encountered: