https://devzone.nordicsemi.com/f/nordic-q-a/18751/pairing-issues-with-s110-v8-0-0It may sound a bit old and you may have fixed them in latest Soft Device stacks however I wanted to share with you a couple of pairing issues we encountered with Soft Device 110 version 8.0.0. The project we have been working on is a simple UART moduleen-USTelligent Community 13Wed, 04 Jan 2017 14:57:57 GMThttps://devzone.nordicsemi.com/thread/72403?ContentTypeID=1Wed, 04 Jan 2017 14:57:57 GMT137ad170-7792-4731-bb38-c0d22fbe4515:b22b4b09-46c6-47aa-be6b-dee182569936run_ar<p>Thank you for reporting theses issues. Note that these are not stack issues, but limitations in the SDK device manager. Also note that for newer SDK&#39;s we have moved to a new module called peer manager.</p> <ol> <li> <p>In this case you should make sure you are not using the whitelist feature. As this will block the non resolvalbe address if it is changed.</p> </li> <li> <p>This is a limitation with the Device manager. As it uses the address of a device to identify it, but not the IRK. Since iOS uses a resolvable private address it might change (every 15 minutes actually) and your workaround of comparing the address might not work (unless you already use the IRK to resolve the address). Anyway, I would not recommend allowing a new bond from an unknown device. The reason I claim this is an unknown device is that anyone could copy the known address to connect to your device. the peer has to be authenticated by the encryption keys, using ediv and rand to identify the keys. If the iOS device lost it&#39;s keys it&#39;s not possible to know it&#39;s the same device. At least be aware that &quot;auto refreshing&quot; might be a security treath.</p> </li> </ol><div style="clear:both;"></div>