Data processing method, electronic device, and storage medium

Abstract

Embodiments of the present application disclose a data processing method, an electronic device and a storage medium, including: obtaining identification information of a target application; checking the identification information; when the identification information passes the check, detecting an application path of the target application; when it is detected that the application path meets a preset condition, processing crash data of the target application by using a crash data processing function, which can improve the accuracy of collecting the crash data and thus improve the efficiency of repairing the crashed application.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to a data processing method, an electronic device, and a storage medium. Background Technology

[0002] During the operation of system programs or applications, crashes often occur due to various reasons, such as application installation errors, system vulnerabilities, virus infection, or operational mistakes. When a crash occurs, it is necessary to collect crash diagnostic information that can help resolve the crash issue, and analyze this information to fix the problem.

[0003] However, when plugins are added to an application, it is very easy for the application to crash. This crash data is meaningless for monitoring the application's crash rate, resulting in inaccurate crash data and reducing the efficiency of repairing crashed applications. Summary of the Invention

[0004] This application provides a data processing method, an electronic device, and a storage medium that can improve the accuracy of collecting crash data, thereby improving the efficiency of repairing crashed applications.

[0005] This application provides a data processing method, including:

[0006] Obtain the identification information of the target application;

[0007] The identification information is verified;

[0008] When the identification information passes the verification, the application path of the target application is detected;

[0009] When the application path is detected to meet the preset conditions, the crash data of the target application is processed using a crash data processing function.

[0010] Optionally, in some embodiments, when the application path is detected to meet preset conditions, processing the crash data of the target application using a crash data processing function includes:

[0011] When the application path is detected to meet the preset conditions, the target application is determined to be a legitimate application;

[0012] Obtain the crash data handling function corresponding to the legitimate application;

[0013] Based on the crash data processing function, the crash data of the target application is collected and uploaded to the server.

[0014] Optionally, in some embodiments, determining the target application as a legitimate application when the application path is detected to meet preset conditions includes:

[0015] Iterate through the link library paths corresponding to the target application;

[0016] Based on the link library path, detect whether the target application carries a plug-in program;

[0017] When it is detected that the target application does not carry any plug-in programs, the target application is determined to be a legitimate application.

[0018] Optionally, in some embodiments, detecting whether the target application carries a plug-in program based on the link library path includes:

[0019] If the link library corresponding to the link library path is not of a preset type, it is determined that the target application does not carry any plug-in program, or;

[0020] When the link library corresponding to the link library path is identified as a preset type, the signature information of the target application is checked to see if it conforms to preset rules; when the signature information is detected to conform to preset rules, it is determined that the target application does not carry any plug-in programs.

[0021] Optionally, in some embodiments, it further includes:

[0022] When the link library corresponding to the link library path is identified as a preset type and the signature information does not conform to the preset rules, it is determined that the target application carries a plug-in program.

[0023] Optionally, in some embodiments, it further includes:

[0024] When the application path is detected to not meet the preset conditions, the crash data of the target application is processed using a preset function.

[0025] Optionally, in some embodiments, when the application path is detected to not meet preset conditions, processing the crash data of the target application using a preset function includes:

[0026] When the application path is detected to not meet the preset conditions, a preset function is triggered;

[0027] Based on the preset function, the identification information and link library information of the target application are collected;

[0028] The collected identification information and link library information are uploaded to the server.

[0029] Optionally, in some embodiments, verifying the identification information includes:

[0030] Verify the unique identifier and signature information of the target application.

[0031] Accordingly, this application also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program as described in any of the methods above.

[0032] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps of any of the methods described above.

[0033] This application's embodiments, after obtaining the target application's identification information, verify the identification information. Then, when the identification information passes verification, the application path of the target application is detected. Finally, when the application path is detected to meet preset conditions, a crash data processing function is used to process the target application's crash data. The data processing scheme provided in this application uses identification information and the application path to determine whether the target application meets preset conditions. When the application path is detected to meet the preset conditions, a crash data processing function is used to process the target application's crash data. This improves the accuracy of collected crash data, thereby increasing the efficiency of crash application repair. Attached Figure Description

[0034] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0035] Figure 1 This is a flowchart illustrating the data processing method provided in an embodiment of this application;

[0036] Figure 2 This is another schematic flowchart of the data processing method provided in the embodiments of this application;

