mapbox / mapbox/mapbox-maps-android

MultiPolygon with holes renders correctly in v10 but holes are missing in v11

Open
#2,667 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

auto-triaged bug :beetle:
Dominant language
Kotlin
Stars
578
Forks
161
PR merge metrics
No merged PRs in 30d

Description

## Environment

- Android OS version: Tested on Android 16 (Google Pixel 6) and multiple Android Emulator devices across various Mapbox-supported OS versions
- Devices affected: Reproducible on all tested real and virtual devices
- Maps SDK Version: v10.19.0 (correct) and v11.14.1 (incorrect)

## Observed behavior and steps to reproduce

When loading the same Mapbox Vector Tile (MVT) containing a MultiPolygon feature with holes:

1. Open the provided Android sample app (the MVT file is included as an app asset).
2. When the app starts, the map automatically loads and displays the vector tile.
3. In Mapbox Maps SDK v10.19.0 — the MultiPolygon renders correctly, with holes.
4. In Mapbox Maps SDK v11.14.1 — the holes are missing, and the polygon appears filled.

## Expected behavior

The MultiPolygon should render with its holes in v11.14.1 exactly as it does in v10.19.0.

## Notes / preliminary analysis

- The MVT file is identical in both tests.
- No external data source is required; the vector tile is bundled with the app.
- Issue confirmed on both physical and multiple emulator devices.

## Additional links and references

- Minimal reproduction (v10.19.0, correct rendering): https://github.com/ferencBolla/sample-app-map-10
- Minimal reproduction (v11.14.1, incorrect rendering): https://github.com/ferencBolla/sample-app-map-11
- Extracted GeoJSON of the MultiPolygon feature from the MVT is attached for reference:
[feature-multipolygon.json](https://github.com/user-attachments/files/21763792/feature-multipolygon.json)

- Screenshots comparing outputs:
Image
Image

Contributor guide

Open the contributing guide

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

Start by running the linked v10.19.0 and v11.14.1 sample apps with the bundled MVT and compare their rendering against feature-multipolygon.json. Trace the SDK path responsible for MultiPolygon holes and reproduce the regression; done means the same feature renders with its holes in v11.14.1 as in v10.19.0.

Written by the indexing model from the issue text.

Assessment

Tech stack
android, kotlin
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.