<?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>Clean way to deal with a central not bonding (pseudo denial of service)</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/9956/clean-way-to-deal-with-a-central-not-bonding-pseudo-denial-of-service</link><description>iOS&amp;#39;s auto connect introduces a number of unpleasant corner cases that can be difficult to deal with. 
 One annoying error path is if you delete the bond data on the peripheral but not on the iOS device. When iOS auto-reconnects, it will not do any IOs</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Wed, 28 Oct 2015 11:34:18 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/9956/clean-way-to-deal-with-a-central-not-bonding-pseudo-denial-of-service" /><item><title>RE: Clean way to deal with a central not bonding (pseudo denial of service)</title><link>https://devzone.nordicsemi.com/thread/36946?ContentTypeID=1</link><pubDate>Wed, 28 Oct 2015 11:34:18 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:a22b37e0-ec0d-4eb7-a780-7b0302bfd72f</guid><dc:creator>Petter Myhre</dc:creator><description>&lt;p&gt;You cannot force the central. You can send a security request with sd_ble_gap_authenticate(), but iOS doesn&amp;#39;t respond to that.&lt;/p&gt;
&lt;p&gt;When the peripheral has lost the bond that you will end up in variant 2 in &lt;a href="http://infocenter.nordicsemi.com/topic/com.nordic.infocenter.s130.api.v1.0.0/group___b_l_e___g_a_p___p_e_r_i_p_h___e_n_c___m_s_c.html?cp=2_7_2_1_0_2_1_0_10"&gt;this&lt;/a&gt; MSC. So after you reply with sd_ble_gap_sec_info_reply(NULL) you could do a disconnect. It seems that to do this requires you to modify the Device Manager library a bit.&lt;/p&gt;
&lt;p&gt;I guess it doesn&amp;#39;t solve your problem, but it is an alternative to a timeout.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>