EAS project not configured. #1426

widjesh · 2022-10-07T15:00:50Z

Build/Submit details page URL

No response

Summary

When I execute the following command on my local machine:
eas update --message "bbbb1124232c2e24aeea2de822541fbbe599e1c0" --branch "development"
Everything works as expected, but the same command is being triggered through my Circle CI pipeline, but on that platform I am getting the following response:
EAS project not configured.
? Existing EAS project found for @************/Satyam-Tours (id = e3cbfdf1-eb35-41fe-**********). Configure this project? › (Y/n)��

Since this is a Pipeline build I am not able to select Y or N.

Can someone help me resolve this issue ?
This worked fine for the last 3 months. Not sure what suddenly happened

Managed or bare?

Managed

Environment

✖ Dependency tree validation for expo-modules-autolinking failed. This validation is only available on Node 16+ / npm 8.
✖ Dependency tree validation for @expo/config-plugins failed. This validation is only available on Node 16+ / npm 8.
✖ Dependency tree validation for @expo/prebuild-config failed. This validation is only available on Node 16+ / npm 8.
✖ Dependency tree validation for @unimodules/core failed. This validation is only available on Node 16+ / npm 8.
✖ Dependency tree validation for @unimodules/react-native-adapter failed. This validation is only available on Node 16+ / npm 8.
✖ Dependency tree validation for react-native-unimodules failed. This validation is only available on Node 16+ / npm 8.
Some dependencies are incompatible with the installed expo package version:

@react-native-picker/picker - expected version: 2.4.2 - actual version installed: 2.4.4
expo-dev-client - expected version: ~1.3.0 - actual version installed: 1.2.1
expo-updates - expected version: ~0.14.6 - actual version installed: 0.14.5
react-native - expected version: 0.69.6 - actual version installed: 0.69.5
Your project may not work correctly until you install the correct versions of the packages.
To install the correct versions of these packages, please run: expo doctor --fix-dependencies,
or install individual packages by running expo install [package-name ...]

Error output

No response

Reproducible demo or steps to reproduce from a blank project

Not sure how to answer this question.

The text was updated successfully, but these errors were encountered:

parniekovvakoms · 2022-10-09T10:38:41Z

The same problem. Everything was fine but after simple commit with only JS changes build has failed.

ysrarff · 2022-10-09T10:39:41Z

I'm experiencing a similar issue as well although it is with the eas build command

The gitlab CI pipeline that was working a month ago is now suddenly failing a few days back (last checked) prompting the "EAS project not configured" error.

Here's my gitlab CI file:

image: node:alpine

cache:
  key: ${CI_COMMIT_REF_SLUG}
  paths:
    - .npm
    # or with yarn:
    #- .yarn

stages:
  - build
  - ship

before_script:
  - npm ci --cache .npm
  # or with yarn:
  #- yarn install --cache-folder .yarn

eas-build:
  stage: build
  only:
    - master
    - qa
  before_script:
    - apk add --no-cache bash
  script:
    - EXPO_TOKEN=$EXPO_TOKEN EAS_NO_VCS=1 npx eas-cli build --platform all --non-interactive

variables:
  EXPO_TOKEN: $EXPO_TOKEN

My eas.json file:

{
  "cli": {
    "version": ">= 0.57.0"
  },
  "build": {
    "development": {
      "distribution": "internal",
      "android": {
        "gradleCommand": ":app:assembleDebug"
      },
      "ios": {
        "buildConfiguration": "Debug"
      }
    },
    "preview": {
      "distribution": "internal"
    },
    "production": {
      "android": {
        "buildType": "apk"
      }
    }
  },
  "submit": {
    "production": {
      "android": {
        "track": "production",
        "applicationId": "****"
      },
      "ios": {
        "appleId": "****",
        "ascAppId": "****",
        "sku": "****",
        "bundleIdentifier": "****"
      }
    }
  }
}

The error I am getting on my pipeline:

