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
Not returning location when location method is "Device only" #14
Comments
Hi! |
Also, what do you mean by |
Well Android has 3 Location modes that you can set: High accuracy, Battery saving and device only. He must be referring to the later. |
Yes, I am talking about the location mode in Android settings. I get no error, it just never returns any location data. |
Hi @hortemo! A more likely cause for this problem is that since you're using |
@MustansirZia - Hi, I am also facing the same issue. In some of the devices its getting lastLocation as null and getting request.getPriority() = 100 but is is not able to get location again and it is not going in catch block also. |
@MustansirZia the problem seems to be that if the device setting is set to "Device Only" (GPS only), trying to get the location with "balanced" accuracy never works (irregardless of GPS signal strength). This can be replicated easily in the simulator. A timeout is a good idea. Reading this setting and acting accordingly would be even better. EDIT: According to https://stackoverflow.com/questions/35830987/fused-location-provider-is-there-a-way-to-check-if-a-location-update-failed, it would be good to replace the |
@sraka1 You're probably right, it's about time we make use of a more appropriate callback. |
Package updated to |
actually just saw this bug. If no one else is working on it, ill try to find some time in the next few days and look at it. |
It didn't go inside catch statement? Which version of the library are you using? |
Hi! I am not able to get a location when using:
This is on a real device for which i.e. Google Maps works fine. It works fine for other location methods (High Accuracy and Battery Saving).
Is this your experience as well, or is it most likely something on my part?
The text was updated successfully, but these errors were encountered: