We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Description of the problem: The accuracy of the Geolocation that is provided with the WatchPosition can be done better for iOS and Android.
Affected platform
OS of the development machine
Other information: For Android you better can use the "Fused Location" (#379)
And for Swift it uses by default:
self.locationManager.desiredAccuracy = kCLLocationAccuracyBest
But Best Accuracy isn't really the best option. There are also the options kCLLocationAccuracyNearestTenMeters and kCLLocationAccuracyBestForNavigation See: https://developer.apple.com/documentation/corelocation/cllocationaccuracy
kCLLocationAccuracyNearestTenMeters
kCLLocationAccuracyBestForNavigation
How can I chose myself which CLLocationAccuracy option to use?
CLLocationAccuracy
The text was updated successfully, but these errors were encountered:
Fixed in #1773
Sorry, something went wrong.
No branches or pull requests
Description of the problem:
The accuracy of the Geolocation that is provided with the WatchPosition can be done better for iOS and Android.
Affected platform
OS of the development machine
Other information:
For Android you better can use the "Fused Location" (#379)
And for Swift it uses by default:
But Best Accuracy isn't really the best option.
There are also the options
kCLLocationAccuracyNearestTenMeters
andkCLLocationAccuracyBestForNavigation
See: https://developer.apple.com/documentation/corelocation/cllocationaccuracyHow can I chose myself which
CLLocationAccuracy
option to use?The text was updated successfully, but these errors were encountered: