mapbox / mapbox/mapbox-maps-flutter
Placing the app in the background while map is moving causes improper positioning on return
Nobody has claimed this yet.
- Dominant language
- Dart
- Stars
- 380
- Forks
- 204
- PR merge metrics
- No merged PRs in 30d
Description
If you swipe the map to move it and then place the app into the background while the map still has velocity, coming back into the app sometimes places the map at a completely wrong position. Ive seen it put the center point hundreds of miles away from what you would have expected the stop point to be.
Ive reproduced this on iOS on an iPad and iPhone. It doesnt happen 100% of the time but this seems to be the only way to reproduce this issue. This issue has happened on every version of the SDK including the current 2.8.0.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are identified. First reproduce this on iOS by moving the map, backgrounding the app before motion stops, and returning; then investigate map positioning across those lifecycle transitions. Done means returning to the app preserves the expected stopping position reliably.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- dart, flutter
- Domain
- mobile
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 28/100