Error: Gradle build failed with unknown error after update to expo 48

Expo Application Services (EAS)
1

Hello,

I using managed workflow. my eas-cli is eas-cli/3.8.1 darwin-arm64 node-v16.15.1

I’ve just migrated my expo from 47 to 48 and now my build on EAS is failing for Android and env staging.
my eas.json contains:

    "development": {
      "channel": "development",
      "developmentClient": true,
      "distribution": "internal",
      "ios": {
        "simulator": false
      },
      "env": {
        "DEBUG": "true"
      }
    },
    "staging": {
      "channel": "staging",
      "distribution": "internal",
    }

All other build are working well: ios staging and development and android development. But my build for android staging is failing with following stack trace

......
> Task :expo-notifications:extractDeepLinksRelease
[stderr] 
Error: @build-script-error-begin
[stderr] 
Error loading application entry point. If your entry point is not index.js, please set ENTRY_FILE environment variable with your app entry point.
[stderr] 
@build-script-error-end
[stderr] 
    at /home/expo/workingdir/build/node_modules/expo-updates/scripts/createManifest.js:36:11
[stderr] 
    at Object.<anonymous> (/home/expo/workingdir/build/node_modules/expo-updates/scripts/createManifest.js:99:3)
[stderr] 
    at Module._compile (node:internal/modules/cjs/loader:1155:14)
[stderr] 
    at Object.Module._extensions..js (node:internal/modules/cjs/loader:1209:10)
[stderr] 
    at Module.load (node:internal/modules/cjs/loader:1033:32)
[stderr] 
    at Function.Module._load (node:internal/modules/cjs/loader:868:12)
[stderr] 
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
[stderr] 
    at node:internal/main/run_main_module:22:47
> Task :expo-notifications:processReleaseManifest
......
[stderr] 
FAILURE: Build completed with 2 failures.
[stderr] 
1: Task failed with an exception.
[stderr] 
-----------
[stderr] 
* What went wrong:
[stderr] 
Execution failed for task ':expo-updates:createReleaseExpoManifest'.
[stderr] 
> Process 'command 'node'' finished with non-zero exit value 1
[stderr] 
* Try:
[stderr] 
> Run with --stacktrace option to get the stack trace.
[stderr] 
> Run with --info or --debug option to get more log output.
[stderr] 
> Run with --scan to get full insights.
[stderr] 
==============================================================================
[stderr] 
2: Task failed with an exception.
[stderr] 
-----------
[stderr] 
* What went wrong:
[stderr] 
java.lang.StackOverflowError (no error message)
[stderr] 
* Try:
[stderr] 
> Run with --stacktrace option to get the stack trace.
[stderr] 
> Run with --info or --debug option to get more log output.
[stderr] 
> Run with --scan to get full insights.
[stderr] 
==============================================================================
[stderr] 
* Get more help at https://help.gradle.org
[stderr] 
BUILD FAILED in 5m 32s
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.
226 actionable tasks: 226 executed
Error: Gradle build failed with unknown error. See logs for the "Run gradlew" phase for more information.

here is a link to the build on EAS (Build Details — 77b761bd-4ecb-4ff9-954c-3e77bd386267 — basquiat-app — Expo)

Do you have an idea where the problem is?

2

After some investigation I found that for an unknown reason, the android build fails if I have not an index.js file. What is weird is that it works well for ios build and android dev client build. only the android build is failing if you don’t have the index.js file.

So I have I have put back an index.js file in my root folder and it works well. But I think it is a bug in the EAS build as it should be working to have another entry file as described here: