Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Component conversion failed: Cannot read properties of undefined (reading 'tagName') #1420

Closed
LeoCordiuS opened this issue Feb 24, 2022 · 4 comments
Labels
investigating We're actively investigating this issue

Comments

@LeoCordiuS
Copy link

Before the huge deployment process, I am getting error log as below
*** Deploying with SOAP API v53.0 *** ERROR running force:source:deploy: Component conversion failed: Cannot read properties of undefined (reading 'tagName')

Command that I am running is
sfdx force:source:deploy -p force-app/main/default -c -l NoTestRun -w 300

While running more verbose version
sfdx force:source:deploy -p force-app/main/default -c -l NoTestRun -w 300 --verbose --json
{ "status": 1, "name": "ConversionError", "message": "Component conversion failed: Cannot read properties of undefined (reading 'tagName')", "exitCode": 1, "commandName": "Deploy", "stack": "TypeError: Cannot read properties of undefined (reading 'tagName')\n at exports.validate (/Users/obidjonkomiljonov/.local/share/sfdx/client/7.139.0-cb77bf7/node_modules/fast-xml-parser/src/validator.js:109:33)\n at SourceComponent.parseAndValidateXML (/Users/obidjonkomiljonov/.local/share/sfdx/client/7.139.0-cb77bf7/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/sourceComponent.js:200:63)\n at SourceComponent.parseXml (/Users/obidjonkomiljonov/.local/share/sfdx/client/7.139.0-cb77bf7/node_modules/@salesforce/source-deploy-retrieve/lib/src/resolve/sourceComponent.js:88:25)\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\n at async RecompositionFinalizer.recompose (/Users/obidjonkomiljonov/.local/share/sfdx/client/7.139.0-cb77bf7/node_modules/@salesforce/source-deploy-retrieve/lib/src/convert/convertContext.js:78:26)\n at async RecompositionFinalizer.finalize (/Users/obidjonkomiljonov/.local/share/sfdx/client/7.139.0-cb77bf7/node_modules/@salesforce/source-deploy-retrieve/lib/src/convert/convertContext.js:40:38)\n at async ConvertContext.executeFinalizers (/Users/obidjonkomiljonov/.local/share/sfdx/client/7.139.0-cb77bf7/node_modules/@salesforce/source-deploy-retrieve/lib/src/convert/convertContext.js:278:17)\n at async ComponentConverter._flush (/Users/obidjonkomiljonov/.local/share/sfdx/client/7.139.0-cb77bf7/node_modules/@salesforce/source-deploy-retrieve/lib/src/convert/streams.js:108:30)\nOuter stack:\n at Function.wrap (/Users/obidjonkomiljonov/.local/share/sfdx/client/7.139.0-cb77bf7/node_modules/@salesforce/core/lib/sfdxError.js:171:27)\n at Deploy.catch (/Users/obidjonkomiljonov/.local/share/sfdx/client/7.139.0-cb77bf7/node_modules/@salesforce/command/lib/sfdxCommand.js:248:67)\n at processTicksAndRejections (node:internal/process/task_queues:96:5)\n at async Deploy._run (/Users/obidjonkomiljonov/.local/share/sfdx/client/7.139.0-cb77bf7/node_modules/@salesforce/command/lib/sfdxCommand.js:85:13)\n at async Config.runCommand (/Users/obidjonkomiljonov/.local/share/sfdx/client/7.139.0-cb77bf7/node_modules/@oclif/config/lib/config.js:173:24)\n at async SfdxMain.run (/Users/obidjonkomiljonov/.local/share/sfdx/client/7.139.0-cb77bf7/node_modules/@oclif/command/lib/main.js:27:9)\n at async SfdxMain._run (/Users/obidjonkomiljonov/.local/share/sfdx/client/7.139.0-cb77bf7/node_modules/@oclif/command/lib/command.js:43:20)\n at async Object.run (/Users/obidjonkomiljonov/.local/share/sfdx/client/7.139.0-cb77bf7/dist/cli.js:162:47)", "warnings": [] }

@LeoCordiuS LeoCordiuS added the investigating We're actively investigating this issue label Feb 24, 2022
@github-actions
Copy link

Thank you for filing this issue. We appreciate your feedback and will review the issue as soon as possible. Remember, however, that GitHub isn't a mechanism for receiving support under any agreement or SLA. If you require immediate assistance, contact Salesforce Customer Support.

@shetzel shetzel added the more information required Issue requires more information or a response from the customer label Mar 2, 2022
@shetzel
Copy link
Contributor

shetzel commented Mar 2, 2022

Please provide the output of sfdx -v --verbose. It would also be helpful to narrow down the conversion problem to a specific type or file using sfdx force:source:convert pointing to individual directories until the see the error.

@LeoCordiuS
Copy link
Author

LeoCordiuS commented Mar 6, 2022

We have find the error reason. It was Layout metadata. It would be better if CLI prints out the name of corrupted XML file 🙂

@no-response no-response bot removed the more information required Issue requires more information or a response from the customer label Mar 6, 2022
@MayTheSForceBeWithYou
Copy link

I encountered this error message when trying to deploy an ApexClass that lacked the -meta.xml file

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
investigating We're actively investigating this issue
Projects
None yet
Development

No branches or pull requests

4 participants