Connecting Convex with EAS fails with `GraphQL request failed`.

[axeelz]

Build/Submit details page URL

No response

Summary

I'm trying to use Convex in my Expo app, following this guide.

1. I am logged in to my EAS account (running eas init outputs Project already linked).
2. I am running the latest EAS CLI version
3. I run eas integrations:convex:connect, it prompts for the region, team and project names, then fails with

✖ Failed to create Convex team
Failed to parse the request body as JSON: EOF while parsing a value at line 1 column 0
Request ID: xxx
    Error: GraphQL request failed.

Managed or bare?

Bare

Environment

  expo-env-info 2.1.0 environment info:
    System:
      OS: macOS 26.5.2
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 26.4.0 - /Users/axel/.local/share/mise/installs/node/latest/bin/node
      npm: 11.17.0 - /Users/axel/.local/share/mise/installs/node/latest/bin/npm
    Managers:
      CocoaPods: 1.16.2 - /opt/homebrew/bin/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 25.5, iOS 26.5, macOS 26.5, tvOS 26.5, visionOS 26.5, watchOS 26.5
    IDEs:
      Xcode: 26.6/17F113 - /usr/bin/xcodebuild
    npmPackages:
      expo: ^57.0.0 => 57.0.2
      expo-router: ~57.0.3 => 57.0.3
      expo-updates: ~57.0.6 => 57.0.6
      react: 19.2.3 => 19.2.3
      react-native: 0.86.0 => 0.86.0
    Expo Workflow: bare

20/20 checks passed. No issues detected!

Error output

✖ Failed to create Convex team
Failed to parse the request body as JSON: EOF while parsing a value at line 1 column 0
Request ID: xxx
CombinedError: [GraphQL] Failed to parse the request body as JSON: EOF while parsing a value at line 1 column 0
    at makeResult (/Users/axel/.local/share/mise/installs/npm-eas-cli/20.5.1/lib/node_modules/eas-cli/node_modules/@urql/core/dist/urql-core-chunk.js:381:43)
    at fetchOperation (/Users/axel/.local/share/mise/installs/npm-eas-cli/20.5.1/lib/node_modules/eas-cli/node_modules/@urql/core/dist/urql-core-chunk.js:744:71)
    at process.processTicksAndRejections (node:internal/process/task_queues:104:5)
    at async /Users/axel/.local/share/mise/installs/npm-eas-cli/20.5.1/lib/node_modules/eas-cli/node_modules/wonka/dist/wonka.js:346:20 {
  graphQLErrors: [
    {
      extensions: [Object],
      message: 'Failed to parse the request body as JSON: EOF while parsing a value at line 1 column 0',
      locations: [Array],
      path: [Array]
    }
  ],
  networkError: undefined,
  response: Response {
    size: 0,
    timeout: 0,
    Symbol(Body internals): { body: [Gunzip], disturbed: true, error: null },
    Symbol(Response internals): {
      url: 'https://api.expo.dev/graphql',
      status: 200,
      statusText: 'OK',
      headers: [Headers],
      counter: 0
    }
  }
}
    Error: GraphQL request failed.

Reproducible demo or steps to reproduce from a blank project

Run

• npx create-expo-app@latest --template default@sdk-57
• cd into the newly created project
• Run eas init
• Run eas integrations:convex:connect
• It fails

[vineyardbovines]

Hit the same error today. Some debugging that narrows it down — the bug is server-side, not in the CLI.

Replaying the exact CreateConvexTeamConnection mutation with a hand-built request against https://api.expo.dev/graphql reproduces it, and the raw GraphQL error carries metadata the CLI doesn't print:

{
  "requestId": "6c536a75-428b-4e81-8239-838bfb608f04",
  "code": "INTERNAL_SERVER_ERROR",
  "errorCode": "CONVEX_API_BAD_REQUEST_ERROR",
  "errorType": "USER",
  "metadata": {
    "code": "BadJsonBody",
    "path": "/v1/teams/507777/create_access_token",
    "status": 400
  },
  "isTransient": false
}

So the EAS backend creates the Convex team fine (a concrete team id shows up in the path), then calls Convex's management API POST /teams/{team_id}/create_access_token with an empty body. Convex's OpenAPI spec for that endpoint (management-openapi.json) accepts JSON null or a CreateTeamAccessTokenArgs object, but a zero-byte body isn't valid JSON, so their axum server rejects it with exactly this message. Convex reworked the team access token platform endpoints recently (get-convex/convex-backend#52965 and follow-ups), which is probably what broke the caller.

Likely fix on the EAS API side: send null or {} as the request body for that call.

Two side effects worth flagging:

• No ConvexTeamConnection row is persisted (the account's convexTeamConnections stays empty), so the whole flow rolls back and the dashboard shows "Not connected".
• The Convex-side team appears to be created before the failure, so each retry may leave an orphaned team on Convex's infrastructure.

[gwdp]

Thanks for the report @axeelz, and @vineyardbovines for the detailed triage, that was spot on.

Confirmed on our side: the root cause is a breaking change in Convex's API. As of get-convex/convex-backend@c3984f0c238f the create_access_token endpoint requires a valid JSON body, and our backend was calling it without one (the original contract). Retrying won't help, and there's no workaround from the CLI side for now.

The fix is server-side, so no CLI update is needed. We'll ship it shortly and follow up here once it's live. Sorry for the trouble!

[axeelz]

Thanks for the report @axeelz, and @vineyardbovines for the detailed triage, that was spot on.

Confirmed on our side: the root cause is a breaking change in Convex's API. As of get-convex/convex-backend@c3984f0c238f the create_access_token endpoint requires a valid JSON body, and our backend was calling it without one (the original contract). Retrying won't help, and there's no workaround from the CLI side for now.

The fix is server-side, so no CLI update is needed. We'll ship it shortly and follow up here once it's live. Sorry for the trouble!

Thanks for the quick investigation and clear explanation. That makes sense.
I’ll wait for the server-side fix and retry once it’s live :)