Re: Android PlayStore Warning APK v1 signature scheme

2020-10-14 Thread J. Landman Gay via use-livecode

On 10/14/20 11:18 AM, Ralph DiMola via use-livecode wrote:

I just got this message when submitting a new app to the PlayStore

Your APK is only signed using the APK v1 signature scheme. This will fail to 
install in versions of Android equal or higher to 11 if the 
android:targetSdkVersion is set to 30 or higher. Please use apksigner to sign 
your APK or switch to the Android App Bundle to fix this.

Does anyone know what the deal is here?


Google explains it here:
https://developer.android.com/studio/command-line/apksigner

Apps already published in the Play Store can continue to use the v1 scheme, created with 
keytool, because updates aren't possible if the signature changes. But new apps should use the 
v2 scheme which is done with apksigner.


I got a little lost in that web page when determining what the variables should be in the 
terminal command. Some guidance on that would be helpful. I do remember when I created the 
signature for an app a few months ago, I got a warning that I was using v1 and I should 
consider using v2 instead, but Google did not reject the app with the v1 signature.


--
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


Re: Android PlayStore Warning APK v1 signature scheme

2020-10-14 Thread JeeJeeStudio via use-livecode
Good question. I'm not 100% sure, but if I'm correct you can update. So I
don't think the keypair will change. I've not had the error you have, and
I've updated with lc961 which uses the correct target. So i made the normal
keystore and did the thing as in the previous mail and had no problems as
far as i know. Only thing is lc accepts only .keystore. Most probably as
long the reversed dns name com.appname.blabla is not changed and you
increase the version nr, also when an app is wrong or declined, then it
should go ok.

Op wo 14 okt. 2020 22:03 schreef Ralph DiMola via use-livecode <
use-livecode@lists.runrev.com>:

>
>
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdim...@evergreeninfo.net
> Phone: 518-636-3998 Ex:11
> Cell: 518-796-9332
> Thanks!
>
> One interesting thing is that keytool requires the keystore and the alias
> passwords to be the same. I had them as different. Although you can change
> the alias password with other tools I left them the same for now.
>
> Question: Do you know if the key-pair or fingerprints will change? In
> otherwords can I update an existing app after converting the keystore to
> PKCS12?
>
> -Original Message-
> From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On
> Behalf
> Of JeeJeeStudio via use-livecode
> Sent: Wednesday, October 14, 2020 2:43 PM
> To: How to use LiveCode
> Cc: JeeJeeStudio
> Subject: Re: Android PlayStore Warning APK v1 signature scheme
>
> I think you need to use PKCS12 industry standard format instead of the
> normal keystore. You can import your existing key via command prompt.
> Keytool -importkeystore -srckeystore yourapp.keystore -destkeystore
> yourapp.keystore -deststoretype pkcs12
>
> Op wo 14 okt. 2020 18:17 schreef Ralph DiMola via use-livecode <
> use-livecode@lists.runrev.com>:
>
> > I just got this message when submitting a new app to the PlayStore
> >
> > Your APK is only signed using the APK v1 signature scheme. This will
> > fail to install in versions of Android equal or higher to 11 if the
> > android:targetSdkVersion is set to 30 or higher. Please use apksigner
> > to sign your APK or switch to the Android App Bundle to fix this.
> >
> > Does anyone know what the deal is here?
> >
> > Ralph DiMola
> > IT Director
> > Evergreen Information Services
> > rdim...@evergreeninfo.net
> >
> >
> > ___
> > 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


RE: Android PlayStore Warning APK v1 signature scheme

2020-10-14 Thread Ralph DiMola via use-livecode



Ralph DiMola
IT Director
Evergreen Information Services
rdim...@evergreeninfo.net
Phone: 518-636-3998 Ex:11
Cell: 518-796-9332
Thanks!

One interesting thing is that keytool requires the keystore and the alias
passwords to be the same. I had them as different. Although you can change
the alias password with other tools I left them the same for now.

Question: Do you know if the key-pair or fingerprints will change? In
otherwords can I update an existing app after converting the keystore to
PKCS12?

-Original Message-
From: use-livecode [mailto:use-livecode-boun...@lists.runrev.com] On Behalf
Of JeeJeeStudio via use-livecode
Sent: Wednesday, October 14, 2020 2:43 PM
To: How to use LiveCode
Cc: JeeJeeStudio
Subject: Re: Android PlayStore Warning APK v1 signature scheme

I think you need to use PKCS12 industry standard format instead of the
normal keystore. You can import your existing key via command prompt.
Keytool -importkeystore -srckeystore yourapp.keystore -destkeystore
yourapp.keystore -deststoretype pkcs12

Op wo 14 okt. 2020 18:17 schreef Ralph DiMola via use-livecode <
use-livecode@lists.runrev.com>:

> I just got this message when submitting a new app to the PlayStore
>
> Your APK is only signed using the APK v1 signature scheme. This will 
> fail to install in versions of Android equal or higher to 11 if the 
> android:targetSdkVersion is set to 30 or higher. Please use apksigner 
> to sign your APK or switch to the Android App Bundle to fix this.
>
> Does anyone know what the deal is here?
>
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdim...@evergreeninfo.net
>
>
> ___
> 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


Re: Android PlayStore Warning APK v1 signature scheme

2020-10-14 Thread JeeJeeStudio via use-livecode
I think you need to use PKCS12 industry standard format instead of the
normal keystore. You can import your existing key via command prompt.
Keytool -importkeystore -srckeystore yourapp.keystore -destkeystore
yourapp.keystore -deststoretype pkcs12

Op wo 14 okt. 2020 18:17 schreef Ralph DiMola via use-livecode <
use-livecode@lists.runrev.com>:

> I just got this message when submitting a new app to the PlayStore
>
> Your APK is only signed using the APK v1 signature scheme. This will fail
> to install in versions of Android equal or higher to 11 if the
> android:targetSdkVersion is set to 30 or higher. Please use apksigner to
> sign your APK or switch to the Android App Bundle to fix this.
>
> Does anyone know what the deal is here?
>
> Ralph DiMola
> IT Director
> Evergreen Information Services
> rdim...@evergreeninfo.net
>
>
> ___
> 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