[eas-cli] Umbrella issue for API error handling

[barthap]

Feel free to edit/update this issue.

There are cryptic error messages when API requests fail, for example:

✖ Creating @barthap10/barthap-dogfood on Expo
    HTTPError: Response code 500 (Internal Server Error)

Since we reach API in two ways, we should handle both:

• GraphQL API - mostly this method: https://github.com/expo/eas-cli/blob/main/packages/eas-cli/src/graphql/client.ts#L44-L58
• REST got API

We should at least display error message from www by default. Also, maybe full stacktrace should be printed when given e.g. EXPO_DEBUG env variable.

List of other related issues

• Improve GraphQL error during eas build -p ios #136 - When building for iOS
• Handle invalid project owner error #163 - When registering projects

[byCedric]

I also want to add another use case which I ran into when working on the channel commands.

When we search for an app, it's based on user input (through project configuration). The app may or may not exist. It's a bit hard to create good feedback with this error handling kicking in with a 400 status when the app doesn't exist.

Take this query for example, just returning null for non-existing apps would be sufficient to signal there is no app with the name @bycedrictest/hue-p1 (there is one, without 1 suffix). It allows us to just check with if (app) and then log or prompt.

query {
  app {
    byFullName(fullName: "@bycedrictest/hue-p1") {
      id
      name
      fullName
    }
  }
}

[senorflor]

Accidentally added this use/test case to a closed issue, so linking here to close the loop: #136 (comment)

[github-actions]

This issue is stale because it has been open for 30 days with no activity. If there is no activity in the next 7 days, the issue will be closed.

[github-actions]

This issue was closed because it has been inactive for 7 days since being marked as stale. Please open a new issue if you believe you are encountering a related problem.