apksigner returned with error #2

Brah

I can't export game as apk without error. Console output : editor/project_export.cpp:863 - Failed to export the project for platform 'Android'. How to fix that?

Megalomaniak

This discussion was caught in the moderation queue since you have not confirmed your account yet.

Upon creating your account you should have received an account verification email. The confirmation email may have been incorrectly flagged as spam, so please also check your spam filter. Without confirming your account, future posts may also be caught in the moderation queue. You can resend a confirmation email when you log into your account if you cannot find the first verification email.

If you need any help, please let us know! You can find ways to contact forum staff on the Contact page. Thanks! :smile:

TwistedTwigleg

Welcome to the forums @Brah!

Are you getting any other errors? Looking at the code, there should be another error printed before that has a bit more detail on what exactly is going wrong. It should say either the export templates are missing, or that there is a configuration issue.

Maaack

I'm encountering the same error when exporting on Linux. I followed the instructions on Export for Android, specifically installed via command line tools and the sdkmanager. I tried generating signatures using both OpenJDK 11 and 8 (based on some older posts that suggested it). This error isn't helpful, and doesn't get any more specific even when I intentionally break something obvious like the user/password combo.

Do people have additional suggestions/experience on what to try next?

Maaack

In the output console, the immediately preceeding line reads:

ADDING: resources.arsc
 editor/project_export.cpp:863 - Failed to export the project for platform 'Android'.

duane

@Maaack said: I'm encountering the same error when exporting on Linux. Do people have additional suggestions/experience on what to try next?

The first thing to do is to run godot from your terminal window (command line). A lot more error information will show in the terminal output than you get in godot's console. If it doesn't immediately help, copy it out of the terminal window and post it.

Also, take a look at setting up the build system. I seem to recall that it includes some points that the export article misses.

Maaack

@duane said: The first thing to do is to run godot from your terminal window (command line). A lot more error information will show in the terminal output than you get in godot's console. If it doesn't immediately help, copy it out of the terminal window and post it. Really good suggestion. Unfortunately in this case, the only additional details I got were:

ADDING: resources.arsc
ERROR: Failed to export the project for platform 'Android'.
at: _export_project_to_path (editor/project_export.cpp:863)

Restarted my computer and regenerated the keys. No change. Checked out the linked article, tried setting the environment variable ANDROID_SDK_ROOT, and accepting all the licenses. I noticed though, each time I ran the sdkmanager it said none of the licenses were accepted. Then I remembered to sudo ./sdkmanager when signing them. Regenerated all of my keys. Restarted Godot. Still the same error :disappointed:

Thought that was going to be it. Thanks for the suggestions, though! I expect that was still progress, even if the error didn't change.

cybereality

Follow the instructions here. I just did them a few weeks ago they work. However, you need very specific versions of each SDK. If you install the wrong one, it won't work. You might want to uninstall the Android stuff and try again fresh.

https://docs.godotengine.org/en/stable/tutorials/export/exporting_for_android.html

duane

When I look at the source

it looks like you've got no path in "Export path", or a path that makes no sense to godot. What export path are you specifying?

Edit: Never mind, I was looking at a different branch of code. The error that you're getting is a lot more generic.

Maaack

@cybereality said: Follow the instructions here. I just did them a few weeks ago they work. However, you need very specific versions of each SDK. If you install the wrong one, it won't work. You might want to uninstall the Android stuff and try again fresh.

https://docs.godotengine.org/en/stable/tutorials/export/exporting_for_android.html

I was debating calling you out specifically as I know you released Myra for Android not long ago. Those are the instructions I followed, though. I've done a fresh install of my android-sdk folder twice with: ./sdkmanager --sdk_root=$ANDROID_SDK_ROOT "platform-tools" "build-tools;30.0.3" "platforms;android-29" "cmdline-tools;latest" "cmake;3.10.2.4988404" "ndk;21.4.7075529" The versions of the packages match with what the documentation says... :confused:

duane

Here's another post I made on simple things to check. One thing that can trip you up is adding the environment variables to ".bash_profile" without relogging, but you already did that. You might also double-check permissions on the sdk and ndk directories.

cybereality

Well, if they SDK was not setup properly, the error window would clearly state the issue (such as unable to find adb or something like that). Have you tested on an actually Android device from the editor? If you can click the Android icon next to the play button with your phone plugged in, then the SDK is working. If that works, then it is most likely an OS level issue. For example if they folder you are writing to doesn't have proper permissions or otherwise some sort of config issue. I would try exporting to a different filename (try something simple like "test.apk") and save it into a folder in your home directory like Documents, that way you know the permissions should be correct. Report back to see if any of that helps.

Maaack

Got it! My issue seems tied to using special characters (either $ or @) in my password for the keystore. Regenerated keystores without those characters and was able to sign the package. Then regenerated the keystores with those characters again, just to be sure they were the culprit, and sure enough, got the error to come back.

Part of it may still have been signing the licenses. Additionally, I noticed on Setting up the buildsystem, they install with tools/bin/sdkmanager --sdk_root=<android_sdk_path> "platform-tools" "build-tools;30.0.3" "platforms;android-29" "cmdline-tools;latest" "cmake;3.10.2.4988404" -- but they omit the inclusion of "ndk;21.4.7075529", as is used in Download the Android SDK. That may have tripped me up a little.

So I guess I won't be using special characters in my keystore passwords...

Maaack

Thanks @duane and @cybereality for your help!

duane

@Maaack said: Got it! My issue seems tied to using special characters (either $ or @) in my password for the keystore.

I never would have guessed that. :)

cybereality

I wouldn't have guessed that, but it makes sense.

Maaack

@duane said: I never would have guessed that. :)

I more stumbled into it while trying other solutions. :tongue:

@cybereality said: I wouldn't have guessed that, but it makes sense.

Does it, though?

cybereality

Well the password itself should be hashed, so it shouldn't matter what's in it. But if you generate the password using the command line, some of those characters may be reserved. For example $ is usually used for expanding environmental variables.

Maaack

@cybereality said: But if you generate the password using the command line, some of those characters may be reserved. For example $ is usually used for expanding environmental variables.

I concede. That does make some sense :sweat_smile:

I make no promises that I'll narrow down the bug further, but I recognize the opportunity.