A desktop-side packaging method and packaging tool for fast packaging based on apk decompilation

Abstract

The present invention relates to a packaging method and packaging tool based on APK decompilation and fast packaging on the desktop. The packaging steps include filling in or importing the basic information of the target APP to be packaged, selecting the desktop icon or startup image of the APP, and selecting the source for packaging. APK file, APP signature file, fill in the signature file information, according to the selected source APK file, use APKtool to decompress, decompress to the specified cache directory for packaging, modify or replace the decompressed package information according to the filled and checked packaging information Generate a new package, use APKtool to build and compile the new package, generate an unsigned APK package, sign the unsigned APK package, and save it after signing.

Description

technical field [0001] The invention relates to the field of technical computer data processing, in particular to a packaging method and a packaging tool based on APK decompilation and fast package desktop. Background technique [0002] At present, APP factory project packaging needs to fill in a lot of configuration files (such as three-party platform key, various interface address configuration, etc.), and various icon files. Configuration replacement and compilation based on source code make the configuration cumbersome, error-prone, and the project is too large The post-compilation time is relatively long, and the third-party sharing and login of the WeChat platform needs to manually create a java file with the same name as the APP package to compile and generate a smali file. Manual packaging may be forgotten, resulting in the inability to share or log in, and the APP three-party push It is also necessary to add some push configuration requirements in the manifest.xml a...

AI Technical Summary

Problems solved by technology

[0002] At present, APP factory project packaging needs to fill in a lot of configuration files (such as three-party platform key, various interface address configuration, etc.), and various icon files. Configuration replacement and compilation based on source code make the configuration cumbersome, error-prone, and the project is too large The post-compilation time is relatively long, and the third-party sharing and login of the WeChat platform needs to manually create a java file with the same name as the APP package to compile and generate a smali file. Manual packaging may be forgotten, resulting in the inability to share or log in, and the APP three-party push It is also necessary to add some push configuration requirements in the manifest.xml according to the package name to have the same name as the name. In addition, the APP has a basic configuration item that we cannot manually create and put into the APK every time. An automated solution is needed.

Images