Allow Fallback ToConsentless Positions Method
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
public: virtual void AllowFallbackToConsentlessPositions() = AllowFallbackToConsentlessPositions;
public void AllowFallbackToConsentlessPositions();
Public Sub AllowFallbackToConsentlessPositions ()
Windows 10 Anniversary Edition (introduced in 10.0.14393.0)
Windows.Foundation.UniversalApiContract (introduced in v3.0)
The coarse location feature allows the app to bypass the app-specific location switch (located in system settings) and obtain a "rough" location that is obfuscated with at least a 4km radius of uncertainty. The PositionSource property of the retrieved Geocoordinate will evaluate to Obfuscated.
Coarse location, if enabled in the app, will be utilized when the app-specific location switch is set to off (that is, when precise location is not allowed). The system-wide location switch, however, must be still switched on in order for any location retrieval to take place.
This feature is enabled for any Geolocator object that calls AllowFallbackToConsentlessPositions. It is disabled by default.
Normally, an app that uses location services should first call RequestAccessAsync to check if its app-specific location is switched on, and if not, it should prompt the user to go to system settings and switch it on. However, an app that has coarse location capability does not need to call RequestAccessAsync, as it can function whether location access is allowed or denied. The user may still turn on the app-specific location in order to use precise location, but this is not needed for the app's location functionality to work.
Submit and view feedback for