[[["āĻ¸āĻšāĻā§ āĻŦā§āĻāĻž āĻ¯āĻžā§","easyToUnderstand","thumb-up"],["āĻāĻŽāĻžāĻ° āĻ¸āĻŽāĻ¸ā§āĻ¯āĻžāĻ° āĻ¸āĻŽāĻžāĻ§āĻžāĻ¨ āĻšā§ā§āĻā§","solvedMyProblem","thumb-up"],["āĻ āĻ¨ā§āĻ¯āĻžāĻ¨ā§āĻ¯","otherUp","thumb-up"]],[["āĻāĻ¤ā§ āĻāĻŽāĻžāĻ° āĻĒā§āĻ°ā§ā§āĻāĻ¨ā§ā§ āĻ¤āĻĨā§āĻ¯ āĻ¨ā§āĻ","missingTheInformationINeed","thumb-down"],["āĻā§āĻŦ āĻāĻāĻŋāĻ˛ / āĻ āĻ¨ā§āĻ āĻ§āĻžāĻĒ","tooComplicatedTooManySteps","thumb-down"],["āĻĒā§āĻ°āĻ¨ā§","outOfDate","thumb-down"],["āĻ āĻ¨ā§āĻŦāĻžāĻĻ āĻ¸āĻāĻā§āĻ°āĻžāĻ¨ā§āĻ¤ āĻ¸āĻŽāĻ¸ā§āĻ¯āĻž","translationIssue","thumb-down"],["āĻ¨āĻŽā§āĻ¨āĻž / āĻā§āĻĄ āĻ¸āĻāĻā§āĻ°āĻžāĻ¨ā§āĻ¤ āĻ¸āĻŽāĻ¸ā§āĻ¯āĻž","samplesCodeIssue","thumb-down"],["āĻ āĻ¨ā§āĻ¯āĻžāĻ¨ā§āĻ¯","otherDown","thumb-down"]],["2025-09-04 UTC-āĻ¤ā§ āĻļā§āĻˇāĻŦāĻžāĻ° āĻāĻĒāĻĄā§āĻ āĻāĻ°āĻž āĻšā§ā§āĻā§āĨ¤"],[[["\u003cp\u003eBefore updating a production map style, it's recommended to test changes in a duplicated style to ensure desired results.\u003c/p\u003e\n"],["\u003cp\u003eThe testing process involves duplicating the production style, making and publishing changes, associating it with a separate map ID for staging, and thoroughly testing in the staging environment.\u003c/p\u003e\n"],["\u003cp\u003eOnce satisfied with the tested changes, associate the updated style with your production map ID for implementation.\u003c/p\u003e\n"],["\u003cp\u003eDuplicated styles do not inherit version history from the original, requiring manual updates to the original style for historical tracking.\u003c/p\u003e\n"],["\u003cp\u003eStyle changes may take a few hours to reflect across all platforms and devices.\u003c/p\u003e\n"]]],["To test map style updates before production, duplicate the existing production map style. Make and publish changes to the duplicate, then associate it with a separate map ID for staging. Test the style in the staging environment. If satisfied, link the updated style to the production map ID. Note that style changes can take a few hours to appear. Duplicated styles don't maintain version history; for history, apply tested changes to the original style.\n"],null,["# Test style updates\n\nSelect platform: [Android](/maps/documentation/android-sdk/cloud-customization/test-style-updates \"View this page for the Android platform docs.\") [iOS](/maps/documentation/ios-sdk/cloud-customization/test-style-updates \"View this page for the iOS platform docs.\") [JavaScript](/maps/documentation/javascript/cloud-customization/test-style-updates \"View this page for the JavaScript platform docs.\") [Web Service](/maps/documentation/maps-static/cloud-customization/test-style-updates \"View this page for the Web Service platform docs.\")\n\n\u003cbr /\u003e\n\nWhen you want to update a style that is being used in production, you\nmay want to test your style updates first.\n\n1. Duplicate the production map style.\n\n2. In the duplicated map style, make your changes and publish.\n\n If the duplicated style has just been updated, check the updated\n styles to make sure they look as expected. Map features with custom styles\n have a solid blue dot next to them. Expand all map features to find all\n changes.\n3. Associate the duplicated map style with a different map ID that you can use\n to test the style in your staging environment.\n\n4. Test your style changes in your staging environment.\n\n5. When you are happy with the results, associate the duplicated map style\n with your production map ID.\n\n| **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.\n| **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](/maps/documentation/ios-sdk/cloud-customization/troubleshoot#style-delay)."]]
