Hey Ralph and everyone who will read this (now and in the future)… We FINNALLY got this solved! So, as you know, Google changed PEPK and they no longer supply the Signing Key. Using their new method with PEPK, we got error after error after error! What finally worked was installing version 17.0.6+10 of OpenLogic’s OpenJDK version of Java. We specifically used this version on our Windows computer: https://builds.openlogic.com/downloadJDK/openlogic-openjdk-jre/17.0.6+10/openlogic-openjdk-jre-17.0.6+10-windows-x64.msi). This version of Java has the appropriate encryption libraries needed for the PEPK Tool that other versions of Java didn’t include.
-Dan From: use-livecode <use-livecode-boun...@lists.runrev.com> on behalf of Ralph DiMola via use-livecode <use-livecode@lists.runrev.com> Date: Wednesday, June 21, 2023 at 11:16 AM To: 'How to use LiveCode' <use-livecode@lists.runrev.com> Cc: Ralph DiMola <rdim...@evergreeninfo.net> Subject: RE: Android Signing I'm sorry, I don't exactly remember. I think that came from the developer console when I selected the pepk option when signing. You can always "Request upload key reset" on the developer console in Setup==>App Integrity in the "App signing" tab. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net -----Original Message----- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Dan Friedman via use-livecode Sent: Wednesday, June 21, 2023 11:51 AM To: How to use LiveCode Cc: Dan Friedman Subject: Re: Android Signing Ralph, Thank you for the reply. I have an old version of the pepk.jar from about a year ago. didn't even try it as I figured it could not be used. I'll give it a try. but, where did you/I get the encryptionkey? SomeVeryLongHexString? -Dan From: use-livecode <use-livecode-boun...@lists.runrev.com> on behalf of Ralph DiMola via use-livecode <use-livecode@lists.runrev.com> Date: Wednesday, June 21, 2023 at 8:18 AM To: 'How to use LiveCode' <use-livecode@lists.runrev.com> Cc: Ralph DiMola <rdim...@evergreeninfo.net> Subject: RE: Android Signing Dan, This is how I did it. NOTE: pepk-v1.jar is just my name for the version that worked. I can post this version if you would like to try it? Actual output from win 10 command line: (names changed to protect the innocent) --------------- java -jar pepk-v1.jar --keystore=MyKeyStore.keystore --alias=AppKeyStoreAilias --output=z:\SomPath\encryptedKey.key --encryptionkey=SomeVeryLongHexString Enter password for store 'MyKeyStore.keystore': Enter password for key 'AppKeyStoreAilias': ---------------------- I then had encryptedKey.key file created. Ralph DiMola IT Director Evergreen Information Services rdim...@evergreeninfo.net Phone: 518-636-3998 Ex:11 Cell: 518-796-9332 -----Original Message----- From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf Of Dan Friedman via use-livecode Sent: Wednesday, June 21, 2023 1:24 AM To: How to use LiveCode Cc: Dan Friedman Subject: Re: Android Signing Jacqueline, Thank you for the reply. That is EXACLY what I am doing. I downloaded the public key and the PEPK tool. Pointed the command to the existing keystore file and got this error: "Cannot find any provider supporting RSA/NONE/OAEPWithSHA1AndMGF1Padding..." It looks like there is an error in the PEPK tool. "/NONE/" is not a supported encryption! I would think it would be "/AES/". -Dan From: use-livecode <use-livecode-boun...@lists.runrev.com> on behalf of J. Landman Gay via use-livecode <use-livecode@lists.runrev.com> Date: Tuesday, June 20, 2023 at 12:42 PM To: How to use LiveCode <use-livecode@lists.runrev.com> Cc: J. Landman Gay <jac...@hyperactivesw.com> Subject: Re: Android Signing On 6/19/23 5:29 PM, Dan Friedman via use-livecode wrote: > I am trying to update an Android app that was previously release on > the Google Play Store. When I went to upload the Bundle, I got this message: > > "To upload an Android App Bundle you must be enrolled in Play App Signing." > > With a little research, I found the App Signing area under "App Integrity". I tried to follow the directions, but I just get errors. Anyone done this? If so, do you have any guidance on this? I had to do this last week with an update to an existing published app on Google Play. Do you have your original signing key for the app? You'll need that first. Sign your app as usual with the original key. Then look at this: <https://developer.android.com/studio/publish/app-signing#enroll_existing> I can't review the necessary Terminal command because I already went through the process and it isn't available to me now. But originally it gave the command to generate the Play Store signing key. I already had a pepk.jar file from before and I used that. I put it into the same directory with Java because I didn't know how else to do it. The Terminal command Google provided starts like this: java -jar pepk.jar --keystore=<yourKeystore.jks> --alias=<your keystore alias> --output=<create a file name> --encryptionkey=<huge long hex alias> number> At what point are you getting the errors? My main issue was in getting Terminal to find Java, it took me a couple of hours and some research to get the path to Java to work. I know almost nothing about Terminal. Let us know where you get stuck, though I can't promise I can help. I congratulate Google on making Android submissions nearly as difficult as iOS. We need an LC lesson this this. -- Jacqueline Landman Gay | jac...@hyperactivesw.com HyperActive Software | http://www.hyperactivesw.com _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
