Re: Unknown error 1309 in didFailToConnectToPeripheral
Re: Unknown error 1309 in didFailToConnectToPeripheral
- Subject: Re: Unknown error 1309 in didFailToConnectToPeripheral
- From: Etan Kissling <email@hidden>
- Date: Sat, 22 Feb 2014 08:57:19 +0000
- Thread-topic: Unknown error 1309 in didFailToConnectToPeripheral
BLE error codes are typically only 1 byte. Seeing a 1309 error code is most likely a CoreBluetooth internal thing (intended or unintended, like uninitialized memory.).
I think the best way to get a professional answer to your problem is the apple DTS (costs 49.50$ per ticket - 2 included for free per year).
If you use it, it would be cool if you could share their answer to the problem.
Otherwise, the least you could do is go to the bug reporter and then hope (most bugs are closed as duplicates of X, but you don’t have permission to view the status of X ;) ).
Etan
On 19.02.2014, at 19:21, Moe Aboulkheir <email@hidden> wrote:
> Hey,
>
> Long time listener, first time caller.
>
> I have seen a post or two about 1309, and a couple of SO questions, with no real result, mostly due to lack of information from the asker. To clarify:
>
> When connecting to a peripheral, didFailToConnectToPeripheral is sometimes passed "Unknown Error: 1309". The aggravating precondition seems to be that either the peripheral or the central is running in the background (with the appropriate UIBackgroundModes key). This error is inevitable with long running background processes and requires turning bluetooth off and on to resolve.
>
> I have opened a bug with Apple, but have not heard back.
>
> Take care,
> Moe
>
> More info:
>
> This happens with peripherals which have previously (sometimes immediately previous) been successfully connected to. The application on both sides of the connection is one which cycles between peripheral and central modes, however I have reproduced this issue with trivial sample code - one peripheral application and a central. The only requirement is repeated reconnections and backgrounding.
>
> The error object has no description, and nobody on the internet seems to have any information about what the error could mean, even vaguely, let alone how to fix it. I know this error code is used elsewhere to indicate a file position/seek/read error, but that's very little to go on.
> _______________________________________________
> 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