[0037] Figure 3 This is a schematic diagram of the structure of the data processing apparatus provided in the embodiments of this application;

[0038] Figure 4 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0039] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0040] This application provides a data processing method, apparatus, electronic device, and storage medium.

[0041] Specifically, the data processing device can be integrated into a server or a terminal. The server can include a stand-alone server or a distributed server, or a server cluster consisting of multiple servers. The terminal can include a mobile phone, tablet computer, or personal computer (PC).

[0042] The following sections provide detailed descriptions of each example. It should be noted that the order in which the embodiments are described is not intended to limit the priority of the embodiments.

[0043] A data processing method includes: obtaining identification information of a target application, verifying the identification information, detecting the application path of the target application when the identification information passes the verification, and processing the crash data of the target application using a crash data processing function when the detected application path meets preset conditions.

[0044] Please see Figure 1 , Figure 1 This is a flowchart illustrating the data processing method provided in an embodiment of this application. The specific flow of this data processing method can be as follows:

[0045] 101. Obtain the identification information of the target application.

[0046] Specifically, the terminal runs an operating system, and applications run on that operating system. An operating system (OS) is a computer program that manages and controls the terminal's hardware and software resources. It is the most basic system software that runs directly on the terminal's bare metal, and applications require the support of the operating system to run. The operating system can be a Windows operating system, a Linux operating system, or a desktop operating system such as Mac OS (Apple's desktop operating system), or a mobile operating system such as iOS (Apple's mobile operating system) or Android. Optionally, the target application can be a social application, an email application, or a game application. Social applications include instant messaging applications, SNS (Social Network Service) applications, or live streaming applications, where identification information is used to uniquely identify an application. Identification information can be a string containing at least one character from numbers, letters, and symbols.

[0047] 102. Verify the identification information.

[0048] In this application, verifying the identification information can be understood as verifying the legality of the identification information. Specifically, it can detect whether the identification information has been tampered with, or whether the content of the identification information is legal. If the identification information passes the verification, step 103 is executed; if the identification information fails the verification, it can be determined that the target application carries illegal programs, such as plug-ins. In this case, when the target application crashes, the crash data of the target application is not collected to avoid reducing the accuracy of the collected crash data, thereby improving the efficiency of repairing the crashed application.

[0049] Optionally, in some embodiments, the identification information may specifically include a unique identifier and signature information. That is, verifying the identification information may specifically involve verifying the unique identifier and signature information of the target application.

[0050] The unique identifier, also known as the universally unique identifier (UUID), consists of 32 hexadecimal digits arranged in five hyphens, in the format 8-4-4-4-12. The signature information can be a digital signature, which is data appended to a data unit or a cryptographic transformation of that data unit. This data or transformation allows the recipient of the data unit to verify its origin and integrity, and to protect the data from forgery by others (such as the recipient). It is a method of signing electronic messages, and a signed message can be transmitted over a communication network. Digital signatures can be obtained using both public-key and private-key cryptography, but are primarily based on public-key cryptography. Digital signatures include both ordinary and special types. Ordinary digital signature algorithms include RSA, ElGamal, Fiat-Shamir, Guillou-Quisquarter, Schnorr, Ong-Schnorr-Shamir, DES / DSA, elliptic curve digital signature algorithms, and finite automata digital signature algorithms. Special digital signatures include blind signatures, proxy signatures, group signatures, non-repudiation signatures, fair blind signatures, threshold signatures, and signatures with message recovery capabilities, which are closely related to the specific application environment.

[0051] 103. When the identification information passes the verification, detect the application path of the target application.

[0052] Optionally, the application path refers to the folder route through which the application's files are stored. This application path can be divided into absolute path and relative path. An absolute path refers to the path starting from the root folder and beginning with "\", while a relative path refers to the path starting from the current folder. To improve the accuracy of subsequent determination of whether the target application carries plug-ins, in some embodiments of this application, the absolute path of the target application is detected.

[0053] Optionally, it can be checked whether the naming rules of the application path meet the set conditions, such as whether the string suffix corresponding to the application path is A. If the string suffix corresponding to the application path is A, then the target application is determined to be a legitimate application, and then step 104 is executed. That is, optionally, the step "when the identification information passes the verification, detect the application path of the target application" can specifically include:

