Re: Catching CBPeripheralManager disconnect
Re: Catching CBPeripheralManager disconnect
- Subject: Re: Catching CBPeripheralManager disconnect
- From: Etan Kissling <email@hidden>
- Date: Mon, 18 Feb 2013 18:31:12 +0000
- Thread-topic: Catching CBPeripheralManager disconnect
Arvydas,
that is intended, as multiple apps on another iPhone may be connected with your peripheral app.
Therefore, it is not possible for the iPhone to know when a specific client connects / disconnects,
and it is also the reason why you cannot disconnect a link from the peripheral side.
You will have to achieve that with an own method. In my case, I'm using periodic reads as a
keep-alive mechanism. When the read does not occur regularly, the connection is considered
timed out and the GUI accordingly updated.
Etan
On 18.02.2013, at 19:28, Arvydas Sidorenko <email@hidden>
wrote:
> I noticed that there are no delegate reporting when central
> disconnects on demand or on poor signal and no samples I have seen
> deals with that. Any ideas how this can be achieved on current iOS
> version?
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Bluetooth-dev mailing list (email@hidden)
> Help/Unsubscribe/Update your Subscription:
>
> This email sent to email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Bluetooth-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden