Skip to content
This repository has been archived by the owner on May 6, 2023. It is now read-only.

Android build arguments are different since Ren'py 7.4.9 #11

Open
SergioAlonsoJr opened this issue May 14, 2022 · 5 comments
Open

Android build arguments are different since Ren'py 7.4.9 #11

SergioAlonsoJr opened this issue May 14, 2022 · 5 comments

Comments

@SergioAlonsoJr
Copy link
Contributor

SergioAlonsoJr commented May 14, 2022

The Android build cli no longer uses the "assembleRelease" argument

Found this in renpy github android.py file

image

If you want to build Android App Bundle format, use the --bundle argument.
If you want to build Universal APK, remove the --bundle argument.

Ren'py 7.4.9 Change log

Still, there are other obstacles to solve, but this is one step ahead.

@kobaltcore
Copy link
Owner

Ah, good catch. I'll audit the last few versions for other changes and then I'll add a version guard to account for this change in API on Ren'Py's side.

kobaltcore added a commit that referenced this issue May 14, 2022
@SergioAlonsoJr
Copy link
Contributor Author

One extra update:

I had to make at least one android build using the interface before the command line would work correctly.
I think there are some configuration steps that are not being done by renconstruct.

@kobaltcore
Copy link
Owner

Can not confirm this at the moment, it's building android distributions fine on my end right now.
I'll take a deeper look tomorrow.

@SergioAlonsoJr
Copy link
Contributor Author

Can not confirm this at the moment, it's building android distributions fine on my end right now. I'll take a deeper look tomorrow.

I think the error I was facing was related to the Dropbox trying to sync the android temporary files.
I moved the build process outside of Dropbox and it seems to be working fine now.

@kobaltcore
Copy link
Owner

Yeah, file syncing stuff like that seems to quickly break down with file-heavy operations such as these (where Ren'Py creates thousands upon thousands of often-tiny files). I've seen issues related to that on most of these services, including OneDrive, iCloud, Dropbox and Google Drive, so it would be recommended to move at least the cache locations out of the purview of these programs, so that they have no chance to mess with the internal state.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants