Home/ Questions/Q 8832497
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-14T08:32:43+00:00

Before upgrading to iOS6, it all worked fine, but now when I run [centralManager

  • 0

Before upgrading to iOS6, it all worked fine, but now when I run

[centralManager cancelPeripheralConnection:peripheral];

the callback gets triggered 

-(void) centralManager:(CBCentralManager *)central didDisconnectPeripheral:(CBPeripheral     *)peripheral error:(NSError *)error{
NSLog(@"Disconnected");
NSLog(@"Error: %@", [error localizedDescription]);
}

and the console outputs

Disconnected
Error: (null)

Still, the peripheral isn’t disconnected until I either turn of bluetooth in settings or turn of the phone (I have a connected status on the peripheral). Has anyone else discovered this iOS6 specific problem?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I believe this is a feature (if you would like to call it that) of iOS6.

    It’s just a way of not disrupting other applications that might use the connection (or it might be in the middle of a pairing procedure). It may take up to 45 seconds before it is disconnected.

    If possible the best solution might be to trigger the disconnect from the peripheral, then the disconnect would happen straight away.

    http://lists.apple.com/archives/bluetooth-dev/2012/Sep/msg00090.html

    • 0