Cannot disconnect ANCS while quit from App

[Stanley]

Dears, I am developing a ANCS application with nus service on our product. There are a few problems I don't know how to fix it. My problem is that : 1. ANCS will not disconnect with iPhone, while App closed. And reopen the App, the App cannot discover our device. (ANCS connected with iPhone all the time) I try to use the function "sd_ble_gap_disconnect" to break the connection of ANCS. But event will not get a event message when App closed. 2. System will reboot, while refuse to ANCS paring. I cannot find where it caused. I have checked in App_error~.c and try to print out a uart message. There is no message when reboot.

I know a smart phone would re-connect the device, when the connection broke unexpected. Have any way to break the ANCS connection, and stop it to advertise, but nus service is still alive?

[Sigurd]

You are developing your own mobile app? See chapter 4 in this document. Also note that the ANCS example will by default reject pairing request from an already bonded peer for security reasons. However, it is possible to override this by setting the .allow_repairing to true. (See Peer Manager event PM_EVT_CONN_SEC_CONFIG_REQ in main.c)

[Stanley]

Yes, we are developing App and nRF51822 ANCS device application. Now, iPhone will reconnect device automatically. App(Nordic App or Lightblue) cannot find the device during advertising. However, I will check your commend and see. Thanks for your advice, Sigurd.

[Sigurd]

You are unable to find the device during advertising, using the nRF-Connect app?

[Stanley]

There is no advertising happening during ANCS connected with App. I mean the application (the SDK of ANCS with nus) didn't know the connection breaking, when pca100028 disconnected from App. I think it could against the behavior when I merged the nus service together. Is it possible to merge the applications of nus and ANCS together?

[Sigurd]

Yes, it's possible to merge NUS and ANCS. So if I understand you correctly, your mobile app is not "informed" when the nRF51 disconnects from the mobile-app? So the mobile app thinks that it’s still connected to the nRF51?