eas-cli: error: unknown command 'generate-modules-provider'. See ' --help'. EAS IOS Build Expo49

Build/Submit details page URL

No response

Summary

EAS build for IOS is failing with the following error: error: unknown command ‘generate-modules-provider’. See ’ --help’.

Expo SDK version: ^49.0.21 React Native Version: “0.72.6”

Failing at fastlane

Managed or bare?

Managed

Environment

eas build --platform ios

Error output

› Executing FrontlineMTApp » [Expo] Configure project

❌ error: unknown command ‘generate-modules-provider’. See ’ --help’.

Reproducible demo or steps to reproduce from a blank project

Build with Expo 49 for IOS and failing at fastlane

Using NPM to manage dependencies.

Only happening while using npm works fine with yarn

About this issue

Original URL
State: closed
Created 5 months ago
Reactions: 4
Comments: 19

Most upvoted comments

Fixed it, make sure to run npx expo-doctor and make sure to install comptaible version of expo-modules-autolinking i.e ~1.5.0 is installed on your project. @abranhe please confirm it works for your team as well and I will close the issue.

+14

kaushik1094 on Jan 30, 2024

@3madurya3 That makes sense. I am assuming updated version of expo-updates might be using an updated version of expo-modules-autolinking which might have the caused the issue. I think generate-modules-provider is the issue from expo-modules-autolinking I might be wrong though.

kaushik1094 on Apr 6, 2024

Fixed it, make sure to run npx expo-doctor and make sure to install comptaible version of expo-modules-autolinking i.e ~1.5.0 is installed on your project. @abranhe please confirm it works for your team as well and I will close the issue.

This was the issue I also faced. expo-modules-autolinking was at version 1.10.3, which is incompatible with expo SDK 49. I didn’t want to install the version ~1.5.0 manually because that could cause version incompatibilities and other unexpected issues. So in order to downgrade to ~1.5.0 I had to find the culprit which was forcing it to version 1.10.3. Running npm ls expo-modules-autolinking@1.10.3 (if using npm) really helped me out. It showed me that the culprit was eas-cli@^7.6.0, because it was evaluating to eas-cli@7.6.2. Downgrading the eas-cli version fixed the issue.

kapobajza on Apr 2, 2024

@abranhe not yet, My app is stuck at splashscreen with successful build using yarn. So it might be happening with yarn too

kaushik1094 on Jan 30, 2024

@evandrorocha It’s probably because build job is unable to find module “generate-modules-provider”.

@yokozawa0701 I am not ready to upgrade to expo 50 yet.

kaushik1094 on Jan 29, 2024