Hi Richard,
Thank you for your reply.
The BLE device I’m trying to connect is a device that my company create, yes I’m certain that it’s a connectable device and most of the time I can connect without an issue, the mentioned issue in my first point is only happening with the testers running an adhoc/release version of the app.
For point #2, is it possible that it case the connection to drop/disconnect? I can’t see this warning in the log of the testers, I only can see it in xCode debug while running the app through it. I’ve tried and changed the type of writeValue to ‘CBCharacteristicWriteWithoutResponse’, that solved the warning but I’m not certain if it cause the disconnection from peripheral, currently, the code is: [_connectedSensor writeValue:[NSData dataWithBytes:&timeOutToSend length:1] forCharacteristic:_resetCharacteristic type:CBCharacteristicWriteWithoutResponse];
As of the scanning, even if I connect successfully to a peripheral, I don’t call stopScan, will this cause an issue to me? the app should only connect to one peripheral only, there is no multiple peripheral connection and a peripheral that is connected to the app is not presentable for other devices.
Best Regards,Mumen Shabaro
On December 18, 2016 at 10:58:47 PM, Richard Grundy (email@hidden) wrote:
_______________________________________________
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
|