android build fail
Forum rules
This is the right place for Ren'Py help. Please ask one question per thread, use a descriptive subject like 'NotFound error in option.rpy' , and include all the relevant information - especially any relevant code and traceback messages. Use the code tag to format scripts.
This is the right place for Ren'Py help. Please ask one question per thread, use a descriptive subject like 'NotFound error in option.rpy' , and include all the relevant information - especially any relevant code and traceback messages. Use the code tag to format scripts.
-
Darksoul1978
- Newbie
- Posts: 5
- Joined: Fri Mar 13, 2020 5:58 am
- Contact:
android build fail
I made a project and built the first version just fine. Now when I try to build the updated 2nd version for android I keep getting a failure. this is the text I get:
Ren’Py 7.3.5.606
Updating project.
Creating assets directory.
Packaging internal data.
I’m using Gradle to build the package.
Starting a Gradle Daemon, 3 stopped Daemons could not be reused, use --status for details
:app:preBuild UP-TO-DATE
:renpyandroid:preBuild UP-TO-DATE
:renpyandroid:preReleaseBuild UP-TO-DATE
:renpyandroid:checkReleaseManifest UP-TO-DATE
:renpyandroid:processReleaseManifest UP-TO-DATE
:app:preReleaseBuild UP-TO-DATE
:renpyandroid:compileReleaseAidl UP-TO-DATE
:app:compileReleaseAidl UP-TO-DATE
:renpyandroid:packageReleaseRenderscript NO-SOURCE
:app:compileReleaseRenderscript UP-TO-DATE
:app:checkReleaseManifest UP-TO-DATE
:app:generateReleaseBuildConfig UP-TO-DATE
:app:prepareLintJar UP-TO-DATE
:app:mainApkListPersistenceRelease UP-TO-DATE
:app:generateReleaseResValues UP-TO-DATE
:app:generateReleaseResources UP-TO-DATE
:renpyandroid:compileReleaseRenderscript UP-TO-DATE
:renpyandroid:generateReleaseResValues UP-TO-DATE
:renpyandroid:generateReleaseResources UP-TO-DATE
:renpyandroid:packageReleaseResources UP-TO-DATE
:app:mergeReleaseResources
:app:createReleaseCompatibleScreenManifests UP-TO-DATE
:app:processReleaseManifest UP-TO-DATE
:app:splitsDiscoveryTaskRelease UP-TO-DATE
:renpyandroid:platformAttrExtractor UP-TO-DATE
:renpyandroid:generateReleaseRFile UP-TO-DATE
:app:processReleaseResources
:app:generateReleaseSources
:renpyandroid:generateReleaseBuildConfig UP-TO-DATE
:renpyandroid:prepareLintJar UP-TO-DATE
:renpyandroid:generateReleaseSources UP-TO-DATE
:renpyandroid:javaPreCompileRelease UP-TO-DATE
:renpyandroid:compileReleaseJavaWithJavac UP-TO-DATE
:renpyandroid:processReleaseJavaRes NO-SOURCE
:renpyandroid:transformClassesAndResourcesWithPrepareIntermediateJarsForRelease UP-TO-DATE
:app:javaPreCompileRelease UP-TO-DATE
:app:compileReleaseJavaWithJavac UP-TO-DATE
:app:compileReleaseNdk NO-SOURCE
:app:compileReleaseSources UP-TO-DATE
:app:lintVitalRelease
:app:mergeReleaseShaders UP-TO-DATE
:app:compileReleaseShaders UP-TO-DATE
:app:generateReleaseAssets UP-TO-DATE
:renpyandroid:mergeReleaseShaders UP-TO-DATE
:renpyandroid:compileReleaseShaders UP-TO-DATE
:renpyandroid:generateReleaseAssets UP-TO-DATE
:renpyandroid:packageReleaseAssets UP-TO-DATE
:app:mergeReleaseAssets
:app:transformClassesWithDexBuilderForRelease UP-TO-DATE
:app:transformDexArchiveWithExternalLibsDexMergerForRelease UP-TO-DATE
:app:transformDexArchiveWithDexMergerForRelease UP-TO-DATE
:app:mergeReleaseJniLibFolders UP-TO-DATE
:renpyandroid:compileReleaseNdk NO-SOURCE
:renpyandroid:mergeReleaseJniLibFolders UP-TO-DATE
:renpyandroid:transformNativeLibsWithMergeJniLibsForRelease UP-TO-DATE
:renpyandroid:transformNativeLibsWithIntermediateJniLibsForRelease UP-TO-DATE
:app:transformNativeLibsWithMergeJniLibsForRelease UP-TO-DATE
:app:processReleaseJavaRes NO-SOURCE
:app:transformResourcesWithMergeJavaResForRelease UP-TO-DATE
:app:validateSigningRelease UP-TO-DATE
:app:packageRelease
Expiring Daemon because JVM Tenured space is exhausted
Daemon will be stopped at the end of the build after running out of JVM memory
FAILURE: Build failed with an exception.
What went wrong:
Gradle build daemon has been stopped: JVM garbage collector thrashing and after running out of JVM memory
Try:
Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Exception is:
org.gradle.launcher.daemon.server.api.DaemonStoppedException: Gradle build daemon has been stopped: JVM garbage collector thrashing and after running out of JVM memory
at org.gradle.launcher.daemon.server.DaemonStateCoordinator.waitForCommandCompletion(DaemonStateCoordinator.java:327)
at org.gradle.launcher.daemon.server.DaemonStateCoordinator.runCommand(DaemonStateCoordinator.java:302)
at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy.doBuild(StartBuildOrRespondWithBusy.java:54)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
at org.gradle.launcher.daemon.server.exec.ReturnResult.execute(ReturnResult.java:36)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
at org.gradle.launcher.daemon.server.api.HandleReportStatus.execute(HandleReportStatus.java:33)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
at org.gradle.launcher.daemon.server.exec.HandleCancel.execute(HandleCancel.java:37)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
at org.gradle.launcher.daemon.server.api.HandleStop.execute(HandleStop.java:45)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecuter.executeCommand(DaemonCommandExecuter.java:48)
at org.gradle.launcher.daemon.server.DefaultIncomingConnectionHandler$ConnectionWorker.handleCommand(DefaultIncomingConnectionHandler.java:160)
at org.gradle.launcher.daemon.server.DefaultIncomingConnectionHandler$ConnectionWorker.receiveAndHandleCommand(DefaultIncomingConnectionHandler.java:133)
at org.gradle.launcher.daemon.server.DefaultIncomingConnectionHandler$ConnectionWorker.run(DefaultIncomingConnectionHandler.java:121)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
at java.lang.Thread.run(Thread.java:748)
Get more help at https://help.gradle.org
The build seems to have failed.
Ren’Py 7.3.5.606
Updating project.
Creating assets directory.
Packaging internal data.
I’m using Gradle to build the package.
Starting a Gradle Daemon, 3 stopped Daemons could not be reused, use --status for details
:app:preBuild UP-TO-DATE
:renpyandroid:preBuild UP-TO-DATE
:renpyandroid:preReleaseBuild UP-TO-DATE
:renpyandroid:checkReleaseManifest UP-TO-DATE
:renpyandroid:processReleaseManifest UP-TO-DATE
:app:preReleaseBuild UP-TO-DATE
:renpyandroid:compileReleaseAidl UP-TO-DATE
:app:compileReleaseAidl UP-TO-DATE
:renpyandroid:packageReleaseRenderscript NO-SOURCE
:app:compileReleaseRenderscript UP-TO-DATE
:app:checkReleaseManifest UP-TO-DATE
:app:generateReleaseBuildConfig UP-TO-DATE
:app:prepareLintJar UP-TO-DATE
:app:mainApkListPersistenceRelease UP-TO-DATE
:app:generateReleaseResValues UP-TO-DATE
:app:generateReleaseResources UP-TO-DATE
:renpyandroid:compileReleaseRenderscript UP-TO-DATE
:renpyandroid:generateReleaseResValues UP-TO-DATE
:renpyandroid:generateReleaseResources UP-TO-DATE
:renpyandroid:packageReleaseResources UP-TO-DATE
:app:mergeReleaseResources
:app:createReleaseCompatibleScreenManifests UP-TO-DATE
:app:processReleaseManifest UP-TO-DATE
:app:splitsDiscoveryTaskRelease UP-TO-DATE
:renpyandroid:platformAttrExtractor UP-TO-DATE
:renpyandroid:generateReleaseRFile UP-TO-DATE
:app:processReleaseResources
:app:generateReleaseSources
:renpyandroid:generateReleaseBuildConfig UP-TO-DATE
:renpyandroid:prepareLintJar UP-TO-DATE
:renpyandroid:generateReleaseSources UP-TO-DATE
:renpyandroid:javaPreCompileRelease UP-TO-DATE
:renpyandroid:compileReleaseJavaWithJavac UP-TO-DATE
:renpyandroid:processReleaseJavaRes NO-SOURCE
:renpyandroid:transformClassesAndResourcesWithPrepareIntermediateJarsForRelease UP-TO-DATE
:app:javaPreCompileRelease UP-TO-DATE
:app:compileReleaseJavaWithJavac UP-TO-DATE
:app:compileReleaseNdk NO-SOURCE
:app:compileReleaseSources UP-TO-DATE
:app:lintVitalRelease
:app:mergeReleaseShaders UP-TO-DATE
:app:compileReleaseShaders UP-TO-DATE
:app:generateReleaseAssets UP-TO-DATE
:renpyandroid:mergeReleaseShaders UP-TO-DATE
:renpyandroid:compileReleaseShaders UP-TO-DATE
:renpyandroid:generateReleaseAssets UP-TO-DATE
:renpyandroid:packageReleaseAssets UP-TO-DATE
:app:mergeReleaseAssets
:app:transformClassesWithDexBuilderForRelease UP-TO-DATE
:app:transformDexArchiveWithExternalLibsDexMergerForRelease UP-TO-DATE
:app:transformDexArchiveWithDexMergerForRelease UP-TO-DATE
:app:mergeReleaseJniLibFolders UP-TO-DATE
:renpyandroid:compileReleaseNdk NO-SOURCE
:renpyandroid:mergeReleaseJniLibFolders UP-TO-DATE
:renpyandroid:transformNativeLibsWithMergeJniLibsForRelease UP-TO-DATE
:renpyandroid:transformNativeLibsWithIntermediateJniLibsForRelease UP-TO-DATE
:app:transformNativeLibsWithMergeJniLibsForRelease UP-TO-DATE
:app:processReleaseJavaRes NO-SOURCE
:app:transformResourcesWithMergeJavaResForRelease UP-TO-DATE
:app:validateSigningRelease UP-TO-DATE
:app:packageRelease
Expiring Daemon because JVM Tenured space is exhausted
Daemon will be stopped at the end of the build after running out of JVM memory
FAILURE: Build failed with an exception.
What went wrong:
Gradle build daemon has been stopped: JVM garbage collector thrashing and after running out of JVM memory
Try:
Run with --info or --debug option to get more log output. Run with --scan to get full insights.
Exception is:
org.gradle.launcher.daemon.server.api.DaemonStoppedException: Gradle build daemon has been stopped: JVM garbage collector thrashing and after running out of JVM memory
at org.gradle.launcher.daemon.server.DaemonStateCoordinator.waitForCommandCompletion(DaemonStateCoordinator.java:327)
at org.gradle.launcher.daemon.server.DaemonStateCoordinator.runCommand(DaemonStateCoordinator.java:302)
at org.gradle.launcher.daemon.server.exec.StartBuildOrRespondWithBusy.doBuild(StartBuildOrRespondWithBusy.java:54)
at org.gradle.launcher.daemon.server.exec.BuildCommandOnly.execute(BuildCommandOnly.java:36)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
at org.gradle.launcher.daemon.server.exec.ReturnResult.execute(ReturnResult.java:36)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
at org.gradle.launcher.daemon.server.api.HandleReportStatus.execute(HandleReportStatus.java:33)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
at org.gradle.launcher.daemon.server.exec.HandleCancel.execute(HandleCancel.java:37)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
at org.gradle.launcher.daemon.server.api.HandleStop.execute(HandleStop.java:45)
at org.gradle.launcher.daemon.server.api.DaemonCommandExecution.proceed(DaemonCommandExecution.java:122)
at org.gradle.launcher.daemon.server.exec.DaemonCommandExecuter.executeCommand(DaemonCommandExecuter.java:48)
at org.gradle.launcher.daemon.server.DefaultIncomingConnectionHandler$ConnectionWorker.handleCommand(DefaultIncomingConnectionHandler.java:160)
at org.gradle.launcher.daemon.server.DefaultIncomingConnectionHandler$ConnectionWorker.receiveAndHandleCommand(DefaultIncomingConnectionHandler.java:133)
at org.gradle.launcher.daemon.server.DefaultIncomingConnectionHandler$ConnectionWorker.run(DefaultIncomingConnectionHandler.java:121)
at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:63)
at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:46)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at org.gradle.internal.concurrent.ThreadFactoryImpl$ManagedThreadRunnable.run(ThreadFactoryImpl.java:55)
at java.lang.Thread.run(Thread.java:748)
Get more help at https://help.gradle.org
The build seems to have failed.
Re: android build fail
Increase the amount of memory you are giving the build process in gradle.settings
Re: android build fail
Location
renpy-7.2.2-sdk\rapt\project
renpy-7.2.2-sdk\rapt\prototype
You need file
gradle.properties
Change this on bigger one, this mine
org.gradle.jvmargs=-Xmx9g
(original 3g, I think)
renpy-7.2.2-sdk\rapt\project
renpy-7.2.2-sdk\rapt\prototype
You need file
gradle.properties
Change this on bigger one, this mine
org.gradle.jvmargs=-Xmx9g
(original 3g, I think)
- Andredron
- Miko-Class Veteran
- Posts: 535
- Joined: Thu Dec 28, 2017 2:37 pm
- Completed: Kimi ga nozomu renpy-port(demo), Albatross Koukairoku(demo)
- Projects: Sisters ~Natsu no Saigo no Hi~(renpy-port)
- Location: Russia
- Contact:
Re: android build fail
The question, is on top they wrote how to change what in the file, but what does it give? For example, the project weighs 6GB, I need to change chtoli from 3g to 6g, tell me what kind of animal it is - gradle?
I'm writing a Renpy textbook (in Russian). https://disk.yandex.ru/i/httNEajU7iFWHA (all information is out of date) Update 22.06.18
Help me to register in QQ International
Honest Critique
Help me to register in QQ International
Honest Critique
Re: android build fail
Gradle is a program (or, perhaps, a system) that can be used to build other software. It’s used a lot in the Java community. (Android is Java-based, and the default way to build Android programs is to use Gradle and a set of related tools that were installed when you set up the Android SDK). So, to make an Android build, what the Ren’py program does is to automatically build a Gradle project and then execute it.
What was happening was that the default configuration didn’t give the Gradle program enough memory to do what it needed to do to build your Android project. The setting you changed doesn’t affect the final Ren’py Android build in any way - it just allows Gradle to use more memory while it’s in the process of doing the build.
What was happening was that the default configuration didn’t give the Gradle program enough memory to do what it needed to do to build your Android project. The setting you changed doesn’t affect the final Ren’py Android build in any way - it just allows Gradle to use more memory while it’s in the process of doing the build.
- Andredron
- Miko-Class Veteran
- Posts: 535
- Joined: Thu Dec 28, 2017 2:37 pm
- Completed: Kimi ga nozomu renpy-port(demo), Albatross Koukairoku(demo)
- Projects: Sisters ~Natsu no Saigo no Hi~(renpy-port)
- Location: Russia
- Contact:
Re: android build fail
ok, thankrames44 wrote: ↑Sat Mar 14, 2020 12:30 pmGradle is a program (or, perhaps, a system) that can be used to build other software. It’s used a lot in the Java community. (Android is Java-based, and the default way to build Android programs is to use Gradle and a set of related tools that were installed when you set up the Android SDK). So, to make an Android build, what the Ren’py program does is to automatically build a Gradle project and then execute it.
What was happening was that the default configuration didn’t give the Gradle program enough memory to do what it needed to do to build your Android project. The setting you changed doesn’t affect the final Ren’py Android build in any way - it just allows Gradle to use more memory while it’s in the process of doing the build.
I'm writing a Renpy textbook (in Russian). https://disk.yandex.ru/i/httNEajU7iFWHA (all information is out of date) Update 22.06.18
Help me to register in QQ International
Honest Critique
Help me to register in QQ International
Honest Critique
Who is online
Users browsing this forum: span4ev