Hope @brentvatne could assist on this. Also I'm sorry if I'm latching on @widjesh 's issue as I thought it would be relevant - as from my pov it seems like it's the same root cause. I am fine submitting this as a separate issue if needed.

mossypaul · 2022-10-10T18:17:08Z

I'm having this same issue running on GitHub actions

widjesh · 2022-10-10T19:17:42Z

Hey Guys,
I found a fix for this issue

Just make sure you add this in your app.config.js

extra: {
eas: {
projectId: <INSERT_YOUR_PROJECT_ID>
},
},

This should resolve the issue. Not sure what caused this to be honest.

Let me know should you need any more information.

evenstay · 2022-10-10T20:26:48Z

Hey Guys, I found a fix for this issue

Just make sure you add this in your app.config.js

extra: { eas: { projectId: <INSERT_YOUR_PROJECT_ID> }, },

This should resolve the issue. Not sure what caused this to be honest.

Let me know should you need any more information.

This helped me. Thank you @widjesh

widjesh · 2022-10-10T20:34:52Z

Glad it worked for you.Good luck on your development

Lester016 · 2022-10-10T22:15:53Z

Glad it worked for you.Good luck on your development

Where can I find my project id?

ysrarff · 2022-10-11T08:29:12Z

Hey Guys, I found a fix for this issue

Just make sure you add this in your app.config.js

extra: { eas: { projectId: <INSERT_YOUR_PROJECT_ID> }, },

This should resolve the issue. Not sure what caused this to be honest.

Let me know should you need any more information.

I can confirm that this is a working solution for me too. I had to extend the values from my app.json and put in the app.config.js file and fill in the slug for my project to make it work. Thanks @widjesh !

Here's a snippet of a working example (app.config.js):

module.exports = ({ config }) => ({
  name: config.name,
  slug: "SLUG_FROM_EAS",
  extra: {
    eas: {
      projectId: "PROJECT_ID_FROM_EAS"
    }
  },
});

widjesh · 2022-10-11T14:05:34Z

Where can I find my project id?

@Lester016 Find your project ID in your expo web portal (www.expo.dev).
Let me know should you need more clarification this.

juanjorge · 2022-10-12T14:08:40Z

Hey Guys, I found a fix for this issue
Just make sure you add this in your app.config.js
extra: { eas: { projectId: <INSERT_YOUR_PROJECT_ID> }, },
This should resolve the issue. Not sure what caused this to be honest.
Let me know should you need any more information.

I can confirm that this is a working solution for me too. I had to extend the values from my app.json and put in the app.config.js file and fill in the slug for my project to make it work. Thanks @widjesh !

Here's a snippet of a working example (app.config.js):
module.exports = ({ config }) => ({
  name: config.name,
  slug: "SLUG_FROM_EAS",
  extra: {
    eas: {
      projectId: "PROJECT_ID_FROM_EAS"
    }
  },
});

this fixed me out, thank you !

dsokal · 2022-10-13T07:35:04Z

You should run eas init locally and commit the changes produced by the command. This will fix the issue for you.

widjesh · 2022-10-13T16:37:57Z

@dsokal The eas was already initialized at the time this issue occurred. I have added the fix that worked for me and for some of the other devs. Thank you

parniekovvakoms · 2022-10-18T09:12:17Z

Resolved by steps:

yarn global add eas-cli (update to last version)
module.exports = ({ config }) => ({
name: config.name,
slug: "SLUG_FROM_EAS",
extra: {
eas: {
projectId: "PROJECT_ID_FROM_EAS"
}
},
});

kyle-lam · 2022-10-27T21:37:26Z

I'm experiencing a similar issue as well although it is with the eas build command

The gitlab CI pipeline that was working a month ago is now suddenly failing a few days back (last checked) prompting the "EAS project not configured" error.

Here's my gitlab CI file:
image: node:alpine

cache:
  key: ${CI_COMMIT_REF_SLUG}
  paths:
    - .npm
    # or with yarn:
    #- .yarn

stages:
  - build
  - ship

before_script:
  - npm ci --cache .npm
  # or with yarn:
  #- yarn install --cache-folder .yarn

eas-build:
  stage: build
  only:
    - master
    - qa
  before_script:
    - apk add --no-cache bash
  script:
    - EXPO_TOKEN=$EXPO_TOKEN EAS_NO_VCS=1 npx eas-cli build --platform all --non-interactive

variables:
  EXPO_TOKEN: $EXPO_TOKEN
My eas.json file:
{
  "cli": {
    "version": ">= 0.57.0"
  },
  "build": {
    "development": {
      "distribution": "internal",
      "android": {
        "gradleCommand": ":app:assembleDebug"
      },
      "ios": {
        "buildConfiguration": "Debug"
      }
    },
    "preview": {
      "distribution": "internal"
    },
    "production": {
      "android": {
        "buildType": "apk"
      }
    }
  },
  "submit": {
    "production": {
      "android": {
        "track": "production",
        "applicationId": "****"
      },
      "ios": {
        "appleId": "****",
        "ascAppId": "****",
        "sku": "****",
        "bundleIdentifier": "****"
      }
    }
  }
}
The error I am getting on my pipeline:

Hope @brentvatne could assist on this. Also I'm sorry if I'm latching on @widjesh 's issue as I thought it would be relevant - as from my pov it seems like it's the same root cause. I am fine submitting this as a separate issue if needed.

any update on what changed causing this break?

Musigwa · 2022-12-20T17:17:50Z

Where can I find my project id?

You can log in to expo.dev with your account credentials and check out the target project.
Then, in the "Overview" section, the highlighted item on the screenshot should be your projectId.

Musigwa · 2022-12-20T17:20:55Z

Hey Guys, I found a fix for this issue
Just make sure you add this in your app.config.js
extra: { eas: { projectId: <INSERT_YOUR_PROJECT_ID> }, },
This should resolve the issue. Not sure what caused this to be honest.
Let me know should you need any more information.

I can confirm that this is a working solution for me too. I had to extend the values from my app.json and put in the app.config.js file and fill in the slug for my project to make it work. Thanks @widjesh !

Here's a snippet of a working example (app.config.js):
module.exports = ({ config }) => ({
  name: config.name,
  slug: "SLUG_FROM_EAS",
  extra: {
    eas: {
      projectId: "PROJECT_ID_FROM_EAS"
    }
  },
});

Some have app.config.js or app.json. Either of which works well when you add the recommended snippet by @dsokal

BrandonMathis · 2023-01-20T00:27:55Z

I also ran into this issue very recently.

The eas update command worked fine locally but would fail in CircleCI with the following message

Error: Project config: Slug for project identified by "extra.eas.projectId" (my.app.slug) does not match the "slug" field (project).
     Learn more: https://expo.fyi/eas-project-id

Not sure how this is happening but @juanjorge suggestion fixed this for me

Please consider re-opening this issue. The FYI article this error links to is quite unhelpful the the solution is very non-intuitive. Took me several hours to figure out what was happening. Seems that there is a bug in eas when it comes to extracting this slug out of wherever it is extracted from.

Maysfeak · 2023-02-22T15:33:40Z

Does anyone already figure out how this can be fix i also ran into this issue
Linking local project to EAS project id
Error: No config exists

henrymoulton · 2023-04-06T22:47:38Z

Also getting this issue on GitHub Actions but weirdly not locally:

Part of my config has:

    "name": "Name",
    "slug": "name",
    "extra": {
      "eas": {
        "projectId": "id"
      }
    },

henrymoulton · 2023-04-06T23:11:05Z

@jonsamp @byCedric @dsokal can this be re-opened?

dsokal · 2023-04-07T07:31:36Z

@henrymoulton can you please open a new issue with all the details? My intuition tells me this is not related to the original issue. It'd be super helpful if you could take new screenshots with more details visible. In particular, could you expand "Run eas update..." from:

