Find out where DeviceType gets determined and set it in the UwbSession when constructing it
forwardpointer opened this issue · comments
forwardpointer commented
#154 changes the constructor of UwbSession to accept a DeviceType, defaulting to Controller. Nothing in the codebase explicitly sets the DeviceType so all UwbSession instances will be Controller. We need to determine where that information comes from and set it accordingly.
Andrew Beltrano commented
Thanks for creating this to track the issue 👍
corbin-phipps commented
DeviceType is a parameter that comes from OOB. We now know that UwbSession is constructed by the WinRT APIs which have knowledge of the OOB parameters (including DeviceType) through the NearObjectIdentityToken, so I am closing this issue.