<?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>Custom BLE app failing to connect to device.</title><link>https://devzone.nordicsemi.com/f/nordic-q-a/70672/custom-ble-app-failing-to-connect-to-device</link><description>Hi There, 
 Custom xamarin bluetooth app [using Plugin.BLE] is failing to connect to the device using ConnectToKnownDeviceAsync approach. User uses tap-to-pair and tries to make a connection to the device. 
 When user does tap-to-pair we are getting device</description><dc:language>en-US</dc:language><generator>Telligent Community 13</generator><lastBuildDate>Fri, 29 Jan 2021 08:01:57 GMT</lastBuildDate><atom:link rel="self" type="application/rss+xml" href="https://devzone.nordicsemi.com/f/nordic-q-a/70672/custom-ble-app-failing-to-connect-to-device" /><item><title>RE: Custom BLE app failing to connect to device.</title><link>https://devzone.nordicsemi.com/thread/291915?ContentTypeID=1</link><pubDate>Fri, 29 Jan 2021 08:01:57 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:0080b7e1-b34d-4c68-baf7-fc175d961089</guid><dc:creator>Balaji.kg</dc:creator><description>&lt;p&gt;Hi Simon,&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;sorry for the delay in replaying. I guess the bonding/pairing was not there after pairing the connection is happening. Thanks for your help.&lt;/p&gt;
&lt;p&gt;&lt;/p&gt;
&lt;p&gt;Regards,&lt;/p&gt;
&lt;p&gt;Balaji&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Custom BLE app failing to connect to device.</title><link>https://devzone.nordicsemi.com/thread/290271?ContentTypeID=1</link><pubDate>Wed, 20 Jan 2021 13:28:39 GMT</pubDate><guid isPermaLink="false">137ad170-7792-4731-bb38-c0d22fbe4515:fdfe4d8e-2ee5-4a05-b5f4-b6a556f29667</guid><dc:creator>Simonr</dc:creator><description>&lt;p&gt;Hi Balaji&lt;/p&gt;
&lt;p&gt;So you&amp;#39;re saying that you have to connect &lt;strong&gt;and&amp;nbsp;&lt;/strong&gt;pair over the nRFConnect app first in order to connect using your&amp;nbsp; custom app at all? I&amp;#39;m not an Android expert, but I think the ConnectToKnownDeviceAsync function will require you to be paired to the device in the first place in order to connect afterwards. Can you provide some more information on how you&amp;#39;re doing pairing, both on the Android side and on your nRF52 device.&amp;nbsp;&lt;/p&gt;
&lt;p&gt;The fact that this issue happen when you&amp;#39;re rebooting the device (I assume you refer to the nRF device) may suggest that the pairing information is deleted whenever you turn the device off. Or by &amp;quot;reboot&amp;quot; do you mean that you do a full flash erase and reprogram the nRF entirely? If so, it makes sense that the nRF won&amp;#39;t be able to &amp;quot;connect to a known device&amp;quot; as it wouldn&amp;#39;t be known anymore.&lt;/p&gt;
&lt;p&gt;Best regards,&lt;/p&gt;
&lt;p&gt;Simon&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>