Compilation failed

Question
1

Could any friend help me understand where the error is?

AB version: 1.7.11
COMMAND:

ASSETS_ARCHIVE_URL=https://appgyver-meap-assets.s3.amazonaws.com/4lodn2ima7oy47ls0bldabcnstlx?response-content-disposition=attachment%3B%20filename%3D"assets.zip"%3B%20filename*%3DUTF-8''assets.zip&response-content-type=application%2Fzip&X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAJJSXXQRL4UNGBAXQ%2F20231010%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20231010T231611Z&X-Amz-Expires=604800&X-Amz-SignedHeaders=host&X-Amz-Signature=43264a584b40e8f29909a78ae75724f30168490796ff07b089c14a20a53df3b2 NODE_OPTIONS=–max-old-space-size=10240 npxrnv export -p android -s standalone -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @appgyver/orchestra-template-standalone@4.9.72 -r

FAILED with ERROR:

FAILURE: Build failed with an exception.

  • What went wrong:
    Unable to start the daemon process.
    This problem might be caused by incorrect configuration of the daemon.
    For example, an unrecognized jvm option is used.
    Please refer to the User Manual chapter on the daemon at The Gradle Daemon
    Process command line: /usr/lib/jvm/java-17-amazon-corretto.x86_64/bin/java -XX:MaxPermSize=2048m -XX:+HeapDumpOnOutOfMemoryError --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.lang.invoke=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED -Xmx6g -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp /home/ec2-user/.gradle/wrapper/dists/gradle-6.7.1-all/2moa8rlfac5eqlcfgk98k0deb/gradle-6.7.1/lib/gradle-launcher-6.7.1.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 6.7.1
    Please read the following process output to find out more:

Unrecognized VM option ‘MaxPermSize=2048m’
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

  • 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

Command failed with exit code 1: ./gradlew assembleRelease -x bundleReleaseJsAndAssets
Could not write standard input to Gradle build daemon.
java.io.IOException: Stream closed
at java.base/java.lang.ProcessBuilder$NullOutputStream.write(ProcessBuilder.java:445)
at java.base/java.io.OutputStream.write(OutputStream.java:162)
at java.base/java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:81)
at java.base/java.io.BufferedOutputStream.flush(BufferedOutputStream.java:142)
at org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:68)
at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:53)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
at java.base/java.lang.Thread.run(Thread.java:833)

FAILURE: Build failed with an exception.

  • What went wrong:
    Unable to start the daemon process.
    This problem might be caused by incorrect configuration of the daemon.
    For example, an unrecognized jvm option is used.
    Please refer to the User Manual chapter on the daemon at The Gradle Daemon
    Process command line: /usr/lib/jvm/java-17-amazon-corretto.x86_64/bin/java -XX:MaxPermSize=2048m -XX:+HeapDumpOnOutOfMemoryError --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.lang.invoke=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED -Xmx6g -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp /home/ec2-user/.gradle/wrapper/dists/gradle-6.7.1-all/2moa8rlfac5eqlcfgk98k0deb/gradle-6.7.1/lib/gradle-launcher-6.7.1.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 6.7.1
    Please read the following process output to find out more:

Unrecognized VM option ‘MaxPermSize=2048m’
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

  • 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
    Starting a Gradle Daemon (subsequent builds will be faster)

Could not write standard input to Gradle build daemon.
java.io.IOException: Stream closed
at java.base/java.lang.ProcessBuilder$NullOutputStream.write(ProcessBuilder.java:445)
at java.base/java.io.OutputStream.write(OutputStream.java:162)
at java.base/java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:81)
at java.base/java.io.BufferedOutputStream.flush(BufferedOutputStream.java:142)
at org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:68)
at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:53)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
at java.base/java.lang.Thread.run(Thread.java:833)

FAILURE: Build failed with an exception.

  • What went wrong:
    Unable to start the daemon process.
    This problem might be caused by incorrect configuration of the daemon.
    For example, an unrecognized jvm option is used.
    Please refer to the User Manual chapter on the daemon at The Gradle Daemon
    Process command line: /usr/lib/jvm/java-17-amazon-corretto.x86_64/bin/java -XX:MaxPermSize=2048m -XX:+HeapDumpOnOutOfMemoryError --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.lang.invoke=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED -Xmx6g -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp /home/ec2-user/.gradle/wrapper/dists/gradle-6.7.1-all/2moa8rlfac5eqlcfgk98k0deb/gradle-6.7.1/lib/gradle-launcher-6.7.1.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 6.7.1
    Please read the following process output to find out more:

