-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
eas build
: Build request failed - CombinedError: [GraphQL] Entity not authorized: AccountEntity
#1324
Comments
Hi,
|
I missed an important piece - I could successfully and reliably build the project with
No, never had.
|
Can you share more details? What's your username? I can't help you without it. |
|
Yes I have 2. seems to work:
|
OK can confirm 0.60.0 works. I tried downgrading to 1.1.1 earlier today but the issue was present there as well. |
Hi @Cafe137, I'm having trouble reproducing the issue on my end. To expedite my debugging, would you be able to clarify the following: It works on |
Hello @wschurman, Yes it does work on Let me know if you want me to try a few more things to help debug this. |
I had the exact same issue, the problem was the |
I have this issue on |
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) |
You are LOVE <3 |
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) |
For me this issue resolved when I switched to the account with which I had my keystore generated |
I solved this issue by removing
I need a build for development, the company's Expo project ID is different than my account's project ID, thus the problem... |
I can confirm this works for anyone that wants to run the project on It will also return the |
This works for me, thanks man! |
I was running a build using another expo login details and a project id has been generated before, i removed the project in my app.json and ran the command again and it worked perfectly |
Removing it and let eas build generate it works for me too. but the error message is very weird.
|
I'm also having this problem. For me, my account is a member of a legacy team account for one client, and an organization for another. No matter what I do, |
@diemer - |
Going to close this out as it is working as expected. The solution is to ensure that the |
installing the eas-cli@0.60.0 worked for me, but now I have this message after eas build -p android --profile preview: |
My solution was a little different.
And then when I upgraded to eas-cli@4.1.2, I received this error:
So, my assumption is that the old version didn't have this error written in... super exciting. |
I was just logged in to another expo account by mistake 👍 |
What worked for me was removing a commented line from my app.json file. |
Thanks brother , it works finlly |
I got this issue [GraphQL] Entity not authorized: AccountEntity[33727d9d-bb0e-403f-b16a-a258bd21c10c] (viewer = RegularUserViewerContext[dae9ee5a-1133-4fbc-948e-2541f4c377b0], action = READ, ruleIndex = -1) |
this error means that you are logged as owner. remove this in app.json :
|
Build/Submit details page URL
No response
Summary
There are some recent comments encountering the same problem in issue #694
Managed or bare?
Managed
Environment
Error output
Reproducible demo or steps to reproduce from a blank project
The text was updated successfully, but these errors were encountered: