This might be related to #217, but most probably not.
What I discovered when porting an application to the Windows Phone platform was the first listener to be set up would never fire. It seems like initializeProximityDevice checks the proximityDeviceStatus property a bit too early and so the first call would always return STATUS_NO_NFC_OR_NFC_DISABLED even when the proximity device was correctly enabled.
This pull request reorganizes the initializeProximityDevice code so that things are hopefully initialized in the correct order.
This might be related to #217, but most probably not.
What I discovered when porting an application to the Windows Phone platform was the first listener to be set up would never fire. It seems like
initializeProximityDevicechecks theproximityDeviceStatusproperty a bit too early and so the first call would always returnSTATUS_NO_NFC_OR_NFC_DISABLEDeven when the proximity device was correctly enabled.This pull request reorganizes the
initializeProximityDevicecode so that things are hopefully initialized in the correct order.