Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Broken Android Exporter on Windows and Mac #1127

Open
sartsuk opened this issue Jul 1, 2024 · 0 comments
Open

Broken Android Exporter on Windows and Mac #1127

sartsuk opened this issue Jul 1, 2024 · 0 comments

Comments

@sartsuk
Copy link

sartsuk commented Jul 1, 2024

AGK Studio version Windows: v2024.06.09
AGK Studio version Mac: v2024.05.20

Hi,

Following various attempts, I have come to the conclusion AGK android export is broken seeing as I'm unable to export to .aab or .apk on any of the aforementioned platforms / versions. Please bear in mind export is not even possible with or without a keystore.

WINDOWS 10

I've downloaded the latest JDK version and also set the JAVA_HOME environmental variables as well as the path correctly (see below):

java -version
java version "22.0.1" 2024-04-16
Java(TM) SE Runtime Environment (build 22.0.1+8-16)
Java HotSpot(TM) 64-Bit Server VM (build 22.0.1+8-16, mixed mode, sharing)

Path
%JAVA_HOME%\bin

JAVA_HOME
C:\Program Files\Java\jdk-22

When I attempt to export .aab or .apk with no keystore file, it says:

Error: Failed to sign APK, is your keystore password and alias correct ? (error: jarsigner: unable to open jar file:

This is strange as the Keystore fields are blank, so why is it talking about a keystore ?

When I attempt to export with a keystore file (the one I've always used successfully in the past, it says):

Error: Failed to sign APK, is your keystore password and alias correct ? (error: jarsigner: unable to open jar file:

Well, it says the same thing.

I have meticulously checked all details on my end, and I'm confident this is an issue with ASK Studio.

MAC OS Sonoma 14.0

Error: AAPT2 return: Ready
Exiting daemon

Failed to write output files, check that your project directory is not in a write protected location

Just to put it simply...It isn't. It's been the same directory it has always been at.

These issues are a nightmare for me seeing as my app is in desperate need of an update, and the issue here is clearly a broken Android export.

Thanks

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

No branches or pull requests

1 participant