A RetroSearch Logo

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

Search Query:

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

Test style updates | Maps SDK for Android

Test style updates

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

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. 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-08-14 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-08-14 UTC."],[[["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."]]],["To test map style updates, duplicate the production map style, make and publish changes within the copy. Associate this new style with a distinct map ID for staging environment testing. After validating changes, link the updated style to your production map ID. Note that duplicated styles don't retain version history. Style updates can take hours to appear, and device internet connection can affect propagation time. For legacy map styles, follow separate instructions.\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