Application processing method, device and computer-readable storage medium

Abstract

The present application discloses a method, device and computer-readable storage medium for processing an application, and relates to the field of financial technology and other related technical fields. The method includes: obtaining a dependency tree file corresponding to a target application and a target program identifier of the target application, wherein the dependency tree file is used to characterize the dependency relationship between a third-party software program and the target application; parsing the dependency tree file to obtain element information of the third-party software program; detecting whether the preset file contains a calling relationship between the target application and the third-party software program based on the target program identifier and the element information; and updating the calling relationship to the preset file when it is detected that the preset file does not contain a calling relationship between the target application and the third-party software program. The present application solves the technical problem of low management efficiency in the prior art when managing the calling relationship between an application and a third-party software program.

Description

Technical Field

[0001] The present application relates to the field of financial technology and other related technical fields, and specifically, to a method, device and computer-readable storage medium for processing an application. Background Art

[0002] During the integration development phase, Android apps (applications) rely on many self-developed SDKs (software development kits, third-party software programs) or SDKs provided by third parties. To strengthen SDK management, technicians typically use scanning tools to integrate the SDK usage scanning process during the app compilation process, thereby automatically scanning the SDK usage and managing the calling relationship between the app and the SDK based on the scanning results.

[0003] However, in the existing technology, since technicians manage the calling relationship between applications and SDKs manually, it is easy to miss SDKs and fail to update the calling status of SDKs in a timely manner, which is not conducive to managers to understand the actual calling status between applications and SDKs in a timely manner, and reduces the management efficiency of SDKs.

[0004] To address the above-mentioned problems, no effective solutions have been proposed so far. Summary of the Invention

[0005] The embodiments of the present application provide a method, device, and computer-readable storage medium for processing an application program to at least solve the technical problem of low management efficiency in the prior art when managing the calling relationship between an application program and a third-party software program.

[0006] According to one aspect of an embodiment of the present application, a method for processing an application is provided, comprising: obtaining a dependency tree file corresponding to a target application and a target program identifier of the target application, wherein the dependency tree file is used to characterize the dependency relationship between a third-party software program and the target application, the third-party software program being a program called by the target application during operation, and the third-party software program including a local software program and a remote software program; parsing the dependency tree file to obtain element information of the third-party software program, wherein the element information is a unique identifier of the third-party software program; detecting whether a preset file contains a calling relationship between the target application and the third-party software program based on the target program identifier and the element information, wherein the preset file pre-records the element information of the third-party software program and the program identifiers of all applications that have historical calling records with the third-party software program; and updating the calling relationship to the preset file when it is detected that the preset file does not contain a calling relationship between the target application and the third-party software program.

[0007] Furthermore, the application processing method includes: obtaining a first dependency tree sub-file by running a first command in an operating system on which a target application is installed, wherein the first dependency tree sub-file is used to characterize the dependency relationship between the remote software program and the target application, and the dependency relationship between the first local software program and the target application, the first local software program being a program that includes code and resource files and has a direct dependency relationship with the target application; and using the first dependency tree sub-file as one of the dependency tree files.

[0008] Furthermore, the application processing method includes: obtaining a second dependency tree sub-file by running a second command in the operating system, wherein the second dependency tree sub-file is used to represent the dependency relationship between the second local software program and the target application, and the dependency relationship between the third local software program and the target application, the second local software program is a program that does not contain resource files, and the third local software program is a program that contains code and resource files and has an indirect dependency relationship with the target application; and using the second dependency tree sub-file as one of the dependency tree files.

[0009] Furthermore, the processing method of the application includes: parsing the first dependency tree sub-file to obtain element information of the remote software program; parsing the first dependency tree sub-file and the second dependency tree sub-file to obtain the storage path of the local software program, wherein the local software program includes a first local software program, a second local software program and a third local software program; determining the element information of the local software program based on the storage path.

[0010] Furthermore, the application processing method includes: determining information summary information of the local software program according to the storage path, wherein the information summary information is information obtained by calculating the local software program according to the information summary algorithm; and determining element information of the local software program according to the information summary information.

[0011] Furthermore, the application processing method includes: determining at least one program identifier corresponding to the element information from all program identifiers in the preset file; detecting whether there is a target program identifier in the at least one program identifier; when the target program identifier exists in the at least one program identifier, determining that the preset file contains a calling relationship between the target application and the third-party software program; when the target program identifier does not exist in the at least one program identifier, determining that the preset file does not contain a calling relationship between the target application and the third-party software program.

[0012] Furthermore, the application processing method includes: after updating the call relationship to the preset file, when an exception occurs in the third-party software program, obtaining exception information of the third-party software program; determining the program identifier of the first application based on the element information of the third-party software program and the preset file, wherein the first application is an application that has an associated relationship with the third-party software program; generating prompt information based on the exception information and the program identifier of the first application, and sending the prompt information to the terminal device.

[0013] According to another aspect of an embodiment of the present application, a processing device for an application is also provided, including: an acquisition module, used to obtain a dependency tree file corresponding to a target application and a target program identifier of the target application, wherein the dependency tree file is used to characterize the dependency relationship between a third-party software program and the target application, and the third-party software program is a program called by the target application during operation, and the third-party software program includes a local software program and a remote software program; a parsing module, used to parse the dependency tree file and obtain element information of the third-party software program, wherein the element information is a unique identifier of the third-party software program; a detection module, used to detect whether a preset file contains a calling relationship between the target application and the third-party software program based on the target program identifier and the element information, wherein the preset file pre-records the element information of the third-party software program and the program identifiers of all applications that have historical calling records with the third-party software program; an update module, used to update the calling relationship to the preset file when it is detected that the preset file does not contain the calling relationship between the target application and the third-party software program.

[0014] According to another aspect of an embodiment of the present application, a computer-readable storage medium is further provided, in which a computer program is stored. The computer program is configured to execute the above-mentioned processing method of the application program when running.

[0015] According to another aspect of an embodiment of the present application, an electronic device is also provided, which includes one or more processors; a memory for storing one or more programs, which, when the one or more programs are executed by the one or more processors, enables the one or more processors to implement a method for running the programs, wherein the programs are configured to execute the above-mentioned application processing method at runtime.

[0016] In this application, a method is adopted to automatically determine all SDKs called by the application during operation through the application's dependency tree file. First, the dependency tree file corresponding to the target application and the target program identifier of the target application are obtained. Then, the dependency tree file is parsed to obtain the element information of the third-party software program. Based on the target program identifier and the element information, it is detected whether the preset file contains the calling relationship between the target application and the third-party software program. Finally, when it is detected that the preset file does not contain the calling relationship between the target application and the third-party software program, the calling relationship is updated to the preset file. Among them, the dependency tree file is used to characterize the dependency relationship between the third-party software program and the target application. The third-party software program is the program called by the target application during operation. The third-party software program includes local software programs and remote software programs. The element information is the unique identifier of the third-party software program. The preset file pre-records the element information of the third-party software program and the program identifiers of all applications that have historical call records with the third-party software program.

[0017] From the above content, it can be seen that the present application determines all third-party software programs called by the application during operation through a dependency tree file, and records the calling relationship in a preset file, thereby achieving the purpose of automatically maintaining the calling relationship between the application and the third-party software program. Compared with the existing technology that uses manual methods to manage the calling relationship between the application and the third-party software program, the technical method of the present application not only reduces the cost of manual maintenance, but also improves the management efficiency of third-party software programs and applications.

[0018] It can be seen that through the technical solution of the present application, the purpose of automatically managing the calling relationship between the application and the third-party software program is achieved, thereby realizing the effect of improving the management efficiency of the third-party software program, and further solving the technical problem of low management efficiency in the existing technology when managing the calling relationship between the application and the third-party software program. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the drawings:

[0020] Figure 1 is a flowchart of an optional application processing method according to an embodiment of the present application;

[0021] Figure 2 is a flowchart of another optional application processing method according to an embodiment of the present application;

[0022] Figure 3is a schematic diagram of an optional application processing device according to an embodiment of the present application;

[0023] Figure 4 is a schematic diagram of an optional electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0024] In order to enable those skilled in the art to better understand the present invention, the following will clearly and completely describe the technical solutions in the embodiments of the present invention in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments in the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of this application.

[0025] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in a sequence other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0026] Example 1

[0027] According to an embodiment of the present application, an embodiment of a method for processing an application is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0028] In addition, it should be noted that an application management system can serve as the execution entity of the application processing method in the embodiment of the present application.

[0029] Figure 1 is a flowchart of an optional application processing method according to an embodiment of the present application, such as Figure 1 As shown, the method includes the following steps:

[0030] Step S101: Obtain a dependency tree file corresponding to a target application and a target program identifier of the target application.

[0031] In step S101, a dependency tree file is used to represent the dependency relationship between a third-party software program and a target application. The third-party software program is a program called by the target application during operation. The third-party software program includes a local software program and a remote software program.

[0032] Specifically, the above-mentioned target application can be understood as an APP developed based on the Android system, and the above-mentioned third-party software program is the SDK that can be called by the APP. Among them, SDK can be divided into local SDK (corresponding to local software program) and remote SDK (corresponding to remote software program). The local SDK can be understood as an SDK deployed on the same local device as the APP. It is an SDK developed by the APP developer in the process of developing the APP; the remote SDK can be understood as an SDK provided by a third party. When the APP calls the remote SDK, it must first download the remote SDK to the local device through the download path provided by the third party, and then it can call the remote SDK.

[0033] Step S102: parse the dependency tree file to obtain element information of the third-party software program.

[0034] In step S102, the element information is the unique identifier of the third-party software program. Specifically, the element information is the Maven three-element information of the SDK, where the three elements are the SDK version number, the SDK package name, and the SDK module name. Maven is an automated management tool for project building and dependency management on the Java platform.

[0035] Since the Maven three-factor information is a unique identifier of a third-party software program, after determining multiple third-party software programs associated with the target application through the dependency tree file, the present application can distinguish different third-party software programs through the Maven three-factor information of each third-party software program.

[0036] Step S103: detecting whether the preset file contains a calling relationship between the target application program and the third-party software program according to the target program identifier and the element information.

[0037] In step S103, the preset file pre-records the element information of the third-party software program and the program identifiers of all application programs that have historical call records with the third-party software program.

[0038] Specifically, the preset file can be a database file deployed on a server and displayed on a display device. After a call relationship occurs between an app and an SDK, the preset file records the call relationship. Thus, administrators can determine which SDKs are called by an app and which apps call an SDK by consulting the preset file.

[0039] In an optional embodiment, Table 1 shows an example of a preset file:

[0040] Table 1

[0041] SDK three elements APP logo ABC Logo 1 EDF Logo 1 EDF Logo 2

[0042] As shown in Table 1, for the SDK whose three elements are ABC, it is only called by the APP identified by the program as ID 1. For the SDK whose three elements are EDF, it is called by both the APP identified by the program as ID 1 and the APP identified by the program as ID 2.

[0043] Step S104 : when it is detected that the preset file does not contain the calling relationship between the target application and the third-party software program, the calling relationship is updated into the preset file.

[0044] In step S104, after obtaining the program identifier of the APP and the three-element information of the SDK associated with the APP, the application management system will poll in the preset file to determine whether the calling relationship between these SDKs and the APP has been recorded. If there is a situation where the calling relationship between an SDK and the APP is missed, the application management system will promptly update the calling relationship between the SDK and the APP to the preset file, thereby avoiding the problem of missing SDKs in the process of managing SDKs.

[0045] Based on the contents of steps S101 to S104 above, it can be seen that in this application, a method of automatically determining all SDKs called by the application during operation is adopted through the dependency tree file of the application. First, the dependency tree file corresponding to the target application and the target program identifier of the target application are obtained. Then, the dependency tree file is parsed to obtain the element information of the third-party software program. Based on the target program identifier and the element information, it is detected whether the preset file contains the calling relationship between the target application and the third-party software program. Finally, when it is detected that the preset file does not contain the calling relationship between the target application and the third-party software program, the calling relationship is updated to the preset file. Among them, the dependency tree file is used to characterize the dependency relationship between the third-party software program and the target application. The third-party software program is the program called by the target application during operation. The third-party software program includes local software programs and remote software programs. The element information is the unique identifier of the third-party software program. The preset file pre-records the element information of the third-party software program and the program identifiers of all applications that have historical call records with the third-party software program.

