Test style updates

AI-generated Key Takeaways

• Cloud-based map styling updates can be tested before applying them to production environments to ensure desired visual results.

• The process involves duplicating the production style, making and publishing changes, associating it with a separate map ID for testing, and finally applying the tested style to the production map ID.

• Style changes may take some time to propagate to all users due to caching and internet connectivity.

• For Android, ensure you're using the latest Maps SDK renderer for compatibility.

• Legacy style updates have a different checking process outlined in the documentation.

Select platform: Android iOS JavaScript Web Service

To use cloud-based maps styling on Android, you must use the latest renderer for Maps SDK for Android. Follow these instructions.

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.