cli: [Bug]: @shopify/app v3.44.1 "npm run dev" 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

“npm run dev” should work successfully

Actual behavior

The Partners GraphQL API responded unsuccessfully with the HTTP status 200 and errors:                          
                                                                                                                
[                                                                                                               
{                                                                                                               
  "message": "Unexpected system error",                                                                         
  "extensions": {                                                                                               
    "code": "500"                                                                                               
  }                                                                                                             
}                                                                                                               

]

To investigate the issue, examine this 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)

Verbose output

npm verb cli /opt/homebrew/Cellar/node/19.8.1/bin/node /opt/homebrew/bin/npm
npm info using npm@9.5.1
npm info using node@v19.8.1
npm verb title npm run dev
npm verb argv "run" "dev" "--loglevel" "verbose"
npm verb logfile logs-max:10 dir:/Users/admin/.npm/_logs/2023-03-30T17_20_22_102Z-
npm verb logfile /Users/admin/.npm/_logs/2023-03-30T17_20_22_102Z-debug-0.log

> y-turbo-address-fill@1.0.0 dev
> shopify app dev



    The Partners GraphQL API responded unsuccessfully with the HTTP status 200 and errors:                          
                                                                                                                    
    [                                                                                                               
    {                                                                                                               
      "message": "Unexpected system error",                                                                         
      "extensions": {                                                                                               
        "code": "500"                                                                                               
      }                                                                                                             
    }                                                                                                               
  ]                                                                                                                 
                                                                                                                    
                                                                                                                    
  To investigate the issue, examine this 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

  1. npm run dev

Operating System

mac os 13.0.1 (22A400)

Shopify CLI version (check your project’s package.json if you’re not sure)

3.44.1

Shell

mac terminal

Node version (run node -v if you’re not sure)

v19.8.1

What language and version are you using in your application?

Node

About this issue

  • Original URL
  • State: closed
  • Created a year ago
  • Reactions: 1
  • Comments: 22 (1 by maintainers)

Most upvoted comments

@ilanlavi22 of course no one here would know. Shopify is a SaaS platform with a lot of moving parts. Clearly their partner oAuth machine is borked out right now, so no one can use it for a bit. Doubtful it’ll be out for days or anything, more likely just hours.

If you logged out of the Auth, and then run yarn run dev or whatever, the first thing the CLI tool will do is log you in. Until you’re logged in as a partner, there is nothing good that will happen. If you are prompted to login, that is good. If not, that is bad. You can tack on a --verbose to your commands to log out what is happening inside the CLI. Try that. More details you have, the better.

This should be fixed now. we had two separate issues, one with authentication services and one with the partners platform. if you are running into the oauth introspection 502ing run auth logout and relogin.