[0046] From the above content, it can be seen that the present application determines all third-party software programs called by the application during operation through a dependency tree file, and records the calling relationship in a preset file, thereby achieving the purpose of automatically maintaining the calling relationship between the application and the third-party software program. Compared with the existing technology that uses manual methods to manage the calling relationship between the application and the third-party software program, the technical method of the present application not only reduces the cost of manual maintenance, but also improves the management efficiency of third-party software programs and applications.

[0047] It can be seen that through the technical solution of the present application, the purpose of automatically managing the calling relationship between the application and the third-party software program is achieved, thereby realizing the effect of improving the management efficiency of the third-party software program, and further solving the technical problem of low management efficiency in the existing technology when managing the calling relationship between the application and the third-party software program.

[0048] In an optional embodiment, the application management system executes a first command in an operating system on which the target application is installed to obtain a first dependency tree subfile, and uses the first dependency tree subfile as one of the dependency tree files. The first dependency tree subfile is used to represent the dependency relationship between the remote software program and the target application, as well as the dependency relationship between the first local software program and the target application. The first local software program is a program that includes code and resource files and has a direct dependency relationship with the target application.

[0049] Optional, Figure 2 FIG. 1 shows a flow chart of another optional application processing method according to an embodiment of the present application. Figure 2 As shown, the first command is the Gradle command ".. / gradlew -q dependencies > .. / script / depends.txt". By running this command on the operating system where the target application is installed, the application management system can obtain the first dependency tree file depends.txt. The first dependency tree file depends.txt is used to represent the dependency relationship between the remote SDK and the target application, as well as the dependency relationship between the first local SDK and the target application. The first local SDK is a local SDK in arr format that is introduced through a method other than artifact.add.

[0050] In an optional embodiment, the application management system obtains a second dependency tree subfile by executing a second command in the operating system, and uses the second dependency tree subfile as one of the dependency tree files. The second dependency tree subfile is used to represent the dependency relationship between the second local software program and the target application, as well as the dependency relationship between the third local software program and the target application. The second local software program is a program that does not include resource files, and the third local software program is a program that includes code and resource files and has an indirect dependency relationship with the target application.

[0051] Optional, such as Figure 2 As shown, the second command is the Gradle command ".. / gradlew anDep>.. / script / anDep.txt". By running the second command in the operating system, the application management system can obtain the second dependency tree file anDep.txt. The second dependency tree file anDep.txt is used to represent the dependency relationship between the second local SDK and the target application, as well as the dependency relationship between the third local SDK and the target application. The second local SDK is a local SDK in jar format, and the third local SDK is a local SDK in arr format introduced using the artifact.add method.

[0052] It should be noted that by running the first command and the second command, the application management system can automatically obtain the first dependency tree file and the second dependency tree file corresponding to the target application. Since the dependency tree file contains information about the SDK that has a dependency relationship with the target application, based on the dependency tree file, the application management system can determine all SDKs associated with the target application and ensure that no SDK is missed.

[0053] In an optional embodiment, the application management system parses the first dependency tree subfile to obtain element information of the remote software program, and parses the first dependency tree subfile and the second dependency tree subfile to obtain the storage path of the local software program, and then determines the element information of the local software program based on the storage path. The local software program includes a first local software program, a second local software program, and a third local software program.

[0054] Optional, such as Figure 2 As shown, by parsing the first dependency tree file depends.txt, the application management system can obtain the Maven three-element information of the remote SDK and the storage path of the first local SDK; by parsing the second dependency tree file anDep.txt, the application management system can obtain the storage path of the second local SDK and the storage path of the third local SDK.

[0055] In addition, the application management system also stores the Maven three-factor information of the remote SDK in the first file and the storage path information of the local SDKs (including the first local SDK, the second local SDK, and the third local SDK) in the second file. The file path of the first file can be script / output / remoteList.txt; the file path of the second file can be script / output / LocalList.txt.

[0056] In an optional embodiment, the application management system can determine information summary information of the local software program based on the storage path, and determine element information of the local software program based on the information summary information, wherein the information summary information is information obtained by calculating the local software program based on an information summary algorithm.

