`Task :expo-updates:createDebugExpoManifest FAILED` on Expo v47 yarn workspace after `expo run:android`
See original GitHub issueSummary
It’s not clear what the actual error here is, although I think it’s this bit: Error loading application entry point. If your entry point is not index.js, please set ENTRY_FILE environment variable with your app entry point.
I am using index.js
for my main
after following this: https://docs.expo.dev/guides/monorepos/.
> Task :expo-updates:createDebugExpoManifest FAILED
Execution optimizations have been disabled for task ':expo-updates:createDebugExpoManifest' to ensure correctness due to the following reasons:
- Gradle detected a problem with the following location: '/Users/gsquare567/Sites/blogcast/mobile/android'. Reason: Task ':expo-updates:createDebugExpoManifest' uses this output of task ':app:compileDebugAidl' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
- Gradle detected a problem with the following location: '/Users/gsquare567/Sites/blogcast/mobile/android'. Reason: Task ':expo-updates:createDebugExpoManifest' uses this output of task ':app:compileDebugRenderscript' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
- Gradle detected a problem with the following location: '/Users/gsquare567/Sites/blogcast/mobile/android'. Reason: Task ':expo-updates:createDebugExpoManifest' uses this output of task ':app:compileDebugShaders' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
- Gradle detected a problem with the following location: '/Users/gsquare567/Sites/blogcast/mobile/android'. Reason: Task ':expo-updates:createDebugExpoManifest' uses this output of task ':app:generateDebugBuildConfig' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
- Gradle detected a problem with the following location: '/Users/gsquare567/Sites/blogcast/mobile/android'. Reason: Task ':expo-updates:createDebugExpoManifest' uses this output of task ':app:generateDebugResValues' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
- Gradle detected a problem with the following location: '/Users/gsquare567/Sites/blogcast/mobile/android'. Reason: Task ':expo-updates:createDebugExpoManifest' uses this output of task ':app:javaPreCompileDebug' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
- Gradle detected a problem with the following location: '/Users/gsquare567/Sites/blogcast/mobile/android'. Reason: Task ':expo-updates:createDebugExpoManifest' uses this output of task ':app:mergeDebugAssets' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
- Gradle detected a problem with the following location: '/Users/gsquare567/Sites/blogcast/mobile/android'. Reason: Task ':expo-updates:createDebugExpoManifest' uses this output of task ':app:mergeDebugNativeDebugMetadata' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
- Gradle detected a problem with the following location: '/Users/gsquare567/Sites/blogcast/mobile/android'. Reason: Task ':expo-updates:createDebugExpoManifest' uses this output of task ':app:mergeDebugShaders' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Error: @build-script-error-begin
Error loading application entry point. If your entry point is not index.js, please set ENTRY_FILE environment variable with your app entry point.
@build-script-error-end
at /Users/gsquare567/Sites/blogcast/node_modules/expo-updates/scripts/createManifest.js:36:11
at Object.<anonymous> (/Users/gsquare567/Sites/blogcast/node_modules/expo-updates/scripts/createManifest.js:99:3)
at Module._compile (node:internal/modules/cjs/loader:1155:14)
at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
at Module.load (node:internal/modules/cjs/loader:1033:32)
at Function.Module._load (node:internal/modules/cjs/loader:868:12)
at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
at node:internal/main/run_main_module:22:47
FAILURE: Build completed with 2 failures.
1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':expo-updates:createDebugExpoManifest'.
> Process 'command 'node'' finished with non-zero exit value 1
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================
2: Task failed with an exception.
-----------
* What went wrong:
java.lang.StackOverflowError (no error message)
* Try:
> Run with --stacktrace option to get the stack trace.
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.
==============================================================================
* Get more help at https://help.gradle.org
Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
See https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings
Execution optimizations have been disabled for 2 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.
BUILD FAILED in 56s
129 actionable tasks: 14 executed, 110 from cache, 5 up-to-date
Error: /Users/gsquare567/Sites/blogcast/mobile/android/gradlew exited with non-zero code: 1
What platform(s) does this occur on?
Android
SDK Version
47.0.6
Environment
> npx expo-env-info
npm WARN ignoring workspace config at /Users/gsquare567/Sites/blogcast/mobile/.npmrc
expo-env-info 1.0.5 environment info:
System:
OS: macOS 12.4
Shell: 3.0.2 - /usr/local/bin/fish
Binaries:
Node: 16.18.1 - /usr/local/bin/node
Yarn: 1.22.5 - ~/.yarn/bin/yarn
npm: 8.19.2 - /usr/local/bin/npm
Managers:
CocoaPods: 1.11.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.5, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK:
API Levels: 30, 31, 32, 33
Build Tools: 29.0.2, 30.0.2, 30.0.3, 31.0.0, 33.0.0
System Images: android-30 | Google Play Intel x86 Atom, android-33 | Google APIs Intel x86 Atom_64
IDEs:
Android Studio: 2021.3 AI-213.7172.25.2113.9123335
Xcode: 13.4.1/13F100 - /usr/bin/xcodebuild
Expo Workflow: bare
Minimal reproducible example
- Create bare monorepo Expo v47 project
expo run:android
Issue Analytics
- State:
- Created 10 months ago
- Reactions:2
- Comments:6 (2 by maintainers)
Top Results From Across the Web
react native expo - Execution failed for task
Everything worked fine, build successfully, but when I execute the command eas build -p android --profile preview , it crashes/build-fails after ...
Read more >Testing expo sdk 39 but failed on expo-yarn-workspaces
I'm trying to build sdk-39 from expo, but failed because of expo-yarn-workspaces with following error. I'm using windows 8.1. Any advice please, ...
Read more >yarn workspaces
Show information about your workspaces. ... yarn workspaces info [--json]. This command will display the workspace dependency tree of your current project.
Read more >expo-yarn-workspaces - npm
A private package for working with Yarn workspaces within the Expo repository. Latest version: 2.0.4, last published: 2 months ago.
Read more >Speed up your Yarn Workspace with Nx | by Emily Xiong
If you have a Yarn workspace, you can turn it into an Nx monorepo with a simple command. Below is an example of...
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
Also happening to me, same platform (“Android”)
will reopen if this persists but as far as we can tell this solves the issue