core-bluetooth

I'm new to working with BLE, currently trying to make a simple application which would connect to my custom BLE device. I am able to discover the BLE device, but for some reason i can't connect to it. I tried to check it with 'Light Blue', it shows my device as connectable and seems to work fine. But in my app after i discover the device, CB manager tries to connect to it and seems to 'freeze'? Function 'didConnect peripheral' is never triggered, and state of peripheral is forever 'connecting'. How can i identify the problem? Is there any options i can include in connection method, or somehow

First things first: running OSX 10.10.4, iOS 4, Xcode 6.3.2, iPhone 6, Swift Short story: I have a certain Bluetooth LE device here from which I want to receive notifications when values of a Characteristic change, e.g. by user input. Trying to subscribe to it does not succeed, but rather yields an error Error Domain=CBATTErrorDomain Code=10 "The attribute could not be found." Long story: So, I have a BluetoothManager class in which I start scanning for Peripherals as soon as my $CBCentralManager.state is .PoweredOn . That's easy, I'm even a good citizen and scan specifically for those with

i'm trying to implement an application using a Bluetooth 4.0 module, and I wonder if using this application with an Iphone 3GS containing a simple Bluetooth 2.1 EDR module is going to enable me take advantage of the the low energy in my 4.0 module. Thank you for your answers Bluetooth 4.0 is the standard, which includes both classical Bluetooth Basic Rate/Enhanced Data Rate (BR/EDR) and Bluetooth Low Energy (BLE, or Bluetooth Smart, which is a marketing name). Compatibility depends on the the device and Bluetooth chip e.g. is it a BR/EDR only chip (Bluetooth 3.0), a BLE only chip or a dual

After I have finished disconnecting from my bluetooth devices, seeing that they have disconnected in the didDisconnectPeripheral delegate, I attempt to dismiss my viewcontroller. When this happens I see the message: "[CoreBlueooth] XPC Connection Invalid" Is there something in specific that has to be cleaned up with Bluetooth before the viewcontroller is dismissed? I placed CBCentralManager to a singleton and the error message is solved. ( CBCentralManager will not be deallocated) I was getting the following message: [CoreBlueooth] XPC Connection Invalid And I wasn't able to scan BLE devices

I'm working on an application that connects phones via core bluetooth (BLE). The connection and data transmission work beautifully, but there is one small imperfection. When connecting to a new device, a pin must be entered on one of the devices. The application is supposed to be very instantaneous, and the pin-input greatly interrupts this process. I'm not worried about security, and I've personally connected my phone to many bluetooth devices without entering pins, so I was just wondering how this could be done with the iOS api. Thanks! If you specify any of your peripheral's characteristics

I initialize the CBCenteralManager in viewdidload on main queue. First time update state method is called and start scanning for bluetooth devices but didDiscoverPeripheral: delegate method never get called. Code is : - (void)viewDidLoad { [super viewDidLoad]; self.CM = [[CBCentralManager alloc]initWithDelegate:self queue:nil]; } -(void)centralManagerDidUpdateState:(CBCentralManager *)central{ if (central.state == CBCentralManagerStatePoweredOn) { [self.CM scanForPeripheralsWithServices:nil options:nil]; } } - (void)centralManager:(CBCentralManager *)central didDiscoverPeripheral(CBPeripheral*

When I utilize the CB framework in my app, I don't introduce any concurrency nor reactive approach and everything works fine. UI is not blocked when I receive over 100 samples per second from peripheral. Does that mean it is designed to work asynchronously? I haven't found any resources that states it's asynchronous nature, nor have I found any implementation where someone introduces dispatch async or background threads while working with Core Bluetooth. Is it safe to say that Core Bluetooth framework is intrinsically asynchronous and one should not bother with dispatch_async and thing like