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
It seems that the SDK forces the EPXProximityZone callback i.e @property(nonatomic, copy, readwrite, nullable) void (^onEnter)(EPXProximityZoneContext *zoneContext); and the others to be called back on the main thread.
In cases where there are a lot of beacons near by this causes heavy usage on the app and in some cases, it's getting totally stuck ...
From stack tracing it seems like Estimote SDK does most of the work on it's own thread com.estimote.EBSUniversalScanner.defaultQueue but then dispatch it back on to the main thread...
I wish one of the two will happen:
The callback would come back on the thread it was registered to
I could inject/supply a queue which I'd like my EPXProximityZones to be observed on
Maybe there is such a case and I'm missing something?
And also why is EPXProximityZone introduce the usage of UIKit is there a reason?
The text was updated successfully, but these errors were encountered:
It seems that the SDK forces the
EPXProximityZone
callback i.e@property(nonatomic, copy, readwrite, nullable) void (^onEnter)(EPXProximityZoneContext *zoneContext);
and the others to be called back on the main thread.In cases where there are a lot of beacons near by this causes heavy usage on the app and in some cases, it's getting totally stuck ...
From stack tracing it seems like Estimote SDK does most of the work on it's own thread
com.estimote.EBSUniversalScanner.defaultQueue
but then dispatch it back on to the main thread...I wish one of the two will happen:
EPXProximityZone
s to be observed onMaybe there is such a case and I'm missing something?
And also why is
EPXProximityZone
introduce the usage of UIKit is there a reason?The text was updated successfully, but these errors were encountered: