I have an android app that's intended for both google play and app gallery , it's one project with 2 flavours , for the google play i generated a keystore , my questions are that

1- Should I use the google play keystore for app gallery or it needs to be a new one ?

2- Bundle id for appgallery can be same as google play or not ? Any pros and cons for same/different id ?

3- Does app gallery accepts aab or only apk as for google there is no choice (only aab)?

CodePudding user response：

You can generally use the same key-store and the same package name.
Use versionNameSuffix, because some devices may feature both stores.

If you want to publish AAB to AppGallery Connect, you need to enable signing.
It's the same as on Google Play; the release key will then become an upload key.

My plugin would also support AAB upload: agconnect-publishing-gradle-plugin.
So far it's probably only me, who uses it... which means it could use some testing.

CodePudding user response：

1- Should I use the google play keystore for app gallery or it needs to be a new one ?

No you should not, because it will cause cross-platform updates (it may update app gallery version from Google Play).

2- Bundle id for appgallery can be same as google play or not ? Any pros and cons for same/different id ?

It can be the same:

pros:

1. Easier for development

2. can use same accounts if you are using some 3rd party APIs

cons:

1- app gallery will try to update the app that you have instaled from Google Play and vise versa (but you can over come this with different keystores)

3- Does app gallery accepts aab or only apk as for google there is no choice (only aab)?

Yes it accepts AAB