Using NCS's anti-spoofing keys with the FMDN locator tag app

[Jon1029384756]

I've been testing the FMDN locator tag sample application with a nRF52840 devkit and I would very much like to get an answer to the following questions:

1. Is it possible to get past the provisioning stage using Nordic's Model ID and anti-spoofing key without having filled out the "Google Fast Pair, Audio Switch & Find My Device Proposal Form"?

2. If so, what are the exact steps I need to take in order to get this to work? I understand that I need to be on "Google’s email allow list for the FMDN feature" but I'm not sure exactly what that entails. I've followed Google's model registration instructions (Fast Pair  |  Google for Developers) but that doesn't seem to help. I assume I would need a to have a device registered in the Nearby console with Nordic's Model ID and Anti-Spoofing key in order for my Android device to be able to properly provision the devkit running the locator tag app but I don't know how to do that assuming it's even possible.

Any help would be much appreciated.

[Amanda Hsieh]

Hi, 

1. Is it possible to get past the provisioning stage using Nordic's Model ID and anti-spoofing key without having filled out the "Google Fast Pair, Audio Switch & Find My Device Proposal Form"?

If the test Android device uses a primary email account that is not on Google’s email allow list for the FMDN feature, testing steps will fail at the FMDN provisioning stage for the default debug (uncertified) device model. To be able to test with debug device models, register your development email account by completing Google’s device proposal form. You can find the link to the device proposal form in the Fast Pair Find My Device Network extension specification.

2. If so, what are the exact steps I need to take in order to get this to work?

You can find the link to the device proposal form in the Fast Pair Find My Device Network extension specification. 

Regards,
Amanda H.