Is your feature request related to a problem? Please describe.
Currently if a version code or other property of the AndroidManifest protobuf file is changed it requires manual parsing and re-serialization. It would be very helpful to have a command for the bundletool to support parsing and re-serializing the protobuf files.
Describe the solution you'd like
I'd suggest an extension off of the bundletool to convert AndroidManifest and other protobuf files to xml and a re-serialization command to assemble them for bundling. Much like what the apktool does today.
Describe alternatives you've considered
If APKs are available I believe there are workarounds using the apktool and inserting the AndroidManifest + using build-bundle but if you are trying to work with purely aab files then it would require parsing and re-serializing the protobuf file manually.
Additional context
This issue is based off largely off of a stackoverflow discussion. Relevant link
Is your feature request related to a problem? Please describe. Currently if a version code or other property of the AndroidManifest protobuf file is changed it requires manual parsing and re-serialization. It would be very helpful to have a command for the bundletool to support parsing and re-serializing the protobuf files.
Describe the solution you'd like I'd suggest an extension off of the bundletool to convert AndroidManifest and other protobuf files to xml and a re-serialization command to assemble them for bundling. Much like what the apktool does today.
Describe alternatives you've considered If APKs are available I believe there are workarounds using the apktool and inserting the AndroidManifest + using build-bundle but if you are trying to work with purely aab files then it would require parsing and re-serializing the protobuf file manually.
Additional context This issue is based off largely off of a stackoverflow discussion. Relevant link