Estimote / iOS-Fleet-Management-SDK

Estimote Fleet Management SDK for iOS
https://developer.estimote.com
MIT License
1.18k stars 398 forks source link

Beacon not found after disconnect #202

Closed souhl closed 9 years ago

souhl commented 9 years ago

Hi,

we are facing the following issue:

After starting ranging beacons, we find and connect to a beacon in order to get some parameters from it. This works stable.

But when we disconnect this beacon we don't find it again.

Disconnect is done via [beaconConnection cancelConnection];

After the disconnect was successful - didDisconnectWithError returned no error - we are ranging again, but the beacon is not showing up anymore. Only a restart of the app solves the issue.

Anything else we need to do clean up things, except calling cancelConnection?

Thanks Sascha

martinklimek commented 9 years ago

@souhl can you confirm that device was disconnect looking at bluetooth icon on status bar?

souhl commented 9 years ago

@martinklimek oh, yes. it is still connected when I check the settings. So, what do we need to do disconnect properly?

martinklimek commented 9 years ago

In iOS may be delay between sending disconnect request and actual disconnect (bluetooth icon is not highlighted) - can you check if this is actually happening?

souhl commented 9 years ago

yes, but nothing happens. at the moment I just call cancelConnection. Do I need to call disconnect, too? When I just call disconnect nothing happens. I expected that the didDisconnect callbacks fireback...

martinklimek commented 9 years ago

actually both disconnect and cancelConnection methods do the same thing. We are going to deprecate cancelConnection method soon. Anyway - do you get didDisconnect callback in 3.2.9?

souhl commented 9 years ago

I think I found the issue... will double check later this week.

martinklimek commented 9 years ago

Cool, let me know!

martinklimek commented 9 years ago

Actually I was looking more into your issue and did disconnect event was missing. Test with 3.2.10.

martinklimek commented 9 years ago

@souhl any news on that?

souhl commented 9 years ago

@martinklimek we had a software bug which simply reconnected to lost connections all the time... closing this.