[0054] (11) When the application path is detected to meet the preset conditions, the target application is determined to be a legitimate application;

[0055] (12) Obtain the crash data handling function corresponding to the legitimate application;

[0056] (13) Based on the crash data processing function, collect the crash data of the target application and upload the crash data to the server.

[0057] Optionally, in some embodiments, the application path can be a link library path, that is, the step "when the application path is detected to meet the preset conditions, determine that the target application is a legitimate application" may specifically include:

[0058] (21) Traverse the link library paths corresponding to the target application;

[0059] (22) Detect whether the target application carries any plug-in programs based on the link library path;

[0060] (23) When it is detected that the target application does not carry any plug-in program, the target application is determined to be a legitimate application.

[0061] Linked libraries are divided into static linked libraries and dynamic linked libraries. Static linked libraries directly link the function code used in the (lib) file into the target program, and no other library files are needed when the program runs. Dynamic linking links the file module (DLL) where the called function is located and the location of the called function in the file into the target program. When the program runs, it searches for the corresponding function code in the DLL, so it requires the support of the corresponding DLL file.

[0062] Taking dynamic link libraries as an example, in the current iOS environment, customized plugins generally exist in the form of dylibs. Therefore, by detecting whether the dynamic link library is a dylib, it can be determined whether the target application carries a plugin. That is, optionally, the step "detect whether the target application carries a plugin based on the link library path" can specifically include:

[0063] (31) If the link library corresponding to the identified link library path is not of the preset type, it is determined that the target application does not carry any plug-in program;

[0064] (32) When the link library corresponding to the link library path is identified as a preset type, check whether the signature information of the target application conforms to the preset rules; when the signature information is detected to conform to the preset rules, it is determined that the target application does not carry any plug-in program.

[0065] For example, when the link library path is identified as a dll type, it can be determined that the target application does not carry any plug-ins; when the link library path is identified as a dylib type, it checks whether the signature information of the target application conforms to the preset rules. When it is detected that the signature information has been tampered with (i.e. does not conform to the preset rules), it is determined that the target application does not carry any plug-ins.

[0066] It's important to note that "cheating software" generally refers to an application that, during system operation, is able to attach itself to another application's space through a certain event (common trigger events include keyboard, mouse, and message triggers). The purpose of this attachment is usually to change the way the attached program operates. Common examples include game cheating software, which integrates cheat programs into the game program, intercepting and modifying data sent by the game to the game server to enhance various functions. Internet client / server communication typically uses the TCP / IP communication protocol, and data exchange is achieved through the transmission of IP packets. Generally, when a client sends requests to the server, such as movement or combat commands, it exchanges data with the server in the form of packets. The main application principle is to use packet capture tools and packet sniffing tools to submit fake parameters to the game itself or the game server, thereby altering the character's abilities in the game. When an application is plugged with cheating software, it is highly likely to cause the application to crash.

[0067] Optionally, if the linked library corresponding to the linked library path is identified as a preset type and the signature information does not conform to the preset rules, then it is determined that the target application carries a plug-in program.

[0068] Optionally, if the string suffix corresponding to the application path is not A, then the application path is determined to not meet the preset conditions. In this case, a preset function can be used to process the crash data of the target application. This preset function can collect corresponding crash data according to the type of crash of the target application, such as collecting the unique identifier, signature information, and hit link library path of the target application. At the same time, it can collect information about the plug-in program, which may include the content modified by the plug-in program, the time and duration of the operation, etc. The specific settings can be made according to the actual situation. That is, optionally, in some embodiments, the step "when the application path is detected to not meet the preset conditions, use a preset function to process the crash data of the target application" can be specifically as follows: when the application path is detected to not meet the preset conditions, trigger the preset function; based on the preset function, collect the identification information and link library information of the target application; and upload the collected identification information and link library information to the server.

[0069] 104. When the application path is detected to meet the preset conditions, the crash data of the target application is processed using the crash data processing function.

[0070] Optionally, in some embodiments, this application determines applications that do not carry plug-ins as legitimate applications. When the target application is a legitimate application, the crash data processing function corresponding to the legitimate application is used to collect the crash data of the target application and upload the crash data to the server. The crash data can be crash stack data, which describes the specific circumstances of the crash and may include the time of the crash, the line number of the specified application code where the crash occurred, the client identifier or user account of the application, the system version number, etc.

