search

troystribling / BlueCap

iOS Bluetooth LE framework
MIT License
714 stars 114 forks source link

Connection and disconnection not working properly #82

Closed JohnyKumar27 closed 6 years ago

JohnyKumar27 commented 6 years ago

Hi, Thanks for the awesome library. Actually i am facing some issues with the connection. I have created a Home screen and Device list in both screens i am trying to connect to peripheral. when i connect on device list it gets connected and i can write on characterstic and manually disconnect after that.(connection onSuccess and onFailure getting called) When i go back to home screen and and make connection with same peripheral then also it is getting connected i can write on characterstic and manually disconnect after that.(connection onSuccess and onFailure getting called). But when i second time on device list after calling .connect "onSuccess" and "onFailure" are not getting called. App flow is Showing device list from home screen.

Please if you can help on this.

troystribling commented 6 years ago

I do not know what App flow is. There could be any number of things wrong. I do not have enough information to help you.

JohnyKumar27 commented 6 years ago

Thanks for replying. After disconnection with peripheral, When i am trying to connect again with same peripheral then its onSuccess and onFailure not getting called. Is there any possibility that will happen?

troystribling commented 6 years ago

Are you using the same Peripheral instance or rediscovering the Peripheral? Did you originally disconnect? How many Peripherals are you connected to? Do you have access to logs on the Device you are connecting? Can you see what it is doing?

JohnyKumar27 commented 6 years ago

No, I am scanning again and using that peripheral, But i checked there addresses are same. Yes i am calling disconnect before scanning again. Connected with single peripheral Yes i have access of log, i am connecting with Raspberry Pi device. it is printing log of connect with peripheral even returning promise also after connection. but connection future completions(onSuccess,onFailure) are not getting called.

troystribling commented 6 years ago

Put a break point here https://github.com/troystribling/BlueCap/blob/master/BlueCapKit/Central/CentralManager.swift#L274. The source code is included in the pod.

If it is not called in your test case the issue is lower in the stack. If it is called you should be able to step through the code and see why the future is not completed.