[0057] Optional, such as Figure 2 As shown, the information digest is the MD5 value of the local SDK. MD5 is a message digest algorithm, which can be understood as a cryptographic hash function, used to generate a 128-bit hash value as the information digest of the local SDK. Furthermore, after obtaining the MD5 value of the local SDK, the application management system can store the MD5 value in a third file, where the file path of the third file is script / output / MD5List.txt.

[0058] In addition, the application management system will also upload the MD5 value of the local SDK to the Maven interface. After receiving the MD5 value, the Maven interface will return the Maven three-factor information of the local SDK to the application management system based on the MD5 value.

[0059] In an optional embodiment, the application management system determines at least one program identifier corresponding to the element information from all program identifiers in the preset file, and detects whether there is a target program identifier in the at least one program identifier. When the target program identifier exists in the at least one program identifier, the application management system determines that the preset file contains a calling relationship between the target application and the third-party software program. When the target program identifier does not exist in the at least one program identifier, the application management system determines that the preset file does not contain a calling relationship between the target application and the third-party software program.

[0060] Optional, such as Figure 2 As shown, the application management system includes a matching notification module. The application management system will send all the Maven three-element information of the local SDK and the Maven three-element information of the remote SDK to the matching notification module, and will also send the target program identifier of the target application to the matching notification module.

[0061] Furthermore, the matching notification module can call the preset file and match the above-mentioned Maven three-element information with the Maven three-element information of the SDK recorded in the preset file. For example, if the element information of SDK1 recorded in the preset file is element information A, and the program identifier corresponding to element information A is program 1, it means that in the information recorded in the preset file, SDK1 is called by program 1. On this basis, if the application management system detects that the element information of the third-party software program associated with the target application 3 is also element information A, it means that the third-party software program is SDK1. At this time, the calling relationship between SDKA and the target application 3 has not been recorded in the preset file. Therefore, in order to ensure that all calling relationships of SDK1 are recorded, the application management system will also add the calling relationship between the target application 3 and SDK1 to the preset file.

[0062] It should be noted that when it is detected that the preset file does not contain the calling relationship between the target application and the third-party software program, the application management system will also generate an email and send it to the terminal device to remind the architect to manage the target application and the third-party software program in a timely manner.

[0063] In an optional embodiment, after updating the call relationship in the preset file, the application management system further detects whether the third-party software program has an anomaly. If the third-party software program has an anomaly, the application management system obtains the anomaly information of the third-party software program, determines the program identifier of the first application based on the element information of the third-party software program and the preset file, and finally generates a prompt message based on the anomaly information and the program identifier of the first application, and sends the prompt message to the terminal device. The first application is an application that has an associated relationship with the third-party software program.

[0064] Optionally, since when an SDK has an exception, the APP that calls the SDK will also be affected, therefore, in order to improve operation and maintenance efficiency and improve user experience, the application management system will determine all applications corresponding to the SDK (i.e., the first application) according to the preset file when it determines that an SDK has an exception, and read the program identifiers of these first applications from the preset file, and finally generate prompt information based on these program identifiers and the SDK's exception information, and send the prompt information to the terminal device in the form of an email to remind the operation and maintenance personnel. After receiving the prompt information, the operation and maintenance personnel can make corresponding processing for the corresponding application and SDK. For example, the technician immediately starts the process of repairing the SDK. When the SDK repair time is long, the operator suspends the use of the first application and promptly explains to the user to avoid unnecessary losses and user complaints as much as possible.

[0065] It can be seen that through the technical solution of this application, the purpose of automatic scanning of SDK usage is achieved, and the SDK scanning results are automatically managed, which can assist technical personnel in timely understanding the information of SDK-related applications when troubleshooting SDK problems, thereby improving operation and maintenance efficiency and improving user experience.

[0066] Example 2

