cli: [Bug]: @shopify/app v3.35.0 "deploy" command fails with unexpected error
Please confirm that you have:
- Searched existing issues to see if your issue is a duplicate. (If you’ve found a duplicate issue, feel free to add additional information in a comment on it.)
- Reproduced the issue in the latest CLI version.
In which of these areas are you experiencing a problem?
App
Expected behavior
App should be deployed successfully.
Actual behavior
Deploy script fails with the following error:
The Partners GraphQL API responded unsuccessfully with the HTTP status 200 and errors:
[
{
"message": "Unexpected system error",
"extensions": {
"code": "500"
}
}
]
This error is also sometimes returned in Spanish:
The Partners GraphQL API responded unsuccessfully with the HTTP status 200 and errors:
[
{
"message": "Error inesperado del sistema",
"extensions": {
"code": "500"
}
}
]
The error also only occurs when @shopify/app v3.35.0
is used. The following dependency config for example, works as expected:
"@shopify/app": "3.34.0",
"@shopify/cli": "3.35.0",
Stack trace
at (graphql-request/src/index.ts:410)
throw new ClientError(
at step (graphql-request/dist/index.js:63)
op = body.call(thisArg, _);
at next (graphql-request/dist/index.js:44)
function verb(n) { return function (v) { return step([n,
v]); }; }
at fulfilled (graphql-request/dist/index.js:35)
function fulfilled(value) { try {
step(generator.next(value)); } catch (e) { reject(e); }
}
at processTicksAndRejections
(node:internal/process/task_queues:95)
Reproduction steps
- Create new app boilerplate using
npm init @shopify/app@latest
- Create a new extension inside app using
npm run shopify app generate extension
- Run
npm run deploy
to try to deploy the app & extension
Operating System
Windows 11
Shopify CLI version (check your project’s package.json
if you’re not sure)
3.35.0
Shell
Gitbash
Node version (run node -v
if you’re not sure)
18.12.1
What language and version are you using in your application?
Node 18.12.1
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 20 (4 by maintainers)
Thanks all for the continued reports! The CLI is fine in the latest version, but there seems to be an incident happening on the API side, and I’ve confirmed that our team is looking into it.
This should be fixed in 3.36.0. Please comment or open a new issue if an upgrade doesn’t solve the issue for you.