You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Put an X between the brackets on this line if you have done all of the following:
My beacons have Estimote Monitoring enabled (Check it in the Estimote Cloud, or via app)
My Android device/devices supports BLE and has Android OS version >= 5.0.0
My Android device/devices have bluetooth enabled
My app has Location Permissions granted
Basic information
Estimote SDK version: [0.6.2]
Android devices affected: [none]
Android OS version affected: [none
Description
[Description of the issue] @pawelDylag
Actually i was Using 0.6.2 version of Proximity SDK but when i used the latest Proximity SDK version and updated it in my gradle file. The Previous code gave a lot of errors for the classes which were present in previous version of Proximity SDK. I reffered to the Change Log and could find any info about the changes in thos classes nor i was able to find out any example regarding the latest Proximity SDK.
As the one used here is using version 0.6.1 . Please refer any example or mention what can i do?
Regards
Aman Rawat
The text was updated successfully, but these errors were encountered:
Prerequisites
Basic information
Estimote SDK version: [0.6.2]
Android devices affected: [none]
Android OS version affected: [none
Description
[Description of the issue]
@pawelDylag
Actually i was Using 0.6.2 version of Proximity SDK but when i used the latest Proximity SDK version and updated it in my gradle file. The Previous code gave a lot of errors for the classes which were present in previous version of Proximity SDK. I reffered to the Change Log and could find any info about the changes in thos classes nor i was able to find out any example regarding the latest Proximity SDK.
As the one used here is using version 0.6.1 . Please refer any example or mention what can i do?
Regards
Aman Rawat
The text was updated successfully, but these errors were encountered: