`eas build`: Build request failed - CombinedError: [GraphQL] Entity not authorized: AccountEntity
See original GitHub issueBuild/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
Issue Analytics
- State:
- Created a year ago
- Comments:15 (4 by maintainers)
Top Results From Across the Web
[GraphQL] Unexpected server error when running eas build
When running eas build I get an error that seems to indicate the build servers have some issue. Does anyone else experience this...
Read more >GraphQL Unexpected server error when running eas submit
I'm trying to create a submission to ...
Read more >EAS SUBMIT ERROR: Failed to schedule submission ... - Reddit
I uploaded a build the same way 2-3 weeks ago and don't see… ... submission CombinedError: [GraphQL] Unexpected server error (Expo error ID: ......
Read more >combinederror: [graphql] invalid slug - You.com | The search engine ...
[GraphQL error]: Message: Variable "$slug" of required type "String! ... expo/eas-cliBuild request failed - CombinedError: [GraphQL] Entity not authorized#Â ...
Read more >Full Stack Error Handling with GraphQL and Apollo
Most GraphQL layers sit between the application frontend and a constellation of micro-services and data sources, which make them a focal ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I had the exact same issue, the problem was the
extra.eas.projectIdinapp.jsonfile. I hadprojectIdfrom another expo.dev account and the current logged in user was from my second account. Changingextra.eas.projectIdto theprojectIdfrom my second account fixed the issue. So, always check if you haveextra.eas.projectIdfrom the same expo.dev account that you are logged in to throughexpo loginoreas login.projectIdin app.json? Sth like in the screenshot:eas-cli@0.60.0and let me know if it works for you on that version?0.60.0but this time removeextra.eas.projectIdfrom app.json.