Hi Jacque, > Am 12.04.2023 um 18:58 schrieb J. Landman Gay via use-livecode > <use-livecode@lists.runrev.com>: > > I think the option to allow Google to manage the keys only appears the first > time you upload a new app.
OK, will take a deeper look once I upload the new app. > Maybe there's a way to retake control of the keys? Nope! Google explicitely states that they will NOT share any of their keys. Will try and look better next time. > Is there any info in the app page that tells you who has control of the keys? > > If you can verify that Google is managing the keys, and you can't regain > control, then I think the only fix is for LC to update the SB to recognize an > upload key. Ouch, that may take a couple of versions of LC until that will happen and I'm already 66. 8-) Will create a new report/enhancement request tomorrow. I will have to dive deeper into the "Google Play Console"... > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > On April 12, 2023 11:19:40 AM Klaus major-k via use-livecode > <use-livecode@lists.runrev.com> wrote: > >> Hi Jacque, >> >>> Am 12.04.2023 um 18:12 schrieb J. Landman Gay via use-livecode >>> <use-livecode@lists.runrev.com>: >>> Did you agree to let Google manage your keys? >> >> to be honest, I did not find that one (yet) on the Google Dev pages!? >> Any hints much appreciated! >> >>> If so you need to create an upload key, which I think is different from the >>> original signing key. >>> LC may not recognize that format. >> >> Yes, that's what I experienced. >> See below, LC told me about a wrong format of the key file. >> >>> I've never let Google manage my keys so I'm not sure how that works. >>> -- >>> Jacqueline Landman Gay | jac...@hyperactivesw.com >>> HyperActive Software | http://www.hyperactivesw.com >>> On April 12, 2023 7:18:57 AM Klaus major-k via use-livecode >>> <use-livecode@lists.runrev.com> wrote: >>> >>>> Hi all, >>>> >>>> I created a new app and cannot sign it!? >>>> >>>> I did this: >>>> <https://developer.android.com/studio/publish/app-signing> >>>> -> Generate an upload key and keystore >>>> and generated a *.jks file. >>>> >>>> Then I selected this key file in LC, and at the end of the signing process >>>> LC told me that the keystore file had the wrong format!? >>>> >>>> Then I renamed the key to *.keystore >>>> And LC told me again that this was the wrong format of the key file? >>>> >>>> What am I missing? >>>> Thank you for any hint! >>>> >>>> P.S. >>>> I had published my earlier app successfully to the Google Play Store with >>>> a selfsigned key in "Android Studio" as shown in: >>>> <https://lessons.livecode.com/m/4069/l/32674-how-do-i-create-a-self-signed-certificate-for-an-android-app> >>>> >>>> When I later wanted to upload an update, Google told me that I did not use >>>> the correct key for signing??? >>>> So I read up everthing about this and came to create an UPLOAD key, so I >>>> could use this later for any further >>>> updates of the app. >>>> >>>> However that failed so far, see above.. Best Klaus -- Klaus Major https://www.major-k.de https://www.major-k.de/bass kl...@major-k.de _______________________________________________ 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
