Closed aqibshxhzd closed 6 years ago
Yes, me too i also had a lot of crashes of this in my Crashlytics dashboard.
If you call this method : beaconManager.setBackgroundScanPeriods(scanTime, waitTime) it will trigger this exception
Hey! I just wanted you to know that we are in the process of moving our SDK for Android to a completely new architecture. We won't be publishing any updates to our old (current master) SDK for a while.
But don't worry - there is an ALPHA version of our FRESH PROXIMITY SDK available now!
It uses a completely new scanning mechanism and will work on new Android versions like a charm (6.0, 7.0, 8.0).
We did a great job with renovating our ecosystem to cut off the old, messy code, full of hacks for Android KitKat an Jellybean. This is why working with BeaconManager
was so frustrating by the way.
Plan for the next couple of weeks:
I encourage you to try it out - there is a ready made app for you to show the possibilities of our completely new SDK -> https://github.com/Estimote/Android-SDK/tree/proximity-sdk Let us know what you think! I will keep you updated about the progress.
Duplicated issue -> https://github.com/Estimote/Android-SDK/issues/263
hi i'm facing this type of Exception in my app,, is this bug or ma doing something wrong>>?? attached screenshots of my logs thanks