Skip to content
New issue

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

Accuracy House + Room + Navigation don't work #48

Closed
luskin opened this issue Jul 10, 2016 · 7 comments
Closed

Accuracy House + Room + Navigation don't work #48

luskin opened this issue Jul 10, 2016 · 7 comments
Labels
Milestone

Comments

@luskin
Copy link

luskin commented Jul 10, 2016

if you choose location accuracy house or room you get no responses...

@luskin luskin changed the title Location House + Room don't work Accuracy House + Room + Navigation don't work Jul 10, 2016
@ghost
Copy link

ghost commented Jul 17, 2016

This is happening for me too, except house is working for me. House is the most detailed I can get.

@dkrusenstrahle
Copy link

Same error for me. Hard to use it without these accuracies.

@dkrusenstrahle
Copy link

Any solution to this? Or perhaps a suggestion for other pod?

@luskin
Copy link
Author

luskin commented Aug 11, 2016

No solution, I had to end up not using this package.

@malcommac
Copy link
Owner

Take a look to 1.0.0 and tell me if it works

@MetalheadSanya
Copy link

MetalheadSanya commented Aug 20, 2016

Use 1.0.0, get this issue. With .Block all work correct.

@malcommac
Copy link
Owner

I've made some further investigations and I've found a logic error (fixed in 8058990 and available in 1.0.1 I'll publish in less than an hour).

In fact both .Room and .Navigation uses kCLLocationAccuracyBest and kCLLocationAccuracyBestForNavigation which does not mean a valid fixed value (a CLLocationAccuracy which identify the meters of uncertainly) but the best value which the phone can achieve (by consuming higher energy).
So the value we can accept for both the value is < kCLLocationAccuracyNearestTenMeters. If you use .OneShot you will receive the first value below kCLLocationAccuracyNearestTenMeters GPS module can receive. Theoretically with .Continuous location scan you may receive better values (this always depends by several external factors).
I'll publish this update quickly. Thank you for your report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants