Если вы хотите обновить стиль, который используется в производстве, вам, возможно, сначала захочется протестировать обновления стиля.
Дублируйте стиль производственной карты.
Внесите изменения в дублированный стиль карты и опубликуйте его.
Если дублированный стиль был только что обновлён, проверьте обновлённые стили, чтобы убедиться, что они выглядят так, как и ожидалось. Рядом с объектами карты с пользовательскими стилями отображается сплошная синяя точка. Разверните все объекты карты, чтобы увидеть все изменения.
Свяжите дублированный стиль карты с другим идентификатором карты, который вы можете использовать для тестирования стиля в своей промежуточной среде.
Протестируйте изменения стиля в сценической среде.
Если вы довольны результатами, свяжите дублированный стиль карты с идентификатором вашей производственной карты.
[null,null,["Последнее обновление: 2025-08-27 UTC."],[[["\u003cp\u003eBefore updating a production map style, it's recommended to test changes in a duplicated style to ensure they appear as expected.\u003c/p\u003e\n"],["\u003cp\u003eThe 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.\u003c/p\u003e\n"],["\u003cp\u003eDuplicated styles don't inherit version history from the original, requiring manual updates to the original style if history preservation is desired.\u003c/p\u003e\n"],["\u003cp\u003eStyle changes might need a few hours to reflect across platforms, with potential delays for offline devices.\u003c/p\u003e\n"]]],["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"],null,["Select 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/javascript/cloud-customization/troubleshoot#style-delay)."]]
