Closed kamilwlf closed 8 years ago
Hello @kamilwlf
Well, this doesn't affect anything. This log is posted when our SDK is trying to resolve your owned nearables in your area. But it can not do that because you haven't initialized your sdk with proper app id
and app token
.
Anyway thanks for reporting that - we will remove this log in next release, so it won't bother you anymore :)
I was originally using Android SDK version 0.10.4 because that's what the setup tutorial uses (http://developer.estimote.com/android/tutorial/part-1-setting-up/). All I am using is nearable discovery, thus I add a nearable listener and start discovery. This works just fine with 0.10.4.
I saw today that there is a version 0.11.0, thus I decided to try it. I started getting the exact same exception as in the op. I assume this exception is because the SDK is trying to look up the nearable type in the cloud but I didn't initialize the SDK (because I don't want the cloud). Fine, just set the type to UNKOWN
. Having said that, there does seem to be an effect: the SDK no longer discovers any nearables. Weirdly, it still calls the nearable listener, but with an empty list.
Sometimes I see this in logs. Should I care?
U use 'com.estimote:sdk:0.11.0@aar'