Hi all,
I wonder whether an apk manager lib could be designed in order to manipulate an existing apk by B4A code.
That lib should be able at least to read in an existing apk, reach any embedded dir/file, add/modify files in "assets" dir and write out a new apk file.
Methods to read infos from specialized file types could be added to augment lib capabilities.
Reading/writing an existing apk "as is" is surely doable since there are out backup apps that work this way.
But what about a simple adding of an image file in the assets dir? Does it break any CRC check or other static info about the original apk file?
I've got no specific usage in mind for the above, right now. Just curious about its feasibility and willing to collect hints and ideas on the subject.
Thank you.
Umberto
I wonder whether an apk manager lib could be designed in order to manipulate an existing apk by B4A code.
That lib should be able at least to read in an existing apk, reach any embedded dir/file, add/modify files in "assets" dir and write out a new apk file.
Methods to read infos from specialized file types could be added to augment lib capabilities.
Reading/writing an existing apk "as is" is surely doable since there are out backup apps that work this way.
But what about a simple adding of an image file in the assets dir? Does it break any CRC check or other static info about the original apk file?
I've got no specific usage in mind for the above, right now. Just curious about its feasibility and willing to collect hints and ideas on the subject.
Thank you.
Umberto
Last edited:
