Location Capability behavior for Desktop bridge application
We have a UWP application which we converted to Desktop bridge application.
In the app we use Location related API's and have declared <DeviceCapability Name="location"/> in the appxmanifest file.
The system behaviour of prompting the user to allow access to precise location was working fine before the app was converted to Desktop bridge application.
Post the conversion, access to location is granted by default as soon as the application is installed.
We have tried to search for any documentation which explains this behaviour, but haven't found anything.
It would be great if someone can point to us to a document which explains this behaviour.
Your UWP app could publish store directly. why you want convert it to desktop-bridge?
As you mentioned above, it works well if adding location capability for uwp appxmanifest.
Post the conversion, access to location is granted by default as soon as the application is installed. what behavior that you want to implement?
Sign in to comment