I am facing the same issue

Did you able to find any work around?

Configuration on demand is an incubating feature.
:ReactNative:Running '[node, D:\SUMMER24\health\fitnessApp\node_modules\@react-native-community\cli\build\bin.js, config]' command failed.
FAILURE: Build failed with an exception.
* Where:
Script 'D:\SUMMER24\health\fitnessApp\node_modules\@react-native-community\cli-platform-android\native_modules.gradle' line: 401
* What went wrong:
A problem occurred evaluating script.
> 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.
> Get more help at https://help.gradle.org.
BUILD FAILED in 5s
5 actionable tasks: 4 executed, 1 from cache
Error: D:\SUMMER24\health\fitnessApp\android\gradlew.bat app:assembleDebug -x lint -x test --configure-on-demand --build-cache -PreactNativeDevServerPort=8081 -PreactNativeArchitectures=arm64-v8a,armeabi-v7a exited with non-zero code: 1                                                                                                                                                                                                                                    
Error: D:\SUMMER24\health\fitnessApp\android\gradlew.bat app:assembleDebug -x lint -x test --configure-on-demand --build-cache -PreactNativeDevServerPort=8081 -PreactNativeArchitectures=arm64-v8a,armeabi-v7a exited with non-zero code: 1
    at ChildProcess.completionListener (D:\SUMMER24\health\fitnessApp\node_modules\@expo\spawn-async\build\spawnAsync.js:42:23)
    at Object.onceWrapper (node:events:634:26)
    at ChildProcess.emit (node:events:519:28)
    at cp.emit (D:\SUMMER24\health\fitnessApp\node_modules\cross-spawn\lib\enoent.js:34:29)
    at maybeClose (node:internal/child_process:1105:16)
    at ChildProcess._handle.onexit (node:internal/child_process:305:5)
    at spawnAsync (D:\SUMMER24\health\fitnessApp\node_modules\@expo\spawn-async\build\spawnAsync.js:7:23)
    at spawnGradleAsync (D:\SUMMER24\health\fitnessApp\node_modules\@expo\cli\build\src\start\platforms\android\gradle.js:96:48)
    at assembleAsync (D:\SUMMER24\health\fitnessApp\node_modules\@expo\cli\build\src\start\platforms\android\gradle.js:74:18)
    at runAndroidAsync (D:\SUMMER24\health\fitnessApp\node_modules\@expo\cli\build\src\run\android\runAndroidAsync.js:45:37)
              
You topic is not even nearly similar.

He was getting an exception from some Gradle code in a react native component.

You are getting a failed node command.
You might need to ask the maintainer of that dependency what is going wrong.

This has not much to do with Gradle.

Maybe you can get more info when using --info or --scan.