[0071] The crash data processing function can collect corresponding crash data based on the type of crash in the target application. For example, a crash caused by a page error can collect page display information; a crash caused by user operation can collect user operation information on the current page and detailed execution information of Fragment system callbacks; a crash caused by a database error can collect detailed logs such as database opening and closing; and a crash caused by insufficient disk space can collect information on user disk usage.

[0072] In this application embodiment, after obtaining the identification information of the target application, the identification information is verified. When the identification information passes the verification, the application path of the target application is detected. When the application path is found to meet preset conditions, a crash data processing function is used to process the crash data of the target application. The data processing scheme provided by this application uses identification information and application path to determine whether the target application meets preset conditions. When the application path is detected to meet preset conditions, a crash data processing function is used to process the crash data of the target application. This improves the accuracy of crash data collection and thus improves the efficiency of crash application repair.

[0073] To better understand the data processing methods provided in this application, please refer to Figure 2 , Figure 2 This is another flowchart illustrating the data processing method provided in this application. The data processing method provided in this application is a scheme for distinguishing and processing crash data when an application with plug-ins crashes.

[0074] In this application's solution, the crash collection framework is defined as an open-source or commercial package that encapsulates crash collection functionality and provides it to applications. 1. When a user clicks the application icon, the target application is launched. 2. The target application launches and begins running the crash collection framework. The framework listens for system crash exception ports and registers an exception handling function. This function receives crash data information passed by the system's exception handling function when the application crashes. 3. Obtain the application's unique identifier from the target application's information. 4. Compare the target application's unique identifier with the correct string. 5. If the strings do not match, the target application's code has been modified, indicating the presence of a cheat program. Proceed to step 13. 6. Obtain the developer account information from the target application's signature information. 7. Determine if the developer account information in the signature information matches the developer's own account. If not, the target application is considered to contain a cheat program. Proceed to step 13. 8. Obtain the paths of all library files that need to be loaded in the target application and iterate through them, starting with the first file path. 9. Iterate through the next library file path. 10. Based on the file path, determine if the file extension is ".dylib". If it is, proceed to step 6; otherwise, proceed to step 4. 11. Based on the file path, determine if it contains ".app". If it does, determine that the target application contains a cheat program and proceed to step 8; otherwise, proceed to step 4. 12. If all file paths have been traversed, but none of the conditions in steps 5 and 6 have been met, then it is determined that the target application does not contain a cheat program. Proceed to step 9.

[0075] 13. If the target application contains cheats, register a custom exception handling function. This custom exception handling function will replace the exception handling function registered by the crash collection framework. This function is used to receive crash data information passed by the system exception handling function when the application crashes, and to collect cheat information. 14. End the startup process. 15. When the target application crashes, the system exception capture mechanism sends the exception information to the exception handling function registered by the target application. 16. If the target application contains cheats, since the custom exception handling function is registered after the exception handling function of the crash collection framework, it will receive the exception information first and collect both crash data and cheat information. After collection, the process ends to prevent the crash collection framework from reporting the crash data. 17. Collect the unique identifier of the target application. 18. Collect the signature information of the target application. 19. Collect the target application's hit link library paths. 20. Execute step 22. 21. If the target application does not contain cheats, the system exception capture mechanism will directly pass the exception information to the exception handling function of the crash collection framework, where crash data will be collected. 22. Upload the collected data to the server.

[0076] To facilitate better implementation of the data processing method of this application embodiment, this application embodiment also provides a data processing apparatus (hereinafter referred to as the processing apparatus) based on the above-described data processing method. The meanings of the terms are the same as in the above-described data processing method, and specific implementation details can be found in the description of the method embodiment.

[0077] Please see Figure 3 , Figure 3 This is a schematic diagram of the structure of a data processing device provided in an embodiment of this application. The processing device may include an acquisition module 201, a verification module 202, a detection module 203, and a processing module 204, which may be as follows:

[0078] The acquisition module 201 is used to acquire the identification information of the target application.

[0079] The identification information is used to uniquely identify an application. The identification information can be a string containing at least one of the following characters: numbers, letters, and symbols.

[0080] The verification module 202 is used to verify the identification information.