[0067] According to an embodiment of the present application, a device for processing an application is also provided, wherein: Figure 3 is a schematic diagram of an optional application processing device according to an embodiment of the present application, such as Figure 3As shown, the device includes: an acquisition module 301, which is used to obtain a dependency tree file corresponding to the target application and a target program identifier of the target application, wherein the dependency tree file is used to characterize the dependency relationship between the third-party software program and the target application, and the third-party software program is a program called by the target application during operation, and the third-party software program includes a local software program and a remote software program; a parsing module 302, which is used to parse the dependency tree file and obtain element information of the third-party software program, wherein the element information is a unique identifier of the third-party software program; a detection module 303, which is used to detect whether a preset file contains a calling relationship between the target application and the third-party software program based on the target program identifier and the element information, wherein the preset file pre-records the element information of the third-party software program and the program identifiers of all applications that have historical calling records with the third-party software program; an updating module 304, which is used to update the calling relationship to the preset file when it is detected that the preset file does not contain the calling relationship between the target application and the third-party software program.

[0068] It should be noted that the above-mentioned acquisition module 301, analysis module 302, detection module 303 and update module 304 correspond to steps S101 to S104 in the above-mentioned embodiment 1. The examples and application scenarios implemented by the four modules and the corresponding steps are the same, but are not limited to the contents disclosed in the above-mentioned embodiment 1.

[0069] Optionally, the acquisition module further includes: a first acquisition unit and a first determination unit. The first acquisition unit is configured to acquire a first dependency tree sub-file by running a first command in an operating system on which a target application is installed, wherein the first dependency tree sub-file is used to characterize the dependency relationship between the remote software program and the target application, and the dependency relationship between the first local software program and the target application, wherein the first local software program is a program that includes code and resource files and has a direct dependency relationship with the target application; and the first determination unit is configured to use the first dependency tree sub-file as one of the dependency tree files.

[0070] Optionally, the acquisition module further includes: a second acquisition unit and a second determination unit. The second acquisition unit is configured to acquire a second dependency tree sub-file by running a second command in the operating system, wherein the second dependency tree sub-file is configured to represent the dependency relationship between the second local software program and the target application, and the dependency relationship between the third local software program and the target application, wherein the second local software program is a program that does not contain resource files, and the third local software program is a program that contains code and resource files and has an indirect dependency relationship with the target application; and the second determination unit is configured to use the second dependency tree sub-file as one of the dependency tree files.

[0071] Optionally, the parsing module further includes: a first parsing unit, a second parsing unit, and a third determining unit. The first parsing unit is configured to parse the first dependency tree subfile to obtain element information of the remote software program; the second parsing unit is configured to parse the first dependency tree subfile and the second dependency tree subfile to obtain storage paths of local software programs, wherein the local software programs include a first local software program, a second local software program, and a third local software program; and the third determining unit is configured to determine element information of the local software program based on the storage paths.

[0072] Optionally, the third determination unit further includes: a first determination submodule and a second determination submodule. The first determination submodule is configured to determine information digest information of the local software program based on the storage path, wherein the information digest information is information obtained by calculating the local software program based on an information digest algorithm; and the second determination submodule is configured to determine element information of the local software program based on the information digest information.

[0073] Optionally, the detection module further includes: a fourth determination unit, a detection unit, a fifth determination unit, and a sixth determination unit. The fourth determination unit is configured to determine at least one program identifier corresponding to the element information from all program identifiers in the preset file; the detection unit is configured to detect whether a target program identifier exists in the at least one program identifier; the fifth determination unit is configured to determine that the preset file contains a calling relationship between the target application and the third-party software program if the target program identifier exists in the at least one program identifier; and the sixth determination unit is configured to determine that the preset file does not contain a calling relationship between the target application and the third-party software program if the target program identifier does not exist in the at least one program identifier.

[0074] Optionally, the application processing device further includes: a first acquisition module, a determination module, and a generation module. The first acquisition module is configured to acquire exception information of the third-party software program when an exception occurs in the third-party software program; the determination module is configured to determine a program identifier of the first application based on element information of the third-party software program and a preset file, wherein the first application is an application associated with the third-party software program; and the generation module is configured to generate prompt information based on the exception information and the program identifier of the first application, and send the prompt information to the terminal device.

[0075] Example 3

[0076] According to an embodiment of the present application, a computer-readable storage medium is further provided, in which a computer program is stored. The computer program is configured to execute the processing method of the application in the above-mentioned embodiment 1 when running.

[0077] Example 4

[0078] According to an embodiment of the present application, an electronic device embodiment is also provided, wherein: Figure 4 is a schematic diagram of an optional electronic device according to an embodiment of the present application, such as Figure 4 As shown, the electronic device includes a processor, a memory, and a program stored in the memory and capable of running on the processor. When the processor executes the program, the following steps are implemented:

[0079] Obtain a dependency tree file corresponding to the target application and a target program identifier of the target application, wherein the dependency tree file is used to characterize the dependency relationship between the third-party software program and the target application, the third-party software program is a program called by the target application during operation, and the third-party software program includes a local software program and a remote software program; parse the dependency tree file to obtain element information of the third-party software program, wherein the element information is a unique identifier of the third-party software program; detect whether the preset file contains a calling relationship between the target application and the third-party software program based on the target program identifier and the element information, wherein the preset file pre-records the element information of the third-party software program and the program identifiers of all applications that have historical calling records with the third-party software program; when it is detected that the preset file does not contain a calling relationship between the target application and the third-party software program, update the calling relationship to the preset file.

[0080] Optionally, when executing the program, the processor also implements the following steps: obtaining a first dependency tree sub-file by running a first command in an operating system on which a target application is installed, wherein the first dependency tree sub-file is used to characterize the dependency relationship between the remote software program and the target application, and the dependency relationship between the first local software program and the target application, the first local software program being a program that includes code and resource files and has a direct dependency relationship with the target application; and using the first dependency tree sub-file as one of the dependency tree files.

[0081] Optionally, when executing the program, the processor further implements the following steps: obtaining a second dependency tree sub-file by running a second command in the operating system, wherein the second dependency tree sub-file is used to characterize the dependency relationship between the second local software program and the target application, and the dependency relationship between the third local software program and the target application, the second local software program is a program that does not contain resource files, and the third local software program is a program that contains code and resource files and has an indirect dependency relationship with the target application; and using the second dependency tree sub-file as one of the dependency tree files.

[0082] Optionally, when executing the program, the processor also implements the following steps: parsing the first dependency tree sub-file to obtain element information of the remote software program; parsing the first dependency tree sub-file and the second dependency tree sub-file to obtain the storage path of the local software program, wherein the local software program includes a first local software program, a second local software program and a third local software program; determining the element information of the local software program based on the storage path.

[0083] Optionally, when executing the program, the processor further implements the following steps: determining information summary information of the local software program based on the storage path, wherein the information summary information is information obtained by calculating the local software program based on an information summary algorithm; and determining element information of the local software program based on the information summary information.

[0084] Optionally, when executing the program, the processor further implements the following steps: determining at least one program identifier corresponding to the element information from all program identifiers in the preset file; detecting whether there is a target program identifier in at least one program identifier; if the target program identifier exists in at least one program identifier, determining that the preset file contains a calling relationship between the target application and the third-party software program; if the target program identifier does not exist in at least one program identifier, determining that the preset file does not contain a calling relationship between the target application and the third-party software program.

[0085] Optionally, the processor also implements the following steps when executing the program: after updating the call relationship to the preset file, when an exception occurs in the third-party software program, obtaining exception information of the third-party software program; determining the program identifier of the first application based on the element information of the third-party software program and the preset file, wherein the first application is an application that has an associated relationship with the third-party software program; generating prompt information based on the exception information and the program identifier of the first application, and sending the prompt information to the terminal device.

[0086] The serial numbers of the above embodiments of the present application are for description only and do not represent the advantages or disadvantages of the embodiments.

[0087] In the above embodiments of the present application, the description of each embodiment has its own focus. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.

[0088] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. Among them, the device embodiments described above are only exemplary. For example, the division of the units can be a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of units or modules, which can be electrical or other forms.

