Ошибка 127 андроид

Still the same. I’ll try to reinstall Android Studio (since I have a somewhat old version).

EDIT: Nothing, did a fresh install of Android studio, same error.

OK, I’m retarded, forgot to generate a new keystore (the old one will not work). Feel free to close.

Maybe we should document that if apksigner adds new requirements on the debug keystone @m4gr3d.

The error about needing a valid Android SDK path when there’s one is also weird.

No need, the Android SDK error was a mistaken on my part. Since the log screen doesn’t get cleared wen you make a new export, that was the old error wen I didn’t had it configured.

Everything seems to work OK. Tho it would be nice to comment in the docs that old keystores will not work and you need to generate a new one, and also a more intuitive error message (couldn’t find any info on Google about ‘apksigner error 127’).

ADDING: lib/armeabi-v7a/libc++_shared.so
ADDING: res/mipmap-xhdpi-v4/icon.png
ADDING: res/layout/notification_template_media.xml
ADDING: res/drawable-hdpi-v4/notification_bg_low_pressed.9.png
ADDING: res/layout/notification_template_big_media_narrow.xml
ADDING: res/drawable-hdpi-v4/notification_bg_normal.9.png
ADDING: classes.dex
ADDING: lib/armeabi-v7a/libgodot_android.so
Exception in thread «main» java.lang.OutOfMemoryError
at sun.misc.Unsafe.allocateMemory(Native Method)
at java.nio.DirectByteBuffer.(DirectByteBuffer.java:127)
at java.nio.ByteBuffer.allocateDirect(ByteBuffer.java:311)
at com.android.apksig.internal.util.RandomAccessFileDataSource.feed(RandomAccessFileDataSource.java:106)
at com.android.apksig.internal.apk.ApkSigningBlockUtils$ChunkDigester.run(ApkSigningBlockUtils.java:637)
at com.android.apksig.util.RunnablesExecutor.lambda$static$0(RunnablesExecutor.java:20)
at com.android.apksig.internal.apk.ApkSigningBlockUtils.computeOneMbChunkContentDigests(ApkSigningBlockUtils.java:559)
at com.android.apksig.internal.apk.ApkSigningBlockUtils.computeContentDigests(ApkSigningBlockUtils.java:422)
at com.android.apksig.internal.apk.ApkSigningBlockUtils.computeContentDigests(ApkSigningBlockUtils.java:1035)
at com.android.apksig.internal.apk.v2.V2SchemeSigner.generateApkSignatureSchemeV2Block(V2SchemeSigner.java:152)
at com.android.apksig.DefaultApkSignerEngine.outputZipSectionsInternal(DefaultApkSignerEngine.java:786)
at com.android.apksig.DefaultApkSignerEngine.outputZipSections2(DefaultApkSignerEngine.java:752)
at com.android.apksig.ApkSigner.sign(ApkSigner.java:543)
at com.android.apksig.ApkSigner.sign(ApkSigner.java:193)
at com.android.apksigner.ApkSignerTool.sign(ApkSignerTool.java:340)
at com.android.apksigner.ApkSignerTool.main(ApkSignerTool.java:83)

‘apksigner’ returned with error #1
‘apksigner’ returned with error #1
‘apksigner’ returned with error #1
‘apksigner’ returned with error #1

Godot version:

3.2.4-beta6

OS/device including version:
win10

Issue description:

I don’t know why I tried almost everything, but I couldn’t solve this problem. I also regenerated the keystore

@cjmxp The error is Exception in thread "main" java.lang.OutOfMemoryError, it sounds like you are running out of RAM. How much RAM do you have on that system? Can you monitor its usage while exporting the APK to see if it reaches 100% and eventually fails?

@akien-mga 3.2.4-beta 4 can be exported. My memory is 16g to use 30%

Could you open a new issue for this OutOfMemoryError? It’s also related to the switch to apksigner but it’s unrelated to @Janders1800’s issue, so we should treat it separately.

The apksigner parameter should modify the memory size of the JVM

@akien-mga

Is it possible to reopen it ? because, I still have same issue on godot 3.3 RC8. (https://downloads.tuxfamily.org/godotengine/3.3/rc8/).
When I try to export for android, getting the error message below:
‘apksigner’ returned with error #127

but in 3.2.3 stable release, exports perfectly fine.

OS : Ubuntu 18.04
Build target : oculus quest 2 (Android)

@tqm-dev Can you enable verbose stdout in your project settings. That should provide more information about why the signing step is failing.
Also, can you try building your apk after enabling custom build and let us know if that succeeds.

@m4gr3d
I have got some messages on log window:

Starting signing of the APK binary using /home/tqm-dev/Android/sdk/build-tools/30.0.1/apksigner
Signing debug binary using:
/home/tqm-dev/Android/sdk/build-tools/30.0.1/apksigner sign —verbose —ks /home/tqm-dev/.android/debug.keystore —ks-pass pass:android —ks-key-alias androiddebugkey /home/tqm-dev/.cache/godot/tmpexport.apk

but I could not get additional error messages.
I think that Oculus quest need v2 scheme for signing but it is not v2 explicitly.

@tqm-dev Could you try to run the last command in a terminal window and see what happens (you may need to check that the tmpexport.apk file is still there first):

/home/tqm-dev/Android/sdk/build-tools/30.0.1/apksigner sign --verbose --ks /home/tqm-dev/.android/debug.keystore --ks-pass pass:android --ks-key-alias androiddebugkey /home/tqm-dev/.cache/godot/tmpexport.apk

@tqm-dev In addition can you enable custom build in your Android export settings and try building and signing your apk again.

@tqm-dev Could you try to run the last command in a terminal window and see what happens (you may need to check that the tmpexport.apk file is still there first):

/home/tqm-dev/Android/sdk/build-tools/30.0.1/apksigner sign --verbose --ks /home/tqm-dev/.android/debug.keystore --ks-pass pass:android --ks-key-alias androiddebugkey /home/tqm-dev/.cache/godot/tmpexport.apk

I got the error message below:

Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=com/android/apksigner/ApkSignerTool, offset=6
	at java.lang.ClassLoader.defineClassImpl(Native Method)
	at java.lang.ClassLoader.defineClassInternal(ClassLoader.java:398)
	at java.lang.ClassLoader.defineClass(ClassLoader.java:359)
	at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
	at java.net.URLClassLoader.defineClass(URLClassLoader.java:682)
	at java.net.URLClassLoader.access$400(URLClassLoader.java:89)
	at java.net.URLClassLoader$ClassFinder.run(URLClassLoader.java:1086)
	at java.security.AccessController.doPrivileged(AccessController.java:774)
	at java.net.URLClassLoader.findClass(URLClassLoader.java:589)
	at java.lang.ClassLoader.loadClassHelper(ClassLoader.java:953)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:898)
	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:352)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:881)
	at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:601)

I seems that java would not be found but
$ java -version
works fine for me.

Then /home/tqm-dev/.cache/godot/tmpexport.apk does not exist because of the above error.

@tqm-dev In addition can you enable custom build in your Android export settings and try building and signing your apk again.

I am going to try but still struggling to set it up for custom build yet .

Once I switched java runtime OpenJ9 to HotSpot (both are OpenJDK
is giving me the error:

Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.UnsupportedClassVersionError: com/android/apksigner/ApkSignerTool has been compiled by a more recent version of the Java Runtime (class file version 53.0), this version of the Java Runtime only recognizes class file versions up to 52.0

Then I installed OpenJDK 11 HotSpot and tried again, the result is different than before:

Exception in thread "main" java.io.FileNotFoundException: /home/takuma/.cache/godot/tmpexport.apk (No such file or directory)
	at java.base/java.io.RandomAccessFile.open0(Native Method)
	at java.base/java.io.RandomAccessFile.open(RandomAccessFile.java:345)
	at java.base/java.io.RandomAccessFile.<init>(RandomAccessFile.java:259)
	at java.base/java.io.RandomAccessFile.<init>(RandomAccessFile.java:214)
	at com.android.apksig.ApkSigner.sign(ApkSigner.java:183)
	at com.android.apksigner.ApkSignerTool.sign(ApkSignerTool.java:344)
	at com.android.apksigner.ApkSignerTool.main(ApkSignerTool.java:84)

@m4gr3d

I tried signing my godot_quest_example.apk file with apksigner(OpenJDK 11 HotSpot) was succeeded by manually.
And installed apk by adb command, then launched my app using SideQuest or adb shell.
I think the reason why I failed signing is related for signing on godot, not apksigner problems that I thought about v2 scheme.

@tqm-dev Does it work if you delete ~/.cache/godot/tmpexport*?

@akien-mga

@tqm-dev Does it work if you delete ~/.cache/godot/tmpexport*?

It does not exist when I try to delete it.
tmpexport.apk.tmp, tmpexport-unaligned.apk only appeared at one click deploy, then immediately removed.

@akien-mga
I solved .

The way that solved the issue for me is that launch godot from command line with using OpenJDK 11.
also using OpenGL ES3 is fine for me.

I do not know the problem is only for my environment.
If it is not, the documentation should be maintained with more details for exporting to Oculus Quest 2.

Thank you.

I had the same problem with error #127 and no matter what I did it was still there.
Fixed it by downloading Godot from official website. The one that I had before was from Elementary OS App Center (I guess it is a flatpack) and reinstalling it did not help, but the version from the website works just fine

The one that I had before was from Elementary OS App Center (I guess it is a flatpack) and reinstalling it did not help, but the version from the website works just fine

Exporting to Android isn’t supported in Snap/Flatpak versions because of sandboxing limitations.

Ok, makes sense. But it’s pretty hard to understand it from the error message

Ok, makes sense. But it’s pretty hard to understand it from the error message

To improve this, we can prevent exporting to Android from the Flatpak/Snap versions, either by patching those versions downstream or by detecting the presence of a /.flatpak-info file and triggering an error in that case.

Edit: Pull request opened: flathub/org.godotengine.Godot#72

I just ran into this and want to throw my solution onto this discussion in case anyone else ends up here with the same problem as me.

My problem was that I never added openjdk’s bin folder to my PATH. This wasn’t an issue in earlier versions since we told godot where to find jarsigner, but the new version assumes it (or some other openjdk component) is in your PATH.

If you’re in the same situation I was, you can fix it by adding this line to your ~/.profile file and then rebooting:

PATH="WHEREVER_YOU_PUT_OPENJDK/openjdk8/bin:$PATH"

Also encountering this problem on Linux (Ubuntu 20.04 MATE), and found a quirk:

Oddly, if I launch godot manually from a terminal, the apksigner error doesn’t appear, and it exports normally.

If I launch godot from a desktop shortcut, then the apksigner error occurs.

Edit: this is a Linux PATH issue, but I wanted to mention because I had this problem when upgrading from 3.2 to 3.3 and it might help someone else wondering why they are getting this error.

Have you tried the solution I posted above? It sounds like you might be
adding something to your PATH variable in either your terminal or .bashrc
file when you need to set it in .profile if you want stuff launched outside
the terminal to see it.

…

I just ran into this and want to throw my solution onto this discussion in case anyone else ends up here with the same problem as me.

My problem was that I never added openjdk’s bin folder to my PATH. This wasn’t an issue in earlier versions since we told godot where to find jarsigner, but the new version assumes it (or some other openjdk component) is in your PATH.

If you’re in the same situation I was, you can fix it by adding this line to your ~/.profile file and then rebooting:

PATH="WHEREVER_YOU_PUT_OPENJDK/openjdk8/bin:$PATH"

I ended up adding openjdk path to .bashrc !

Adding the path to .profile works fine.
But, exporting to Oculus Quest 2, it does not work with OpenJDK8 but OpenJDK11 works fine.

OK, I’m retarded, forgot to generate a new keystore (the old one will not work). Feel free to close.

For me this solution didnt work. I unticked the ‘signed’ box under package section and export was successful …. bt that causes another apk running issue. certificate

I just ran into this and want to throw my solution onto this discussion in case anyone else ends up here with the same problem as me.

My problem was that I never added openjdk’s bin folder to my PATH. This wasn’t an issue in earlier versions since we told godot where to find jarsigner, but the new version assumes it (or some other openjdk component) is in your PATH.

If you’re in the same situation I was, you can fix it by adding this line to your ~/.profile file and then rebooting:

PATH="WHEREVER_YOU_PUT_OPENJDK/openjdk8/bin:$PATH"

Thank you very much the solution also worked pramin. But for some reason I had already added it to ~/.bashrc and ~/.zshrc, and just to export to android I got the signature error (#127). To be able to avoid this error I had to open it through the terminal.

OS: POP_OS 21.10
GODOT: v3.4.4.stable.official [419e713] (download from official site)

But for some reason I had already added it to ~/.bashrc and ~/.zshrc, and just to export to android I got the signature error (#127). To be able to avoid this error I had to open it through the terminal.

.bashrc and .zshrc are not read by your desktop environment when you log in. To have environment variables that work with your basic GUI session (when not starting applications from a terminal), you need to add them to the system-wide /etc/environment. This file needs to be edited as root, and it cannot expand environment variables. Therefore, paths must be written in their full, absolute form, instead of using variables such as $HOME.

Check $PATH and $JAVA_HOME, it solved the issue for me.

I was seeing the same issues as I also use .zshrc. Once I opened Godot through the terminal, it shows the little android icon in the top right and I can «install» it.

The problem for me is that the app never actually loads. It just shows the 3 dots forever.

Any ideas why that might be happening?

I was seeing the same issues as I also use .zshrc. Once I opened Godot through the terminal, it shows the little android icon in the top right and I can «install» it.

The problem for me is that the app never actually loads. It just shows the 3 dots forever.

Any ideas why that might be happening?

You could run «adb» in another terminal to try and see what’s happening. There might be a better way tho