AEM Cloud Manager deployment fails due to invalid dialog XML file
This article explains how to resolve Adobe Experience Manager (AEM) Cloud Manager deployment failures that occur when a component dialog XML file contains invalid markup, such as HTML instead of a valid Granite UI dialog definition.
Description description
Environment
Adobe Experience Manager (AEM) Cloud Manager (all versions)
Issue/Symptoms
- Cloud Manager pipeline execution fails during the Deploy to Dev step.
- The failure occurs while AEM is installing the content package into the repository.
- Deployment is rolled back due to unsuccessful package installation.
- Errors may include XML parsing errors (for example., unclosed elements) or repository node errors (for example, No matching property definition).
Cause
The deployment failure is caused by one or more dialog XML files containing invalid markup, such as HTML tags or malformed XML, instead of a valid Granite UI dialog definition.
Resolution resolution
To fix the deployment failure caused by an invalid dialog XML file, follow these steps:
- Review the pipeline execution logs to find the specific component dialog XML file causing the failure (for example, a file like
jcr_root/apps//components//_cq_dialog/.content.xml). - Replace HTML markup with a valid Granite UI dialog definition. The root element should look like:
<?xml version="1.0"?> - Do not include HTML elements such as
<div>,<hr>, and similar tags. - Use an XML validator to ensure the dialog XML is well-formed and adheres to AEM dialog schema requirements.
- Check other component dialog files for similar issues, such as unclosed XML elements, duplicated nodes, or incorrect node types.
- After correcting all identified issues, commit the changes to your codebase and trigger a new deployment via Cloud Manager.
- If the deployment fails again, review the new pipeline execution details and logs for further errors.
recommendation-more-help
experience-cloud-kcs-help-kbarticles