[0089] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple units. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0090] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0091] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions for enabling a computer device (which can be a personal computer, a server or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.

[0092] The above is only a preferred embodiment of the present application. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present application. These improvements and modifications should also be regarded as the scope of protection of the present application.

Claims

1. A method for processing an application, characterized in that: include: Obtaining a dependency tree file corresponding to a target application and a target program identifier of the target application, wherein the dependency tree file is used to represent a dependency relationship between a third-party software program and the target application, the third-party software program being a program called by the target application during operation, and the third-party software program including a local software program and a remote software program; parsing the dependency tree file to obtain element information of the third-party software program, wherein the element information is a unique identifier of the third-party software program; detecting, based on the target program identifier and the element information, whether a preset file contains a calling relationship between the target application and the third-party software program, wherein the preset file pre-records the element information of the third-party software program and the program identifiers of all applications that have historical calling records with the third-party software program; and updating the calling relationship in the preset file when it is detected that the preset file does not contain the calling relationship between the target application and the third-party software program; Obtaining a dependency tree file corresponding to the target application includes: obtaining a first dependency tree subfile by running a first command in an operating system on which the target application is installed, wherein the first dependency tree subfile is used to represent a dependency relationship between the remote software program and the target application, and a dependency relationship between a first local software program and the target application, the first local software program being a program that includes code and resource files and has a direct dependency relationship with the target application; and using the first dependency tree subfile as one of the dependency tree files; Among them, detecting whether the calling relationship between the target application and the third-party software program is recorded in the preset file based on the target program identifier and the element information includes: determining at least one program identifier corresponding to the element information from all program identifiers in the preset file; detecting whether the target program identifier exists in the at least one program identifier; if the target program identifier exists in the at least one program identifier, determining that the preset file contains the calling relationship between the target application and the third-party software program; if the target program identifier does not exist in the at least one program identifier, determining that the preset file does not contain the calling relationship between the target application and the third-party software program.

2. The method according to claim 1, characterized in that Get the dependency tree file corresponding to the target application, including: Obtaining a second dependency tree subfile by running a second command in the operating system, wherein the second dependency tree subfile is used to represent a dependency relationship between a second local software program and the target application, and a dependency relationship between a third local software program and the target application, wherein the second local software program is a program that does not include the resource file, and the third local software program is a program that includes the code and the resource file and has an indirect dependency relationship with the target application; The second dependency tree sub-file is used as one of the dependency tree files.

3. The method according to claim 2, characterized in that Parsing the dependency tree file to obtain element information of the third-party software program includes: Parsing the first dependency tree sub-file to obtain element information of the remote software program; Parsing the first dependency tree subfile and the second dependency tree subfile to obtain storage paths of the local software programs, wherein the local software programs include the first local software program, the second local software program, and the third local software program; The element information of the local software program is determined according to the storage path.

4. The method according to claim 3, characterized in that Determining element information of the local software program according to the storage path includes: Determining information summary information of the local software program according to the storage path, wherein the information summary information is information obtained by calculating the local software program according to an information summary algorithm; The essential information of the local software program is determined according to the information summary information.

5. The method according to claim 1, characterized in that After updating the calling relationship into the preset file, the method further includes: When an exception occurs in the third-party software program, obtaining exception information of the third-party software program; determining a program identifier of a first application program according to the element information of the third-party software program and the preset file, wherein the first application program is an application program associated with the third-party software program; Prompt information is generated according to the abnormal information and the program identifier of the first application, and the prompt information is sent to the terminal device.

6. An application processing device, used to implement the application processing method according to claim 1, characterized in that: include: an acquisition module, configured to acquire a dependency tree file corresponding to a target application and a target program identifier of the target application, wherein the dependency tree file is used to characterize a dependency relationship between a third-party software program and the target application, the third-party software program being a program called by the target application during operation, and the third-party software program including a local software program and a remote software program; a parsing module, configured to parse the dependency tree file to obtain element information of the third-party software program, wherein the element information is a unique identifier of the third-party software program; a detection module, configured to detect, based on the target program identifier and the element information, whether a preset file contains a call relationship between the target application and the third-party software program, wherein the preset file pre-records the element information of the third-party software program and the program identifiers of all application programs that have historical call records with the third-party software program; The updating module is configured to update the calling relationship between the target application and the third-party software program into the preset file when it is detected that the preset file does not contain the calling relationship between the target application and the third-party software program.

7. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a computer program, wherein the computer program is configured to execute the method for processing the application program according to any one of claims 1 to 5 through the device where the computer-readable storage medium is located when the computer program is run.

8. An electronic device, characterized in that: The electronic device includes one or more processors; A memory for storing one or more programs, which, when executed by the one or more processors, enables the one or more processors to implement a method for running the program, wherein the program is configured to execute the processing method of the application described in any one of claims 1 to 5 by the processor at runtime.

Images