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
I'm in an environment where I have a large number (50+) of beacons nearby.
My app often crashes with the error:
The application has crashed with an uncaught exception 'NSRangeException'.
[ERROR] : Reason:
[ERROR] : *** -[__NSArrayM removeObjectAtIndex:]: index 65 beyond bounds [0 .. 64]
I've traced this back to line 426 in OrgBeuckmanTibeaconsModule.m
Seems this piece of code is removing duplicate beacons, but often tries to remove an object at an index that is no longer there. Looks like there is something screwy in the way this function is built.
Generally everything works ok with only 4 or 5 beacons in range.
The text was updated successfully, but these errors were encountered:
I'm in an environment where I have a large number (50+) of beacons nearby.
My app often crashes with the error:
The application has crashed with an uncaught exception 'NSRangeException'.
[ERROR] : Reason:
[ERROR] : *** -[__NSArrayM removeObjectAtIndex:]: index 65 beyond bounds [0 .. 64]
I've traced this back to line 426 in OrgBeuckmanTibeaconsModule.m
Seems this piece of code is removing duplicate beacons, but often tries to remove an object at an index that is no longer there. Looks like there is something screwy in the way this function is built.
Generally everything works ok with only 4 or 5 beacons in range.
The text was updated successfully, but these errors were encountered: