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

Android Export issue: jarsigner error #1, export.cpp warnings #3294

Closed
DeRobyJ opened this issue Jan 9, 2016 · 10 comments
Closed

Android Export issue: jarsigner error #1, export.cpp warnings #3294

DeRobyJ opened this issue Jan 9, 2016 · 10 comments

Comments

@DeRobyJ
Copy link

DeRobyJ commented Jan 9, 2016

Hi!
First of all, the installation of both godot and the android requirements went great, the guide is clear.

Then, I was able to produce and apk, but it doesn't work because of these errors.

First, jarsigner error #1, which was resolved in another issue by deleting META-INF from the apk. However I didn't find any META-INF.

In fact, this problem is probably caused by a bunch of export.cpp errors.
Whenever I try to export to Android, the program outputs these:

  • platform/android/export/export.cpp:854 - Screen res name in a resource, should be plaintext
    [4 times]

and then

  • platform/android/export/export.cpp:799 - Application name in a resource, should be plaintext (but you can ignore this).
  • platform/android/export/export.cpp:810 - Activity name in a resource, should be plaintext (but you can ignore this)

I tried it on a almost plain project of mine and on the "Area 2D input events" demo project.

So, am I missing somthing?
I'm using Ubuntu Studio 14.04, tried both Godot 1.1 and the last Alpha of 2.0 (the errors are the same)
Using Openjdk 6 from ubuntu repositories.

Thanks in advance!

@reduz
Copy link
Member

reduz commented Jan 9, 2016

The warnings are unrelated and should eventually be removed I guess.Would
appreciate if you could describe the jarsigner error.

On Sat, Jan 9, 2016 at 1:36 PM, Roberto Giaconia notifications@github.com
wrote:

Hi!
First of all, the installation of both godot and the android requirements
went great, the guide is clear.

Then, I was able to produce and apk, but it doesn't work because of these
errors.

First, jarsigner error #1 #1,
which was resolved in another issue by deleting META-INF from the apk.
However I didn't find any META-INF.

In fact, this problem is probably caused by a bunch of export.cpp errors.
Whenever I try to export to Android, the program outputs these:

  • platform/android/export/export.cpp:854 - Screen res name in a
    resource, should be plaintext [4 times]

and then

platform/android/export/export.cpp:799 - Application name in a
resource, should be plaintext (but you can ignore this).

platform/android/export/export.cpp:810 - Activity name in a resource,
should be plaintext (but you can ignore this)

I tried it on a almost plain project of mine and on the "Area 2D input
events" demo project.

So, am I missing somthing?
I'm using Ubuntu Studio 14.04, tried both Godot 1.1 and the last Alpha of
2.0 (the errors are the same)

Thanks in advance!


Reply to this email directly or view it on GitHub
#3294.

@DeRobyJ
Copy link
Author

DeRobyJ commented Jan 9, 2016

Steps:

  • Project open
  • Export, Android
  • Settings almost untouched (added project name and keystore, just to try, but nothing changed)
  • Export

the bar loads till 99%, while a message like "debug apk something" is shown, then popup:
'jarsigner' returned with error #1

@reduz
Copy link
Member

reduz commented Jan 10, 2016

Can you check the console (command line) and/or debug error log and paste the entire error?

@DeRobyJ
Copy link
Author

DeRobyJ commented Jan 11, 2016

Sorry I'm relatively new to godot, how do I do it?

@akien-mga
Copy link
Member

I believe this was fixed by #5235.

@akien-mga akien-mga added this to the 2.1 milestone Jul 8, 2016
@reduz
Copy link
Member

reduz commented Jul 8, 2016

this is generally also because of wrong Java version. I would kill to be
able to sign jars within Godot..

On Fri, Jul 8, 2016 at 11:28 AM, Rémi Verschelde notifications@github.com
wrote:

Closed #3294 #3294.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#3294 (comment), or mute
the thread
https://github.com/notifications/unsubscribe/AF-Z209sAmVw6tZmAPCXCl4ttmLq6Xktks5qTl6ngaJpZM4HBt2o
.

@akien-mga
Copy link
Member

akien-mga commented Jul 8, 2016

This used to be due to wrong Java version, but honestly since I started using Godot I never saw anyone not manage to sign jars due to OpenJDK 7 or OpenJDK 8. But I've seen that argument a lot :p
I think the issue is most of the time that people haven't configured their adb or signing keys properly.

@reduz
Copy link
Member

reduz commented Jul 8, 2016

I can't sign jars with OpenJDK 9 :P

On Fri, Jul 8, 2016 at 11:45 AM, Rémi Verschelde notifications@github.com
wrote:

This used to be due to wrong Java version, but honestly since I started
using Godot I never saw anyone not manage to sign jars with OpenJDK 7 or
OpenJDK 8. But I've seen that argument a lot :p
I think the issue is most of the time that people haven't configured their
adb or signing keys properly.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#3294 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AF-Z21O8eKIbz2DRT40x5SLbJqWC11w7ks5qTmKFgaJpZM4HBt2o
.

@reduz
Copy link
Member

reduz commented Jul 8, 2016

Though It seems to be our fault, Jarsigner throws an error because the date
of the files we add is wrong in Java 8, and this becomes a fatal error in
Java 9, we should probably fix it

On Fri, Jul 8, 2016 at 11:48 AM, Juan Linietsky reduzio@gmail.com wrote:

I can't sign jars with OpenJDK 9 :P

On Fri, Jul 8, 2016 at 11:45 AM, Rémi Verschelde <notifications@github.com

wrote:

This used to be due to wrong Java version, but honestly since I
started using Godot I never saw anyone not manage to sign jars with OpenJDK
7 or OpenJDK 8. But I've seen that argument a lot :p
I think the issue is most of the time that people haven't configured
their adb or signing keys properly.


You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#3294 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AF-Z21O8eKIbz2DRT40x5SLbJqWC11w7ks5qTmKFgaJpZM4HBt2o
.

@akien-mga
Copy link
Member

Didn't even know Java 9 was a thing already :p

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

No branches or pull requests

4 participants