Desktop end packing method and packing tool based on APK decompilation fast packing

Abstract

A method for quickly packaging desktop end based on APK decompilation. The packaging steps are as follows: filling in or importing the basic data of the target APP to be packaged, selecting the desktop icon or boot diagram for APP, selecting the source APK file and APP Signature file for package, filling in the signature document information, depending on the source APK file selected, using APKtool for decompression, extracting to the specified cache directory for packaging, modifying or replacing the extracted package information according to the filled and checked packaging data to generatenew packages, using APKtool to build new packages back to compile, generating unsigned APK packages, signing the unsigned APK packages, and saving after signature is completed.

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