A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://developers.google.com/maps/documentation/javascript/cloud-customization/test-style-updates below:

Test style updates | Maps JavaScript API

Test style updates

Stay organized with collections Save and categorize content based on your preferences.

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

  1. Duplicate the production map style.

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

    If the duplicated 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 duplicated 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 duplicated map style with your production map ID.

Note: A duplicated map style does not retain the versions of the style it duplicated. If you want to maintain the style history, you can instead take your tested changes from the duplicated 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.

Except as otherwise noted, the content of this page is licensed under the Creative Commons Attribution 4.0 License, and code samples are licensed under the Apache 2.0 License. For details, see the Google Developers Site Policies. Java is a registered trademark of Oracle and/or its affiliates.

Last updated 2025-07-09 UTC.

[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-09 UTC."],[[["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."]]],["To test map style updates before production, duplicate the existing production map style. Modify and publish changes in the duplicated style. Associate this duplicated style with a staging map ID to test in the staging environment. Once satisfied, link the updated style to the production map ID. Note that duplicated styles lack version history; consider updating the original style directly to preserve history. Style updates might take hours to appear across applications and websites.\n"]]

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4