Android location service updates are unreliable
- Dominant language
- Python
- Stars
- 5.4k
- Forks
- 827
- Avg merge
- 9h 45m
- Merged PRs (30d)
- 58
Description
_Originally posted by @freakboy3742 in https://github.com/beeware/toga/issues/2462#issuecomment-2024498065_
I've only been able to test in the emulator, which has an interface for setting geolocation points; but using that UI doesn't seem to have any impact on the running app:
* It will return a GPS read in response to retrieving the current location; but if you use the "Single point" GUI to change the current location, the same (original) location is consistently returned
* The "Routes" UI lets you describe a driving path, but it doesn't seem to generate any location update events.
I'm unsure if this is me driving the emulator wrong, a bug in the emulator, or misuse of the geolocation APIs. If you're able to take this for a walk (literally), and/or let me know what I'm doing wrong with the emulator, that would be helpful.
Contributor guide
Research direction
Start by reproducing the behavior in the Android emulator with the Single point and Routes geolocation UI. Compare current-location reads with location update events, and determine whether the issue is emulator usage, an emulator defect, or misuse of the geolocation APIs; done means the cause and a reliable update behavior are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100