Hi All, The build in cloud failed with the error Unable to read manifest file (invalid manifest format) -> [Help 1] | Community
Skip to main content
A
ast_markgiul_77
December 7, 2023
Solved

Hi All, The build in cloud failed with the error Unable to read manifest file (invalid manifest format) -> [Help 1]

  • December 7, 2023
  • 3 replies
  • 1304 views

I am performing the build on the cloud in a development environment, and the build fails in the package structure with the message "Unable to read manifest file (invalid manifest format) -> [Help 1]." In the local environment, everything works correctly and as expected. I believe that this message is not the actual issue but that the problem lies elsewhere. The project has two folders, 'ui.frontend' and 'ui.frontend.sites.' Additionally, it is configured with JCR and filters.xml. I have also tried running the 'mvn clean package' command, which, according to the documentation, triggers the cloud build, but locally, there are no issues. I have also verified that there are no dependencies accessible only from my local environment. Thank you for any suggestions.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by ast_markgiul_77

It was actually not an AEM-related problem, but was simply incorrect formatting of the manifest file java, so I simply reformatted the file without the spaces that my editor was adding automatically and solved the problem.

3 replies

Shashi_Mulugu
Community Advisor
Shashi_MuluguCommunity Advisor
Community Advisor
December 9, 2023

@ast_markgiul_77 are you getting error in ui.apps.structure? It could be because of overlap in filter.xml in your two frontend modules.

    A
    ast_markgiul_77Author
    December 11, 2023

    Hi, @shashi_mulugu , thanks for your reply, Since I am new to AEM, could you give me more details? Also because locally everything works properly, these are my package apps filters:

    <?xml version="1.0" encoding="UTF-8"?> <workspaceFilter version="1.0"> <filter root="/apps/first-app/clientlibs"/> <filter root="/apps/first-app/components"/> <filter root="/apps/first-app/i18n"/> <filter root="/apps/cq"/> <filter root="/apps/granite"/> <filter root="/apps/second-app/clientlibs"/> <filter root="/apps/second-app/components"/> <filter root="/apps/second-app/i18n"/> </workspaceFilter>

     and this is the part of POM when declare the apps filters for the ui.structures:

    <filters> <!-- /apps root --> <filter> <root>/apps</root> </filter> <filter> <root>/apps/first-app</root> </filter> <filter> <root>/apps/second-app</root> </filter> <!-- Common overlay roots --> <filter> <root>/apps/sling</root> </filter> <filter> <root>/apps/cq</root> </filter> <filter> <root>/apps/dam</root> </filter> <filter> <root>/apps/wcm</root> </filter> <filter> <root>/apps/msm</root> </filter> <!-- Immutable context-aware configurations --> <filter> <root>/apps/settings</root> </filter> <!-- DAM folder root, will be created via repoinit --> <filter> <root>/content/dam/first-app</root> </filter> </filters>

    thanks a lot

      kautuk_sahni
      Community Manager
      kautuk_sahniCommunity Manager
      Community Manager
      February 28, 2024

      @ast_markgiul_77 If you have found out solution yourself, please share it with the community. 

      Kautuk Sahni
      A
      ast_markgiul_77AuthorAccepted solution
      February 28, 2024

      It was actually not an AEM-related problem, but was simply incorrect formatting of the manifest file java, so I simply reformatted the file without the spaces that my editor was adding automatically and solved the problem.

        Terms & ConditionsAccessibility statement

        Loading footer...