<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://devzone.nordicsemi.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Device disconnects after Foget Device from ANCS server?</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/24227/device-disconnects-after-foget-device-from-ancs-server</link><description>Hi,
I am using &amp;quot;nrf5 sdk v11.0&amp;quot; ble_peripheral &amp;quot;ble_ancs_c&amp;quot; example for nrf52_DK(PCA10040) . 
 When i connect to the my ios device then accepted pairing request then i am able to get the notification from ios ANCS server . But when i do forget device</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Mon, 14 Aug 2017 10:52:53 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/24227/device-disconnects-after-foget-device-from-ancs-server" /><item><title>RE: Device disconnects after Foget Device from ANCS server?</title><link>https://devzone.nordicsemi.com/thread/95396?ContentTypeID=1</link><pubDate>Mon, 14 Aug 2017 10:52:53 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:98fc233e-1a58-4932-a5ff-1935c8a80091</guid><dc:creator>run_ar</dc:creator><description>&lt;p&gt;When you delete the bond information in iOS you should also do so on the peripheral. If you only delete it on the iOS side I don&amp;#39;t think you will be able to create a new bond. That is you will get an event PM_EVT_CONN_SEC_CONFIG_REQ, by default this will not be handled and the new bond will be rejected. This is the default behavior as you don&amp;#39;t know if the device trying to bond is the same as the known device (using the IRK to authenticate the peer is not safe, as it&amp;#39;s very easy for an attacker to use the same address as the known device)&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>