henrymoulton · 2023-04-07T10:57:48Z

@dsokal thanks for the reply, I've refiled #1779

moosthuizen42 · 2023-09-05T09:45:06Z

Just in case this helps anyone, remember to specify the directory if you are working in a monorepo (ie. if your Expo project root is not the same as your repository's root). This issue, albeit silly, will result in the same symptoms.

Changing

- name: 📦 Install dependencies
  run: yarn install

- name: 🚀 Build app
  run: eas build -e preview -p android --non-interactive

to

- name: 📦 Install dependencies
  working-directory: ./app
  run: yarn install

- name: 🚀 Build app
  working-directory: ./app
  run: eas build -e preview -p android --non-interactive

was the solution for us.

widjesh added the needs review Issue is ready to be reviewed by a maintainer label Oct 7, 2022

dsokal closed this as completed Oct 13, 2022

henrymoulton mentioned this issue Apr 6, 2023

EAS project not configured on Github Actions expo/expo-github-action#217

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

EAS project not configured. #1426

EAS project not configured. #1426

widjesh commented Oct 7, 2022 •

edited

Loading

parniekovvakoms commented Oct 9, 2022 •

edited

Loading

ysrarff commented Oct 9, 2022 •

edited

Loading

mossypaul commented Oct 10, 2022

widjesh commented Oct 10, 2022

evenstay commented Oct 10, 2022

widjesh commented Oct 10, 2022

Lester016 commented Oct 10, 2022

ysrarff commented Oct 11, 2022

widjesh commented Oct 11, 2022

juanjorge commented Oct 12, 2022

dsokal commented Oct 13, 2022

widjesh commented Oct 13, 2022

parniekovvakoms commented Oct 18, 2022

kyle-lam commented Oct 27, 2022

Musigwa commented Dec 20, 2022

Musigwa commented Dec 20, 2022 •

edited

Loading

BrandonMathis commented Jan 20, 2023

Maysfeak commented Feb 22, 2023

henrymoulton commented Apr 6, 2023 •

edited

Loading

henrymoulton commented Apr 6, 2023

dsokal commented Apr 7, 2023

henrymoulton commented Apr 7, 2023

moosthuizen42 commented Sep 5, 2023

EAS project not configured. #1426

EAS project not configured. #1426

Comments

widjesh commented Oct 7, 2022 • edited Loading

Build/Submit details page URL

Summary

Managed or bare?

Environment

Error output

Reproducible demo or steps to reproduce from a blank project

parniekovvakoms commented Oct 9, 2022 • edited Loading

ysrarff commented Oct 9, 2022 • edited Loading

mossypaul commented Oct 10, 2022

widjesh commented Oct 10, 2022

evenstay commented Oct 10, 2022

widjesh commented Oct 10, 2022

Lester016 commented Oct 10, 2022

ysrarff commented Oct 11, 2022

widjesh commented Oct 11, 2022

juanjorge commented Oct 12, 2022

dsokal commented Oct 13, 2022

widjesh commented Oct 13, 2022

parniekovvakoms commented Oct 18, 2022

kyle-lam commented Oct 27, 2022

Musigwa commented Dec 20, 2022

Musigwa commented Dec 20, 2022 • edited Loading

BrandonMathis commented Jan 20, 2023

Maysfeak commented Feb 22, 2023

henrymoulton commented Apr 6, 2023 • edited Loading

henrymoulton commented Apr 6, 2023

dsokal commented Apr 7, 2023

henrymoulton commented Apr 7, 2023

moosthuizen42 commented Sep 5, 2023

widjesh commented Oct 7, 2022 •

edited

Loading

parniekovvakoms commented Oct 9, 2022 •

edited

Loading

ysrarff commented Oct 9, 2022 •

edited

Loading

Musigwa commented Dec 20, 2022 •

edited

Loading

henrymoulton commented Apr 6, 2023 •

edited

Loading