eas-cli: `eas build`: Build request failed - CombinedError: [GraphQL] Entity not authorized: AccountEntity

Build/Submit details page URL

No response

Summary

✔ Uploaded to EAS 8s
Build request failed. Make sure you are using the latest eas-cli version. If the problem persists, report the issue.
    CombinedError: [GraphQL] Entity not authorized: AccountEntity[****] (viewer = UserViewerContext[****], action = READ, 
    ruleIndex = -1)

There are some recent comments encountering the same problem in issue https://github.com/expo/eas-cli/issues/694

Managed or bare?

Managed

Environment

  expo-env-info 1.0.5 environment info:
    System:
      OS: macOS 12.4
      Shell: 5.8.1 - /bin/zsh
    Binaries:
      Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
      npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
    IDEs:
      Xcode: /undefined - /usr/bin/xcodebuild
    npmPackages:
      @expo/webpack-config: ^0.16.2 => 0.16.12 
      babel-preset-expo: 8.5.1 => 8.5.1 
      expo: ^43.0.0 => 43.0.4 
      react: 17.0.1 => 17.0.1 
      react-dom: 17.0.1 => 17.0.1 
      react-native: 0.64.3 => 0.64.3 
      react-native-web: 0.17.1 => 0.17.1 
    npmGlobalPackages:
      eas-cli: 1.2.0
      expo-cli: 6.0.5
    Expo Workflow: managed

🎉 Didn't find any issues with the project!

Error output

eas build --platform=ios
An Expo user account is required to proceed.

Log in to EAS
✔ Email or username … ****
✔ Password … *********
» android: androidStatusBar.backgroundColor: Color conflicts with the splash.backgroundColor
» ios: expo-document-picker: Cannot configure iOS entitlements because neither the appleTeamId property, nor the environment variable EXPO_APPLE_TEAM_ID were defined.
✔ Using remote iOS credentials (Expo server)

If you provide your Apple account credentials we will be able to generate all necessary build credentials and fully validate them.
This is optional, but without Apple account access you will need to provide all the missing values manually and we can only run minimal validation on them.
✔ Do you want to log in to your Apple account? … yes

› Log in to your Apple Developer account to continue
✔ Apple ID: … ****
› Restoring session /Users/****/.app-store/auth/****/cookie
› Team **** (****)
› Provider **** (****)
✔ Logged in Local session
✔ Bundle identifier registered ****
✔ Synced capabilities: Enabled: Sign In with Apple
✔ Synced capability identifiers: No updates
✔ Fetched Apple distribution certificates
✔ Fetched Apple provisioning profiles
Provisioning profile (id: ****) is no longer valid
✔ Fetched Apple provisioning profiles
✔ Provisioning Profile - ID: ****
    Name: *[expo] **** AppStore ****
    Expiry: **** 
  Would you like to reuse the original profile? … yes
✔ Fetched Apple provisioning profiles
✔ Updated provisioning profile (****) with distribution certificate (****)
✔ Updated Expo profile for **** (****)

Project Credentials Configuration

Project                   ****
Bundle Identifier         ****
                          
App Store Configuration   
                          
Distribution Certificate  
Serial Number             ****
Expiration Date           ****
Apple Team                ****
Updated                   ****
                          
Provisioning Profile      
Developer Portal ID       ****
Status                    active
Expiration                ****
Apple Team                ****
Updated                   1 second ago
                          
All credentials are ready to build **** (****)

✔ Push Notifications setup for ****: ****

Compressing project files and uploading to EAS Build. Learn more: https://expo.fyi/eas-build-archive
✔ Uploaded to EAS 8s
Build request failed. Make sure you are using the latest eas-cli version. If the problem persists, report the issue.
    CombinedError: [GraphQL] Entity not authorized: AccountEntity[****] (viewer = UserViewerContext[****], action = READ, 
    ruleIndex = -1)

Reproducible demo or steps to reproduce from a blank project

eas build

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 30 (6 by maintainers)

Most upvoted comments

I had the exact same issue, the problem was the extra.eas.projectId in app.json file. I had projectId from another expo.dev account and the current logged in user was from my second account. Changing extra.eas.projectId to the projectId from my second account fixed the issue. So, always check if you have extra.eas.projectId from the same expo.dev account that you are logged in to through expo login or eas login.

+106
noorsheikh on Sep 1, 2022
  1. Do you have projectId in app.json? Sth like in the screenshot:
Screenshot 2022-08-31 at 15 27 10
  1. Can you please install eas-cli@0.60.0 and let me know if it works for you on that version?
  2. If 2. doesn’t work, stay on 0.60.0 but this time remove extra.eas.projectId from app.json.
+78
dsokal on Aug 31, 2022

I solved this issue by removing eas: projectId from app.json:

"extra": {
  "eas": {
    "projectId": "a1b2c3d4-e5f6-g7h8i9-j1k2-l3m4n5o6p7"
  }
}

I need a build for development, the company’s Expo project ID is different than my account’s project ID, thus the problem…

+21
hellocaio on Jan 6, 2023

I have this issue on 2.1.0 and didn’t have this issue on 0.60.0. The owner of the projectId is an organization I am part of. EAS build works fine (android & ios), however I encounter this error running the project on the dev-client so my current workaround is to exclude the projectId when doing so.

+4
hbriese on Sep 9, 2022

I solved this issue by removing eas: projectId from app.json:

"extra": {
  "eas": {
    "projectId": "a1b2c3d4-e5f6-g7h8i9-j1k2-l3m4n5o6p7"
  }
}

I need a build for development, the company’s Expo project ID is different than my account’s project ID, thus the problem…

This works for me, thanks man!

+3
JotaErrE01 on Mar 10, 2023

I Have also this issue: image with eas-cli/4.1.1 linux-x64 node-v20.5.0

+2
guillainbisimwa on Aug 9, 2023

I have this issue on version 2.2.1 and not on 2.1.0 (although the project ID is for a different account that I do not have access to, the 2.1.0 version gave a nicer error message about it)

+2
frankcalise on Oct 5, 2022

I also confirm that I was able to make it work with eas-cli@^0.60.0 without projectId in app.json (app.config.ts in my case)

+2
hirehouse on Oct 4, 2022

Yes I have projectId

2. seems to work:

✔ Uploaded to EAS 8s
⠸ Build in progress...
+2
Cafe137 on Aug 31, 2022

My solution was a little different. I was receiving this error on eas-cli@2.7.1:

We've encountered a transient error. Try again shortly.
Build request failed. Make sure you are using the latest eas-cli version. If the problem persists, report the issue.

And then when I upgraded to eas-cli@4.1.2, I received this error:

This account has used its iOS builds from the Free plan this month, which will reset in 9 days (on Fri Sep 01 2023). Upgrade your plan for more builds with shorter wait times and longer timeouts, and to run more builds concurrently with a subscription plan.

So, my assumption is that the old version didn’t have this error written in… super exciting.

+1
joshfavara on Aug 22, 2023

OK can confirm 0.60.0 works.

I tried downgrading to 1.1.1 earlier today but the issue was present there as well.

+1
Cafe137 on Aug 31, 2022

Hi, Thanks for reporting. Could you please share some details?

  • Do you have owner set in app.json?
  • Are you using a team / organization that has a different name than the username you’re using with EAS CLI? You can check the username with eas whoami.
+1
dsokal on Aug 31, 2022
Read more comments on GitHub
← eas-cli: `eas build`: Build failed - Could not find target 'app' in project.pbxproj
eas-cli: EAS build fails on iOS with ** ARCHIVE FAILED ** →