Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Crash with large number of beacons #33

Open
beaur opened this issue Mar 11, 2015 · 1 comment
Open

Crash with large number of beacons #33

beaur opened this issue Mar 11, 2015 · 1 comment

Comments

@beaur
Copy link

beaur commented Mar 11, 2015

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.

@beaur
Copy link
Author

beaur commented Mar 11, 2015

This could also be because some beacons have the same major and minor IDs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant