This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
Thanks @Armelline but unfortunately it not works for me... it show errors
What errors? The app itself doesn't produce any errors (other than warning an APKS already exists, it has zero error checking) so the problems are likely in your signing process. Might be something we can avoid!
Info in case it's important: This is for a new upload for a file not yet on Google Play. Though I originally published it to GS a couple of years ago and haven't republished since. This comp is still on OS High Sierra.
When I enter everything in Terminal and hit enter, it tells me "Only one alias can be specified", then offers that I look up jarsigner -help.
I only have one alias and one keystore, and that is the one I am using, so what could I be doing wrong?
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
@nir3112 seems works with my testing so I think it just needs to push the latest aab or an APK derived from it
@pinkio75 admob problem is fixed as of the latest release.
@Binny touch issue was also not visible on the latest AAB release
We fixed a host of issues with Android 11 and certain devices (like Samsung and Pixels 4s) in the second to last AAB build. The APK build is still behind, but that will hopefully be fixed by this weekend.
@adent42 so if i now republish my game, and submit to google, users won’t get the sql error that hit them previously on sony and samsung devices?
ive jumped off gs for a while to learn new things, so i don’t want to pay for a month subscription if it’s going to give me a broken build again.
adent42Key Master, Head Chef, Executive Chef, Member, PROPosts: 3,201
Yes @bob loblaw , generating from AAB will remove the SQL error. Generating from APK will not. If you need or want to submit and APK, you will need to follow our instructions for creating a "universal" apk from the aab.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
Just in case anyone else has a similar issue to me signing the bundle, I had to change the 'SHA1withRSA' section to 'SHA1withDSA'. I'm signing using cmd on windows.
It enabled me to sign the aab although not sure if this will cause me issues further down the line...fingers crossed!
adent42Key Master, Head Chef, Executive Chef, Member, PROPosts: 3,201
@strag it shouldn't cause any issues as it actually is dependent on the keystore and key you've created. In our official docs, we should probably highlight what can change based on a individual developer's setup.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
@strag it shouldn't cause any issues as it actually is dependent on the keystore and key you've created. In our official docs, we should probably highlight what can change based on a individual developer's setup.
Yep, had no issues after that and published to Google successfully 👍
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
This is an embed external element. It can be deleted using the delete key or the backspace key. To view the full element, press the preview button below.
Comments
What errors? The app itself doesn't produce any errors (other than warning an APKS already exists, it has zero error checking) so the problems are likely in your signing process. Might be something we can avoid!
Contact me for custom work - Expert GS developer with 15 years of GS experience - Skype: armelline.support
@Armelline Sorry it works!
i've insert the wrong bundle name! because i've a lot of keystore! :P
Thanks for this great utility!
✮My Web Site✮ ✮My Full Games On Sale✮ ✮Follow Me✮ ✮My Video Channel✮ ✮Contact Me To Buy My GS Games✮
Glad it helped!
Contact me for custom work - Expert GS developer with 15 years of GS experience - Skype: armelline.support
Hi @ardent42 and all,
I'm trying this out for the first time and am getting an odd return in Terminal. So far all I have done is download the aab from GS and going through these exact steps: https://help.gamesalad.com/gamesalad-cookbook/publishing/4-android-publishing/android-app-bundle-aab-terminal-signing/.
Info in case it's important: This is for a new upload for a file not yet on Google Play. Though I originally published it to GS a couple of years ago and haven't republished since. This comp is still on OS High Sierra.
When I enter everything in Terminal and hit enter, it tells me "Only one alias can be specified", then offers that I look up jarsigner -help.
I only have one alias and one keystore, and that is the one I am using, so what could I be doing wrong?
Thanks for any help!
@adent42 so if i now republish my game, and submit to google, users won’t get the sql error that hit them previously on sony and samsung devices?
ive jumped off gs for a while to learn new things, so i don’t want to pay for a month subscription if it’s going to give me a broken build again.
Yes @bob loblaw , generating from AAB will remove the SQL error. Generating from APK will not. If you need or want to submit and APK, you will need to follow our instructions for creating a "universal" apk from the aab.
awesome. thanks @adent42
@bob You can use @Armelline's shell to extract APK from AAB, is really simple and avoid the terminal usage.
✮My Web Site✮ ✮My Full Games On Sale✮ ✮Follow Me✮ ✮My Video Channel✮ ✮Contact Me To Buy My GS Games✮
will give it a go. cheers.
Just in case anyone else has a similar issue to me signing the bundle, I had to change the 'SHA1withRSA' section to 'SHA1withDSA'. I'm signing using cmd on windows.
It enabled me to sign the aab although not sure if this will cause me issues further down the line...fingers crossed!
@strag it shouldn't cause any issues as it actually is dependent on the keystore and key you've created. In our official docs, we should probably highlight what can change based on a individual developer's setup.
Yep, had no issues after that and published to Google successfully 👍
@Armelline I'm trying your signing tool but am stumped at the part where it asks to select bundle tool.
would appreciate your help to push me through so I can sign my app please.
@bob loblaw There's a link to the bundle tool in the first post of this thread.
Contact me for custom work - Expert GS developer with 15 years of GS experience - Skype: armelline.support
cheers
works perfect (once you pointed me in the right direction and I figured the bundle name thing was the keystone alias).
thanks for your advice and putting that signing tool together @Armelline it's much appreciated.
hows the new signing tool coming along?
What should i use as the bundle name?