Skip to content
This repository has been archived by the owner on Sep 22, 2019. It is now read-only.

Don't start/stop scanning in timer #4

Open
malhal opened this issue Apr 3, 2014 · 2 comments
Open

Don't start/stop scanning in timer #4

malhal opened this issue Apr 3, 2014 · 2 comments

Comments

@malhal
Copy link

malhal commented Apr 3, 2014

Since you stop and start scanning in your timer it doesn't find all beacons because it stops too soon. You need to make the central manager to repeat the scan itself then you'll get optimal scanning :-)

@liamnichols
Copy link
Owner

For some reason, when I just left the scan going it would only discover each beacon once and then it would never show up again until i stopped and started the scan again. I decided to then put it on a loop to start and stop scanning because I couldn't see a better way to do it using CBCentralManager.

Do you have any examples that you can link to showing your method? Or maybe you can raise a pull request? :)

Liam

@bagusflyer
Copy link

I remove

[self.foundBeacons removeAllObjects];

in _timerDidFire_, then everything seems to be fine.

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

No branches or pull requests

3 participants