DocumentationExperience Cloud KCS

ACS Commons features unavailable in Adobe Experience Manager

Last update: August 18, 2026

In Adobe Experience Manager, ACS AEM Commons modules might be missing, unsupported API findings can appear in BPA reports, or version compatibility issues can prevent features from working correctly. These issues occur when ACS Commons isn’t deployed, uses unsupported APIs, or runs on incompatible versions. To fix this issue, identify the issue type, deploy the correct ACS Commons package, update unsupported APIs, and validate compatibility requirements.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS)

Issue/Symptoms

  • ACS Commons modules are missing from the AEM UI, such as Reports, Content Sync, or MCP Console.
  • /var/acs-commons/reports or related folders fail to deploy to AEMaaCS.
  • BPA output shows unsupported API findings such as {“type”:“unsupported.asset.api”,“told”:“com.day.cq.dam.api.AssetManager.createAsset”}.
  • BPA reports flag unsupported ACS Commons classes such as com.adobe.acs.commons.mcp.impl.processes.asset.AssetIngestor.
  • The Package Manager search bar doesn’t show the ACS Commons package.

Resolution resolution

To fix this issue, follow these steps:

  1. Review the BPA output or module behavior and classify the issue as a missing module, version incompatibility, unsupported API, or deployment filter issue.
  2. Confirm that the category matches the observed symptoms, such as missing UI elements, BPA errors, or deployment failures.
  3. Navigate to /system/console/bundles and search for acs.
  4. Verify that the bundles are in the Active state.
  5. Add ACS Commons dependencies to your Maven project and use the cloud classifier required by Cloud Service
  6. Ensure that the cloud classifier is used for AEMaaCS as required by Adobe’s API removal guidance
  7. Deploy the updated ACS Commons version through Cloud Manager.
  8. Revisit /system/console/bundles after deployment and confirm that ACS Commons bundles are active.
  9. If deployment fails, verify that ACS folders exist in the Git repository.
  10. Download the ACS Commons package from ACS Commons Releases and upload it to /crx/packmgr.
  11. Verify that the package installs successfully.
  12. Verify that the bundles are in the Active state.
  13. If installation fails, review the ACS Commons compatibility matrix.
  14. Verify that the required ACS Commons modules exist in the deployed code.
  15. In AEMaaCS, review the Git repository under ui.content/src/main/content/jcr_root.
  16. Confirm that /var/acs-commons/reports is included in filter.xml.
  17. Check CRX/DE for path visibility.
  18. If modules remain unavailable, confirm that the Git branch contains the required folders.
  19. Identify deprecated API usage such as com.day.cq.dam.api.AssetManager.createAsset or com.adobe.acs.commons.mcp.impl.processes.asset.AssetIngestor.
  20. Verify that unsupported.asset.api findings no longer appear.
  21. If findings persist, log an issue with the ACS Commons maintainers through GitHub.
  22. For AEMaaCS deployments, ensure that no modules attempt runtime writes to /apps or /libs, as these paths aren’t supported in Cloud Service.
  23. Verify that all ACS Commons code deploys successfully through Cloud Manager pipelines.
  24. Review the pipeline logs and confirm that the deployment completed successfully.
  25. If deployment issues occur, review filter.xml and remove any forbidden paths.
recommendation-more-help
experience-cloud-kcs-help-kbarticles