[0081] In this application, verifying the identification information can be understood as verifying the legality of the identification information. Specifically, it can detect whether the identification information has been tampered with, or whether the content of the identification information is legal. If the identification information passes the verification, the detection module 203 executes the corresponding steps. If the identification information fails the verification, it can be determined that the target application carries an illegal program, such as a plug-in program. In this case, when the target application crashes, the crash data of the target application will not be collected to avoid reducing the accuracy of the collected crash data, thereby improving the efficiency of repairing the crashed application.

[0082] The detection module 203 is used to detect the application path of the target application when the identification information passes the verification.

[0083] Optionally, it can detect whether the naming rules of the application path meet the set conditions, such as whether the string suffix corresponding to the application path is A. If the string suffix corresponding to the application path is A, then the target application is determined to be a valid application, and then the processing module 204 executes the corresponding steps.

[0084] Optionally, in some embodiments, the detection module 203 may specifically include:

[0085] The determining unit is used to determine the target application as a legitimate application when the application path is detected to meet preset conditions;

[0086] The acquisition unit is used to acquire the crash data processing function corresponding to the legitimate application.

[0087] The acquisition unit is used to acquire crash data of the target application based on the crash data processing function;

[0088] The upload unit is used to upload crash data to the server.

[0089] Optionally, in some embodiments, the determining unit may specifically include:

[0090] Traverse sub-units to iterate through the link library paths corresponding to the target application;

[0091] The detection subunit is used to detect whether the target application carries any plug-ins based on the link library path.

[0092] The determination subunit is used to determine that the target application is a legitimate application when it is detected that the target application does not carry any plug-ins.

[0093] Optionally, in some embodiments, the determining subunit may be specifically used to: determine that the target application does not carry a plug-in program when the link library corresponding to the identified link library path is not a preset type; detect whether the signature information of the target application conforms to a preset rule when the link library corresponding to the identified link library path is a preset type; and determine that the target application does not carry a plug-in program when the signature information conforms to the preset rule.

[0094] The processing module 204 is used to process the crash data of the target application using a crash data processing function when the application path is detected to meet the preset conditions.

[0095] The crash data processing function can collect corresponding crash data based on the type of crash in the target application. For example, a crash caused by a page error can collect page display information; a crash caused by user operation can collect user operation information on the current page and detailed execution information of Fragment system callbacks; a crash caused by a database error can collect detailed logs such as database opening and closing; and a crash caused by insufficient disk space can collect information on user disk usage.

[0096] In this application embodiment, after obtaining the identification information of the target application, the identification information is verified. When the identification information passes the verification, the application path of the target application is detected. When the application path is found to meet preset conditions, a crash data processing function is used to process the crash data of the target application. The data processing scheme provided by this application uses identification information and application path to determine whether the target application meets preset conditions. When the application path is detected to meet preset conditions, a crash data processing function is used to process the crash data of the target application. This improves the accuracy of crash data collection and thus improves the efficiency of crash application repair.

[0097] Furthermore, embodiments of this application also provide an electronic device, such as... Figure 4 As shown, it illustrates a structural schematic diagram of the electronic device involved in the embodiments of this application, specifically:

[0098] The electronic device may include components such as a processor 301 with one or more processing cores, a memory 302 with one or more computer-readable storage media, a power supply 303, and an input unit 304. Those skilled in the art will understand that... Figure 4 The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein:

[0099] The processor 301 is the control center of the electronic device. It connects various parts of the electronic device via various interfaces and lines, and performs various functions and processes data by running or executing software programs and / or modules stored in the memory 302, and by calling data stored in the memory 302, thereby providing overall monitoring of the electronic device. Optionally, the processor 301 may include one or more processing cores; preferably, the processor 301 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 301.

[0100] The memory 302 can be used to store software programs and modules. The processor 301 executes various functional applications and data processing by running the software programs and modules stored in the memory 302. The memory 302 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 302 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 302 may also include a memory controller to provide the processor 301 with access to the memory 302.

[0101] The electronic device also includes a power supply 303 that supplies power to various components. Preferably, the power supply 303 can be logically connected to the processor 301 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 303 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0102] The electronic device may also include an input unit 304, which can be used to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal inputs related to user settings and function control.

