Update AndroidBuild.java for AAB Jar Signing(V1 Signature) #677
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi @codeanticode @ranaaditya
I found that just Jar signing (V1 signature Scheme) would be sufficient to build bundles that would be uploadable on Play Console. Not sure as I don't have access to the play console But I tried comparing the signing information of the Jar Signed Bundle generated from this PR and the signed bundle generated from Android Studio. I found that both the bundles are signed with the same signing algorithm.
I thought of signing aab with bundletool but it's not included in SDK and the size of bundletool-all.jar is around 26 mb where as AndroidMode itself is around 13 MB. Later found that Jar Signing(V1 signature scheme) would be sufficient.
Can you confirm if the generated signed bundle is uploadable on Play Console? @codeanticode
Thanks,
Rupesh