This was also sent to us via your local FAE.
Note that we had documented several problems with the Whitelist feature already in the previous SDK, and at this point we are not sure if any of these were addressed in recent SDK release (version 2.2).
It's possible that you have found another issue with the feature, not sure.
We do feel that this feature is important as it remembers that you already paired with a specific device and on subsequent attempts to the device it does not ask gain for the Passkey, so our team will test and verify that this specific functionality is not functioning correctly.
If we find that is the case, we will submit a change request to engineering and escalate so that the feature gets fixed within the next release of the SDK (ETA of that released is not known at this point).
We apologize for any inconvenience this has caused.
I will look into creating something and get back to you soon
Here's the instructions we promised (with code) that walks you through setting up the whitelist feature and testing it using three peripherals connecting to one central.
We will spend some additional time this week cleaning it up and making it easier to verify the BD_ADDR of the connected device.