Test style updates

AI-generated Key Takeaways

• Before updating a production map style, it's recommended to test changes in a duplicated style to ensure they appear as expected.

• The testing process involves duplicating the style, making and publishing changes, associating it with a staging environment map ID for testing, and finally associating it with the production map ID once satisfied.

• Duplicated styles don't inherit version history from the original, requiring manual updates to the original style if history preservation is desired.

• Style changes might need a few hours to reflect across platforms, with potential delays for offline devices.

Select platform: Android iOS JavaScript Web Service

When you want to update a style that is being used in production, you may want to test your style updates first.

1. Make a copy of the production map style.

2. In the copied map style, make your changes and publish.

   If the copied style has just been updated, check the updated styles to make sure they look as expected. Map features with custom styles have a solid blue dot next to them. Expand all map features to find all changes.

3. Associate the copied map style with a different map ID that you can use to test the style in your staging environment.

4. Test your style changes in your staging environment.

5. When you are happy with the results, associate the copied map style with your production map ID.

Note: A copied map style does not retain the versions of the style it copied. If you want to maintain the style history, you can instead take your tested changes from the copied map style and make them to the original map style.

Note: Style changes can take a few hours to propagate to your apps websites, and apps can take longer if the devices aren't connected to the internet. If you're still not seeing your style changes after a few hours, see My style changes aren't updating.