10

I'm trying to follow the instructions on the Google Developer's Console to retrieve my .pem certificate's private key to use with the Google Play App Signing. Since I'm not using a Java keystore, I tried the advanced instructions, but on executing the file, I get no main manifest attribute, in pepk-src.jar error. What gives? I'm using java version "1.8.0_101".

tacobot
  • 145
  • 2
  • 10
  • Possible duplicate of this question? https://stackoverflow.com/questions/9689793/cant-execute-jar-file-no-main-manifest-attribute – RToyo Jun 23 '17 at 10:53
  • Tried those, didn't work. Kind of weird that it doesn't run properly when it's part of their instructions -__- – tacobot Jun 27 '17 at 02:13
  • Did you find the answer? I have te same issue – BonifatiusK Oct 12 '17 at 11:26
  • same here..doesn't anyone have answer to this question? – Shan Oct 21 '17 at 03:09
  • same problem here. It's completely unclear how to user this file – morksinaanab Jan 16 '18 at 04:08
  • The pepk-src.jar is the source code of PEPK. You can use it to look how Play encrypts the key, so you can perform the same operation if your key is not in a Java Keystore. There are no detailed instructions for this use-case because each developer would have different ways to extract their private key. – Pierre Dec 03 '18 at 22:27

1 Answers1

17

The download link they gave is apparently a source jar file, maybe they did that accidentally.

Screenshot from Google Play Console showing the "source" jar file link: Screenshot from Google Play Console showing the "source" jar file link ("pepk-src.jar")

Try to use this jar file (from Google): https://www.gstatic.com/play-apps-publisher-rapid/signing-tool/prod/pepk.jar

Screenshot from Google Play Console showing the jar file link ("pepk.jar")

Screenshot from Google Play Console showing the jar file link ("pepk.jar")

Good luck, peace out!

Access Denied
  • 8,723
  • 4
  • 42
  • 72
  • Wish I could do this answer justice, but I've long left the place where I had this problem. If someone else tries this and it works for them, I'll mark it as the answer. – tacobot Jun 12 '19 at 09:35
  • 2
    I just experienced this problem (Google still hasn't fix their website!) and I can confirm - this answer absolutely works. – Ludwik Trammer Jul 02 '19 at 12:45
  • 1
    That's a good answer. Look for gstatic.com in [link](https://lookup.icann.org/lookup) to see that this domain belongs to Google... – Oz Shabat Feb 10 '21 at 09:32
  • 1
    4 years and this is still not fixed on google's page. – Swissdude Feb 12 '21 at 20:26
  • Almost 5 years. There must be so many other more important bugs to fix that nobody finds the time to correct this ... or is it intention ("if these developers are not able to recognize and run a Java source file they should stop developing") – Hartmut Pfitzinger Nov 14 '21 at 18:17