Zoom-Level Dependent Image Display Issue in Symbol Layer

[fawzirifai]

Environment

• Xcode version: 15.2
• iOS version: 17.2
• Devices affected:All devices
• Maps SDK Version: 11.0.0

Observed behavior and steps to reproduce

First Scenario:

1. Initialize the map at any chosen zoom level, for instance, 10.
2. Add a symbol layer, assigning the icon property to a specific ID.
3. After a 1-second delay, add an image to the style using the same ID. Observation: At zoom level 10, the image fails to display on the map. However, it becomes visible when zooming in or out to levels other than 10.

Second Scenario:

1. Initialize the map at any chosen zoom level, for instance, 10.
2. Initially, add an image to the style, associating it with a particular ID.
3. Add a symbol layer, assigning the icon property to the same ID.
4. After a 1-second delay, add a different image to the style using the same ID. Observation: The original image is visible at zoom level 10. Changing the zoom level to either higher or lower than 10 results in the display of the new image.

Expected behavior

1. On adding an image to the style with the same ID after a 1-second delay, the image should immediately appear on the map at the initial zoom level (10) without any need for adjusting the zoom level.
2. The image should remain consistently visible regardless of zooming in or out from the initial zoom level.

Additional links and references

Scenario 1:

Scenario 2:

Sample project: SymbolIcon.zip

[fawzirifai]

@baleboy @OdNairy three weeks without any response.

[baleboy]

Filed internally here: https://mapbox.atlassian.net/browse/MAPSNAT-1768

[fawzirifai]

Thank you, can we have an estimated time when this may be resolved? 1 week? 1 month? 2 months? @baleboy

[stephensilber]

We also need to support remote image loading for a SymbolLayer and have the same use case as OP here if that helps bump up this bug in the priority list

[fawzirifai]

https://github.com/mapbox/mapbox-maps-ios/issues/2000

[fawzirifai]

Any updates on this?

[karldusenbery]

I have a user reporting this who is on iOS Maps SDK 10.16.x, any update on a workaround or a fix?