[0103] Although not shown, the electronic device may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 301 in the electronic device loads the executable files corresponding to the processes of one or more applications into the memory 302 according to the following instructions, and the processor 301 runs the applications stored in the memory 302 to realize various functions, as follows:

[0104] Obtain the identification information of the target application, verify the identification information, and when the identification information passes the verification, detect the application path of the target application. When the application path is detected to meet the preset conditions, use the crash data processing function to process the crash data of the target application.

[0105] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0106] In this application embodiment, after obtaining the identification information of the target application, the identification information is verified. When the identification information passes the verification, the application path of the target application is detected. When the application path is found to meet preset conditions, a crash data processing function is used to process the crash data of the target application. The data processing scheme provided by this application uses identification information and application path to determine whether the target application meets preset conditions. When the application path is detected to meet preset conditions, a crash data processing function is used to process the crash data of the target application. This improves the accuracy of crash data collection and thus improves the efficiency of crash application repair.

[0107] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0108] Therefore, embodiments of this application provide a storage medium storing a plurality of instructions that can be loaded by a processor to execute steps in any of the data processing methods provided in embodiments of this application. For example, the instructions can execute the following steps:

[0109] Obtain the identification information of the target application, verify the identification information, and when the identification information passes the verification, detect the application path of the target application. When the application path is detected to meet the preset conditions, use the crash data processing function to process the crash data of the target application.

[0110] For details on the implementation of each of the above operations, please refer to the previous examples, which will not be repeated here.

[0111] The storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0112] Since the instructions stored in the storage medium can execute the steps of any of the data processing methods provided in the embodiments of this application, the beneficial effects that any of the data processing methods provided in the embodiments of this application can achieve can be realized. For details, please refer to the previous embodiments, which will not be repeated here.

[0113] The data processing method, apparatus, electronic device, and storage medium provided in the embodiments of this application have been described in detail above. Specific examples have been used to illustrate the principles and implementation methods of this application. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of this application. At the same time, for those skilled in the art, there will be changes in the specific implementation methods and application scope based on the ideas of this application. Therefore, the content of this specification should not be construed as a limitation of this application.

Claims

1. A data processing method, characterized in that, include: Obtain the identification information of the target application; The identification information is verified; When the identification information passes the verification, the application path of the target application is detected; When the application path is detected to meet preset conditions, a crash data processing function is used to process the crash data of the target application, specifically including: When the application path is detected to meet the preset conditions, the target application is determined to be a legitimate application; Obtain the crash data handling function corresponding to the legitimate application; Based on the crash data processing function, the crash data of the target application is collected and uploaded to the server; The step of determining the target application as a legitimate application when the application path is detected to meet preset conditions includes: Iterate through the link library paths corresponding to the target application; Based on the link library path, detect whether the target application carries a plug-in program; When it is detected that the target application does not carry any plug-in programs, the target application is determined to be a legitimate application.

2. The method according to claim 1, characterized in that, The step of detecting whether the target application carries a plug-in program based on the link library path includes: If the link library corresponding to the link library path is not of a preset type, it is determined that the target application does not carry any plug-in program. When the link library corresponding to the link library path is identified as a preset type, the signature information of the target application is checked to see if it conforms to preset rules; when the signature information is detected to conform to preset rules, it is determined that the target application does not carry any plug-in programs.

3. The method according to claim 2, characterized in that, Also includes: When the link library corresponding to the link library path is identified as a preset type and the signature information does not conform to the preset rules, it is determined that the target application carries a plug-in program.

4. The method according to claim 1, characterized in that, Also includes: When the application path is detected to not meet the preset conditions, the crash data of the target application is processed using a preset function.

5. The method according to claim 4, characterized in that, When the application path is detected to not meet the preset conditions, the crash data of the target application is processed using a preset function, including: When the application path is detected to not meet the preset conditions, a preset function is triggered; Based on the preset function, the identification information and link library information of the target application are collected; The collected identification information and link library information are uploaded to the server.

6. The method according to claim 1, characterized in that, The verification of the identification information includes: Verify the unique identifier and signature information of the target application.

7. An electronic device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein, When the processor executes the program, it implements the steps of the data processing method as described in any one of claims 1-6.

8. A computer-readable storage medium, characterized in that, It stores a computer program thereon, wherein the computer program, when executed by a processor, implements the steps of the data processing method as described in any one of claims 1-6.

Images