Unrecognized VM option ‘MaxPermSize=2048m’
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

  • 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

Error: Command failed with exit code 1: ./gradlew assembleRelease -x bundleReleaseJsAndAssets
Could not write standard input to Gradle build daemon.
java.io.IOException: Stream closed
at java.base/java.lang.ProcessBuilder$NullOutputStream.write(ProcessBuilder.java:445)
at java.base/java.io.OutputStream.write(OutputStream.java:162)
at java.base/java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:81)
at java.base/java.io.BufferedOutputStream.flush(BufferedOutputStream.java:142)
at org.gradle.process.internal.streams.ExecOutputHandleRunner.forwardContent(ExecOutputHandleRunner.java:68)
at org.gradle.process.internal.streams.ExecOutputHandleRunner.run(ExecOutputHandleRunner.java:53)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:56)
at java.base/java.lang.Thread.run(Thread.java:833)

FAILURE: Build failed with an exception.

  • What went wrong:
    Unable to start the daemon process.
    This problem might be caused by incorrect configuration of the daemon.
    For example, an unrecognized jvm option is used.
    Please refer to the User Manual chapter on the daemon at The Gradle Daemon
    Process command line: /usr/lib/jvm/java-17-amazon-corretto.x86_64/bin/java -XX:MaxPermSize=2048m -XX:+HeapDumpOnOutOfMemoryError --add-opens java.base/java.util=ALL-UNNAMED --add-opens java.base/java.lang=ALL-UNNAMED --add-opens java.base/java.lang.invoke=ALL-UNNAMED --add-opens java.prefs/java.util.prefs=ALL-UNNAMED -Xmx6g -Dfile.encoding=UTF-8 -Duser.country -Duser.language=en -Duser.variant -cp /home/ec2-user/.gradle/wrapper/dists/gradle-6.7.1-all/2moa8rlfac5eqlcfgk98k0deb/gradle-6.7.1/lib/gradle-

launcher-6.7.1.jar org.gradle.launcher.daemon.bootstrap.GradleDaemon 6.7.1
Please read the following process output to find out more:

Unrecognized VM option ‘MaxPermSize=2048m’
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

  • 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
    Starting a Gradle Daemon (subsequent builds will be faster)
    at makeError (/home/ec2-user/builds/702103-android-301930/node_modules/execa/lib/error.js:60:11)
    at handlePromise (/home/ec2-user/builds/702103-android-301930/node_modules/execa/index.js:118:26)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)

2

The build error no longer has much relevance to the issue unless you get the same error 5 or more times. Just keep running it - its flakey as hell.

3

Getting the same error. Tried the following:

  1. Build my app with 4.6.36, 4.7.36, 4.7.37 and 4.9.72 multiple times.
  2. Started recreating my app on a new project and tried to build with 4.6.36, 4.7.36, 4.7.37 and
    4.9.72.
  3. Created another app with a navigation menu linking to all the other pages and tested with
    4.6.36, 4.7.36, 4.7.37 and 4.9.72.
  4. Opened a new project and without doing any work on the project I went straight to build the app. The project is completely untouched. Runtime versions 4.7.37, 4.7.36, and 4.6.36 all gave the same error.

Hope this helps the guys at Appgyver to resolve the problem.

4

Unrecognized VM option ‘MaxPermSize=2048m’
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.

6

Problem solved. Used the new Appgyver community edition. Built the .APK without any problems the first attempt. The new Appgyver community edition is AWESOME!

7

Como utilizar a nova versão?

8

Having the same issue (and I’ve never seen this issue before). I think the build service needs a kick.

9

Where do I find the new Appgyver community edition?

10

How to use the new version

11

Here is the announcement and instructions.

12

Good evening, hello my friends. I took my app to the new platform, and it still gave an error. This error below, could any friend help me resolve this?

O comando falhou com o código de saída 1: npx rnv export -p android -s standalone -c standalone --ci --yes --skipRnvCheck --packageManager yarn --template @appgyver/orchestra-template-standalone@4.9.84 -r

13

Is this error a problem with me or is it with the platform?

image
image460×644 12.9 KB

14

Good afternoon!
Were you able to integrate your app on the new platform?

15

I am getting the same error. At a loss on how to move past this error. Have you found a solution yet?

16

I am also getting the same error too.

17

@Sam_Engstrom Sam, can you provide any insight on this error many of us are receiving when trying to compile apps on the new platform.

18

Hi, anyone else facing issues while creatign account?
I haven’t received the verification email yet