[eas] - Unable build application with EAS build

Summary

I have an error when I build an android app on EAS build. My build ID is a276ca34-3dae-45c1-a34e-c6133f30fced.

> Task :react-native-community_netinfo:checkReleaseManifest
> Task :react-native-community_masked-view:processReleaseManifest
> Task :react-native-gesture-handler:checkReleaseManifest
> Task :react-native-community_netinfo:processReleaseManifest
> Task :react-native-maps:checkReleaseManifest
> Task :app:bundleReleaseJsAndAssets FAILED
                 Welcome to React Native!
                Learn once, write anywhere
Error: The resource `/build/workingdir/build/apps/xxxxxxxxxx/index.js` was not found.
    at /build/workingdir/build/node_modules/metro/src/IncrementalBundler.js:157:26
    at gotStat (fs.js:1864:21)
    at callback (/build/workingdir/build/node_modules/graceful-fs/polyfills.js:299:20)
    at FSReqCallback.oncomplete (fs.js:183:21)
> Task :react-native-gesture-handler:processReleaseManifest
> Task :react-native-maps:processReleaseManifest

TL/DR: Other issues when I migrate the project to EAS build

I trying to migrate the current project from SDKv40 to SDKv41 and use EAS build. Because My project is in a mono repo so it has a lot of problems when I build the project.

1. I have an issue with expo upgrade when ran it under apps/foo. Related to a bug of yarn, https://github.com/yarnpkg/yarn/issues/7807, so I have to downgrade yarn to version 1.18.0 with yarn policies set-version 1.18.0 to fix the issue.

2. My project uses some private packages hosting on Github Package Registry. So, I have to authenticate with packages. Put .npmrc in the project root doesn’t work. I have to ready instruction to find the way is adding an script eas-build-pre-install into my package.json for update ~/.npmrc. (The guide should help me do it faster).

{
    "eas-build-pre-install": "echo \"//npm.pkg.github.com/:_authToken=${NPM_TOKEN}\" >> ~/.npmrc"
}

1. My project in the workspace. Yeah, again. EAS complains about modules not found for expo-constant,… I checked the symlinks list at bare-expo but It not enough to resolve the issue. Finally, the list is below; a lot of modules have to symlinks:

{
  "expo-yarn-workspaces": {
    "symlinks": [
      "@unimodules/core",
      "@unimodules/react-native-adapter",
      "expo-camera",
      "expo-constants",
      "expo-splash-screen",
      "expo-structured-headers",
      "expo-updates",
      "unimodules-app-loader",
      "unimodules-barcode-scanner-interface",
      "unimodules-camera-interface",
      "unimodules-constants-interface",
      "unimodules-face-detector-interface",
      "unimodules-file-system-interface",
      "unimodules-font-interface",
      "unimodules-image-loader-interface",
      "unimodules-permissions-interface",
      "unimodules-sensors-interface",
      "unimodules-task-manager-interface"
    ]
  }
}

Managed or bare workflow? If you have ios/ or android/ directories in your project, the answer is bare!

managed

What platform(s) does this occur on?

Android

SDK Version (managed workflow only)

41.0.0

Environment

EAS BUILD

Reproducible demo or steps to reproduce from a blank project

none,

please DM me to get access my repo

[giautm]

Yeah, the first success build 7edb0b49-f66d-4ace-881f-f3fd1d271386

Just added a new secret. ENTRY_FILE. 😃))

[brentvatne]

we’re investigating a good fix for the index.js issue that you encountered. i’ll also update the documentation to clarify that support for monorepos with managed apps on eas build (wow that’s a lot of words) is still a bit rough