I’m encountering an error during app packing, even though my project has no API Mesh dependencies. How can I resolve this and complete the app packaging process?
aio app pack
✔ Copied project files
⠧ Getting api-mesh config...Error: Command failed with exit code 1: aio api-mesh get --json
{
"error": {
"oclif": {
"exit": 2
}
}
}
at makeError (/home/user/.nvm/versions/node/v20.19.4/lib/node_modules/@adobe/aio-cli/node_modules/execa/lib/error.js:60:11)
at handlePromise (/home/user/.nvm/versions/node/v20.19.4/lib/node_modules/@adobe/aio-cli/node_modules/execa/index.js:118:26)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
at async Pack.createDeployYamlFile (/home/user/.nvm/versions/node/v20.19.4/lib/node_modules/@adobe/aio-cli/node_modules/@adobe/aio-cli-plugin-app/src/commands/app/pack.js:174:36)
at async Pack.run (/home/user/.nvm/versions/node/v20.19.4/lib/node_modules/@adobe/aio-cli/node_modules/@adobe/aio-cli-plugin-app/src/commands/app/pack.js:95:7)
at async Pack._run (/home/user/.nvm/versions/node/v20.19.4/lib/node_modules/@adobe/aio-cli/node_modules/@oclif/core/lib/command.js:117:22)
at async Config.runCommand (/home/user/.nvm/versions/node/v20.19.4/lib/node_modules/@adobe/aio-cli/node_modules/@oclif/core/lib/config/config.js:329:25)
at async run (/home/user/.nvm/versions/node/v20.19.4/lib/node_modules/@adobe/aio-cli/node_modules/@oclif/core/lib/main.js:89:16)
at async AIOCommand.run (/home/user/.nvm/versions/node/v20.19.4/lib/node_modules/@adobe/aio-cli/src/index.js:38:12) {
shortMessage: 'Command failed with exit code 1: aio api-mesh get --json',
command: 'aio api-mesh get --json',
escapedCommand: 'aio api-mesh get --json',
exitCode: 1,
signal: undefined,
signalDescription: undefined,
stdout: '{\n "error": {\n "oclif": {\n "exit": 2\n }\n }\n}',
stderr: '',
failed: true,
timedOut: false,
isCanceled: false,
killed: false
}
✖ Command failed with exit code 1: aio api-mesh get --json
{
"error": {
"oclif": {
"exit": 2
}
}
}
› Error: Command failed with exit code 1: aio api-mesh get --json
› {
› "error": {
› "oclif": {
› "exit": 2
› }
› }
› }
Views
Replies
Total Likes
Views
Replies
Total Likes
System:
OS: Linux 6.8 Ubuntu 22.04.5 LTS 22.04.5 LTS (Jammy Jellyfish)
CPU: (6) x64 Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz
Memory: 6.90 GB / 15.43 GB
Shell: 5.1.16 - /bin/bash
Binaries:
Node: 20.19.4 - /home/user/.nvm/versions/node/v20.19.4/bin/node
Yarn: 1.22.22 - /usr/bin/yarn
npm: 10.8.2 - /home/user/.nvm/versions/node/v20.19.4/bin/npm
Virtualization:
Docker: 28.2.2 - /usr/bin/docker
npmGlobalPackages:
@ADOBE/aio-cli: 10.3.4
Proxies:
http: (not set)
https: (not set)
CLI plugins:
core:
@ADOBE/aio-cli 10.3.4
@ADOBE/aio-cli-plugin-app 13.3.0
@ADOBE/aio-cli-plugin-app-dev 2.1.2
@ADOBE/aio-cli-plugin-app-storage 1.2.0
@ADOBE/aio-cli-plugin-app-templates 2.0.3
@ADOBE/aio-cli-plugin-auth 4.0.1
@ADOBE/aio-cli-plugin-certificate 2.0.1
@ADOBE/aio-cli-plugin-config 5.0.1
@ADOBE/aio-cli-plugin-console 5.0.1
@ADOBE/aio-cli-plugin-events 4.0.1
@ADOBE/aio-cli-plugin-info 4.0.1
@ADOBE/aio-cli-plugin-runtime 7.1.0
@ADOBE/aio-cli-plugin-telemetry 2.0.3
@oclif/plugin-autocomplete 3.2.39
@oclif/plugin-help 6.2.36
@oclif/plugin-not-found 2.4.3
@oclif/plugin-plugins 5.4.54
@oclif/plugin-warn-if-update-available 3.1.53
user:
link:I have updated the CLI to version 11.0.1The issue persists.
Views
Replies
Total Likes
Thanks, couple additional questions:
- After upgrading to 11.0.1 is it the same error?
- Is it possible there's another aio installation being used somehow? Asking because in order to get this error, you would need to have the api mesh plugin adobe/aio-cli-plugin-api-mesh installed, but I don't see this under the user plugins in the aio info output.
- Are you by chance using the commerce starter kit?
Views
Replies
Total Likes
Yes, I am facing the same issue. After upgrading to 11.0.1,
I didn’t understand what you meant by "another aio installation." Can you clarify? Yes, I am using a starter kit
Views
Replies
Total Likes
Reason I'm asking about another aio installation is because the aio info above doesn't show the api-mesh plugin being installed, but the aio CLI is still trying to fetch an api mesh configuration during pack. It only does this when the api-mesh plugin is installed, so I'm wondering if you have another, older aio installed somehow (Maybe through nvm?) that has the api-mesh plugin that is somehow being used that needs to be updated.
Views
Replies
Total Likes
Views
Likes
Replies
Views
Likes
Replies