Hot repair method and device, equipment and storage medium

Abstract

The embodiment of the invention provides a hot repair method and device, equipment and a storage medium. The method comprises the steps: compiling a software development kit SDK used for hot repair; searching a target file used for storing a keeping rule during code obfuscation; searching content needing to be kept in the SDK, and generating an updated keeping rule based on the content; updating the retention rule in the target file into the updated retention rule, and generating a binary archived file, wherein the binary archived file is used for providing a hot repair function for a target application accessing the SDK. According to the embodiment of the invention, after the access side App is secondarily confused, the hot repair function of the SDK can be conveniently and effectively used without additional operation, and the application range of the SDK hot repair is expanded.

Description

technical field [0001] Embodiments of the present disclosure relate to the field of computer technology, and in particular, to a hot repair method, device, equipment, and storage medium. Background technique [0002] Hot fix (hotfix) refers to the method of implementing online repair by releasing a patch (patch, that is, a patch for repairing a vulnerability), which is a low-cost method for repairing software version defects. Existing hot repair methods are all to actively initiate a request to the server when the client starts an application (App, application) to check whether there is a hot repair script, and if there is a script, download the script and execute the script. [0003] Common methods for software development kit (Software Development Kit, SDK)-level hot fixes include SDK hot fixes that use the hook program (hookApp) compilation process or use their own code (project_only) to perform optional hot fixes within the scope Generally, the accessing App needs to pe...

AI Technical Summary

Problems solved by technology

[0003] Common methods for software development kit (Software Development Kit, SDK)-level hot fixes include SDK hot fixes that use the hook program (hookApp) compilation process or use their own code (project_only) to perform optional hot fixes within the scope Solution, the general access party App needs to perform secondary obfuscation when accessing the SDK, but the secondary obfuscation may cause the hot patch to be unavailable, the hot fix to fail, and may even cause the App to fail to connect

In the prior art, by giving the corresponding keep rule requirements, the accessing App adds the corresponding keep (that is, does not confuse or keep) rules when accessing the SDK, but this will cause the following defects: if the keep rule is provided, it depends on Manually perform keep (that is, not confuse) when the App is connected. If the App omits to add other relevant rules, it may cause problems such as hot fix invalidation and App flashback. At the same time, the SDK and App need to manually maintain the keep rules every time the SDK version is updated. , high maintenance cost

[0004] Therefore, the hot repair solution of the existing technology cannot guarantee the effectiveness of the hot repair once the access party App is confused twice, and may even cause the access party App to crash due to the issuance of the hot fix. Rules to ensure the usability after the second obfuscation also need to be jointly maintained by both the SDK and the access-side App, which is very intrusive for the access-side App

Images