Hardware Model: iPhone5,2
Process: BTServer [330]
Path: /usr/sbin/BTServer
Identifier: BTServer
Version: ??? (???)
Code Type: ARM (Native)
Parent Process: launchd [1]
Date/Time: 2013-05-26 10:21:30.232 +0300
OS Version: iOS 6.1.4 (10B350)
Report Version: 104
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0xfffffffc
Crashed Thread: 8
Thread 0 name: Dispatch queue: com.apple.main-thread
Thread 0:
0 libsystem_kernel.dylib 0x3c4bee30 mach_msg_trap + 20
1 libsystem_kernel.dylib 0x3c4befd0 mach_msg + 48
2 CoreFoundation 0x342b52b6 __CFRunLoopServiceMachPort + 126
3 CoreFoundation 0x342b3fd6 __CFRunLoopRun + 814
4 CoreFoundation 0x34227238 CFRunLoopRunSpecific + 352
5 CoreFoundation 0x34285c46 CFRunLoopRun + 94
6 BTServer 0x000927a2 0x8b000 + 30626
7 libdyld.dylib 0x3c408b1c start + 0
24.05.2013, в 22:18, Alexey Grechaninov <
email@hidden> написал(а):
Hello everyone!
I'm getting very strange things. Periodically my CBPeripheral becomes invalid and I have no idea what does is mean.
Connection passes fine, then I retaining CBPeripheral instance and everything works fine until suddenly the peripheral become "invalid".
When is happens - it still indicated as connected and .isConnected returns true.
The only solution is to restart the app.
Here is example how it looks:
May 24 21:49:17 iPhone-5-Alexey BB Utility[4464] <Warning>: CoreBluetooth[WARNING] <CBConcretePeripheral: 0x200956a0 UUID = <CFUUID 0x2008b600> B17DDC76-54FA-080A-E029-C5421813C45C, Name = "Device Name", IsConnected = YES> is not a valid peripheral
"– centralManager:didDisconnectPeripheral:error:" never gets called as well...
Is just hangs and fills the console with provided warning message.
Looks like bug in iOS.
Did anyone faced this issue?
Best regards,
Alexey