microg / microg/GmsCore

[com.ubercab] Incorrect map bounds when viewing the route in Uber

Open
#1,511 25 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

🗺 Maps bug confirmed
Dominant language
Java
Stars
14.6k
Forks
3.2k
Avg merge
12d 11h
Merged PRs (30d)
4

Description

Affected app
Name: Uber
Package id: com.ubercab

Describe the bug
When Uber is displaying the full route, the map is displayed incorrectly and doesn't match the route. It looks like Mapbox zoom calculation is done around the wrong point? The more you zoom in, the more correct it becomes. But as you zoom out, the route moves to the north.

This doesn't happen until you actually set a destination in Uber. At first, when you view the map with available cars, it looks correct. Also, it doesn't affect Lyft.

To Reproduce
Steps to reproduce the behavior:

  1. Open Uber
  2. Pick any destination
  3. Zoom out

Expected behavior
Route should align with the map

Screenshots
Initial view - clearly incorrect as it's over the water:

2021-07-05 17 57 09

Zoomed in - more or less correct:

2021-07-05 17 57 45

Zoomed out - route moves to the north:

2021-07-05 17 58 29

System
Android Version: 10
Custom ROM: LineageOS 17.1

microG
microG Core version: 0.2.21.212158
microG Self-Check results: All ticked

Additional context

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue on Android with Uber by selecting a destination and zooming out, then trace the Mapbox zoom or map-bounds calculation used for the full route. Compare the route alignment at different zoom levels and verify that the route remains aligned with the map without affecting the available-cars view or Lyft behavior.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, java
Domain
mobile-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.