IOS application crash repair method and device, equipment and storage medium

By listening and parsing iOS app crash events, dynamic and automatic fixes resolve the problem of iOS app crashes, improving the user experience, and avoiding crashes during waiting for the new version to be reviewed.

CN119045857APending Publication Date: 2024-11-29SICHUAN SHENZHOUXING NETWORK CAR-HAILING SERVICE CO LTD
View PDF 0 Cites 1 Cited by

Patent Information

Application Number
CN202411139975.2
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-19
Publication Date
2024-11-29

AI Technical Summary

Technical Problem

When an iOS application crashes, the existing technology needs to wait for the new version to be reviewed, resulting in users still encountering crash problems while waiting, affecting the user experience.

Method used

By listening to application crash events, recording crash logs, parsing crash details, determining whether it is a startup crash, and dynamically automatically repair it based on the crash type and cause.

Benefits of technology

It realizes timely repair of crash events, ensures the availability of users' APP, and avoids the tedious process of waiting for the new version to review.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119045857A_ABST
    Figure CN119045857A_ABST
Patent Text Reader

Abstract

The invention discloses an iOS application crash repair method and device, equipment and a storage medium, and relates to the technical field of computers, the method comprises the steps of recording a crash log of a crash event when it is monitored that the crash event occurs in an application program; when the application program is started again, the crash log is analyzed, crash detail information of the crash event is obtained, and the crash detail information comprises a crash type and a crash reason; on the basis of the crash detail information, whether the crash event is a preset startup crash or not is judged, and the startup crash means that the application program crashes in the startup process; if the crash event is the starting crash event, repairing the crash event based on the crash detail information. When it is monitored that the crash of the application program belongs to the starting crash, automatic repair of the crash event is achieved according to the information such as the crash type and the crash reason, and therefore the crash can be repaired in time, and the availability of the APP used by a user is guaranteed.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to an iOS application crash repair method, device, equipment and storage medium. Background Art

[0002] At present, when running various applications on mobile terminals, application crashes may occur. In response to the crash problem in iOS applications, the industry generally adopts the following two solutions to fix the crash: (1) Release a new version to encourage users to upgrade the software, where the new version contains fixes for various problems found in the old version; (2) Use hot fix technology to fix, that is, without releasing a version, dynamically send the repair code to the user's mobile terminal through the server.

[0003] However, the release of a new version needs to be reviewed by the app store, which is often a cumbersome process and may take a long time. While waiting for the review, users may continue to encounter crashes, affecting their experience. Summary of the invention

[0004] Based on this, it is necessary to provide an iOS application crash repair method, device, equipment and storage medium to address the above technical issues, so as to solve at least one of the above technical issues.

[0005] The present invention provides an iOS application crash repair method, comprising:

[0006] When a crash event of an application is detected, a crash log of the crash event is recorded;

[0007] When the application is started again, the crash log is parsed to obtain crash details information of the crash event, wherein the crash details information includes the crash type and the crash cause;

[0008] Based on the crash detail information, determining whether the crash event is a preset startup crash, wherein the startup crash refers to a crash that occurs during the startup process of the application;

[0009] If a crash occurs, the crash event is repaired based on the crash detail information.

[0010] Optionally, according to an iOS application crash repair method provided by the present invention, the crash details information further includes the crash time and the page level where the crash occurs;

[0011] The determining, based on the crash detail information, whether the crash event is a preset startup crash includes:

[0012] Determine a target duration according to the crash time and the application startup time, wherein the target duration refers to the difference between the crash event occurrence time and the application startup time;

[0013] Based on the crash type, the target duration, and the page level where the crash occurs, it is determined whether the crash event is a preset startup crash.

[0014] Optionally, according to an iOS application crash repair method provided by the present invention, the crash details information also includes the class name and function name of the crash event;

[0015] The repairing the crash event based on the crash detail information includes:

[0016] Based on the crash type, the crash cause and the stack function, the crash event is dynamically and automatically repaired.

[0017] Optionally, according to an iOS application crash repair method provided by the present invention, when a crash event of an application is monitored, recording a crash log of the crash event includes:

[0018] Determine whether the preset crash signal monitoring function intercepts the crash signal;

[0019] If a crash signal is intercepted, it is determined that a crash event occurs in the application, and a crash log of the crash event is collected;

[0020] If no crash signal is intercepted, it is determined that the application has not crashed.

[0021] Optionally, according to an iOS application crash repair method provided by the present invention, when a crash event of an application is monitored, recording a crash log of the crash event includes:

[0022] Get the code data of the application;

[0023] Locating a target position in the code data, and performing point embedding at the target position;

[0024] Parsing feedback data corresponding to the tracking point, and determining whether the feedback data includes crash information;

[0025] If the crash information is included, it is determined that a crash event occurs in the application program, and a crash log of the crash event is collected;

[0026] If no crash information is included, it is determined that no crash event has occurred in the application.

[0027] Optionally, according to an iOS application crash repair method provided by the present invention, the collecting crash logs of the crash events includes:

[0028] Calling a preset exception callback function to obtain the crash type and crash cause corresponding to the crash event, and capturing the stack trace information of the crash event;

[0029] Based on the crash type, the crash cause and the stack trace information, a crash log is formed and stored.

[0030] Optionally, according to an iOS application crash repair method provided by the present invention, after repairing the crash event based on the crash detail information, the method further includes:

[0031] Determine whether the application has a crash event with the same crash type and crash cause again within a preset time;

[0032] If yes, generating an emergency crash report based on the crash details information of the crash event and sending it to the administrator;

[0033] If not, a repair success notification is generated and pushed to the administrator.

[0034] The present invention also provides an iOS application crash repair device, comprising:

[0035] A recording module is used to record a crash log of an application crash event when a crash event of the application is detected;

[0036] A parsing module, used to parse the crash log when the application is restarted to obtain crash details of the crash event, wherein the crash details include the crash type and the crash cause;

[0037] A judgment module, configured to judge whether the crash event is a preset startup crash based on the crash detail information, wherein the startup crash refers to a crash that occurs during the startup process of the application;

[0038] The repair module is used to repair the crash event based on the crash detail information if the crash occurs during startup.

[0039] The present invention also provides a computer device, comprising a memory, a processor, and computer-readable instructions stored in the memory and executable on the processor, wherein the processor implements the above-mentioned iOS application crash repair method when executing the computer-readable instructions.

[0040] The present invention also provides one or more readable storage media storing computer-readable instructions, and when the computer-readable instructions are executed by a processor, the above-mentioned iOS application crash repair method is implemented.

[0041] The above-mentioned iOS application crash repair method, device, equipment and storage medium include: when monitoring an application crash event, recording the crash log of the crash event; when the application is restarted, parsing the crash log to obtain crash details information of the crash event, wherein the crash details information includes the crash type and the crash cause; based on the crash details information, judging whether the crash event is a preset startup crash, wherein the startup crash refers to the crash that occurs during the startup process of the application; if it is a startup crash, repairing the crash event based on the crash details information. The present invention records the crash log of the crash event, and when monitoring that the crash of the application belongs to the startup crash, according to the information such as the crash type and the crash cause, the crash event is automatically repaired, so that the crash can be repaired in time to ensure the availability of the user using the APP. BRIEF DESCRIPTION OF THE DRAWINGS

[0042] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for use in the description of the embodiments of the present invention will be briefly introduced below. Obviously, the accompanying drawings in the following description are only some embodiments of the present invention. For ordinary technicians in this field, other accompanying drawings can be obtained based on these accompanying drawings without paying creative labor.

[0043] Figure 1 This is a flow chart of a method for repairing an iOS application crash in one embodiment of the present invention;

[0044] Figure 2 It is a schematic diagram of a repair process when a crash event is not found by the method provided in an embodiment of the present invention;

[0045] Figure 3 is a structural diagram of an iOS application crash repair device in one embodiment of the present invention;

[0046] Figure 4 is a schematic diagram of a computer device in one embodiment of the present invention. DETAILED DESCRIPTION

[0047] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.

[0048] The terms used in one or more embodiments of the present invention are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of the present invention. The singular forms of "a", "said" and "the" used in one or more embodiments of the present invention are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used in one or more embodiments of the present invention refers to and includes any or all possible combinations of one or more associated listed items.

[0049] At present, when running various applications on mobile terminals, applications may crash. In response to crash problems in IOS applications, the industry usually adopts the following two solutions to fix crashes: (1) Release a new version to encourage users to upgrade the software, where the new version contains fixes for various problems found in the old version; (2) Use hot fix technology for repair, that is, without releasing the version, dynamically send the repair code to the user's mobile terminal through the server. However, the release of the new version needs to be reviewed by the application store, and this review process is often cumbersome and may take a long time. While waiting for the review, users may continue to encounter crash problems, affecting the user experience.

[0050] In view of the above problems, the present invention provides the following embodiments. In one embodiment, specifically, Figure 1 As shown, Figure 1 1 is a flow chart of a method for repairing an iOS application crash in an embodiment of the present invention. The present invention provides a method for repairing an iOS application crash, comprising the following steps:

[0051] Step S11, when a crash event of an application is monitored, a crash log of the crash event is recorded;

[0052] In one embodiment, after starting an application, it is necessary to monitor whether the application crashes. Optionally, after the application is started, a crash signal monitoring function is registered; it is determined whether the crash signal monitoring function intercepts the crash signal, wherein the crash signal monitoring function can globally monitor the operation of the application at all times to see whether a crash occurs, and crash signals include system signals such as SIGILL, SIGFPE, SIGBUS, SIGPIPE, SIGSEGV and SIGABRT; if the crash signal is intercepted, it is determined that a crash event has occurred in the application, and the crash log of the crash event is collected; if the crash signal is not intercepted, it is determined that the application has not crashed.

[0053] Optionally, it is also possible to determine whether the application has crashed by placing a tracking point at a specific location of the application. Specifically: the code data of the application is obtained, and then the target location is located in the code data, and a tracking point is placed at the target location to obtain feedback data corresponding to the tracking point; further, the feedback data is parsed, and it is determined whether the feedback data includes crash information; if the crash information is included, it is determined that the application has crashed, and the crash log of the crash event is collected; if the crash information is not included, it is determined that the application has not crashed.

[0054] Furthermore, an exception callback function signal_handler is set. When the application crashes, the exception callback function signal_handler is called to obtain the crash type and crash cause corresponding to the crash event, and capture the stack trace information of the crash. The stack trace information includes the crash time, the page level where the crash occurs, the class name and function name of the crash event, and other information; related user information, mobile device information, App interface information and other related information can also be collected, and a crash log is formed based on the crash type, the crash cause and the stack trace information, and the crash log is stored on the terminal application disk.

[0055] Step S12, when the application is started again, the crash log is parsed to obtain crash details information of the crash event;

[0056] Specifically, when the application is started next time, the latest crash log stored in the application App is read, and then the crash log is parsed to obtain the crash details information of the crash event. The crash details information includes the crash type, crash cause, crash time, page level where the crash occurred, and the class name and function name of the crash event.

[0057] Step S13, based on the crash details information, determining whether the crash event is a preset startup crash;

[0058] It should be noted that startup crash refers to a crash that occurs during the startup process of an application. Specifically, based on the crash type, the page level where the crash occurs, the time from the crash event to the startup of the application, and other information, a comprehensive judgment is made as to whether the crash event is a startup crash.

[0059] Step S14: If a crash is initiated, repair the crash event based on the crash details information.

[0060] Specifically, if a crash occurs when the system is started, a repair strategy is determined based on the crash type, the crash cause, and the stack function, so that the dynamic characteristics of iOS are used to perform corresponding dynamic and automatic repairs on the crash event according to the repair strategy. For example, if a method is not found, an array is out of bounds, the dictionary key value is empty, a string is intercepted, etc., the dynamic characteristics of iOS are used to perform corresponding repair processing.

[0061] In a specific example, referring to Figure 2 , Figure 2 This is a schematic diagram of the repair process of a crash event caused by a method not found provided by an embodiment of the present invention; taking a crash caused by a method not found as an example: when a message is sent to an object, if the method list of the object and the method list of its parent class cannot process the message, the message forwarding mechanism will be triggered. The specific steps are as follows:

[0062] When an object receives a message, the runtime system first checks the object's method list to see if there is an implementation for the message. If not found, the runtime system calls the object's resolveInstanceMethod method. This method gives the class the opportunity to dynamically add a method that implements the message. Typically, this is done by adding a category to the class that contains the implementation for the message. If resolveInstanceMethod returns YES, indicating that the method implementation was found, the runtime system will call the newly added method.

[0063] If dynamic method resolution fails, the runtime system calls the object's forwardingTargetForSelector method. This method allows the object to find another object that can handle the message. If forwardingTargetForSelector returns a non-nil object, the runtime system will use this object as the new recipient and send the message again.

[0064] If the backup receiver cannot process the message, the runtime system calls the object's -forwardInvocation method. This method allows the object to manually forward the message to another object, or to perform other processing on the message. In the forwardInvocation method, you can change the message's receiver or method selector by modifying the NSInvocation object, and then resend the message.

[0065] If the above steps cannot process the message, the runtime system will eventually throw an exception doesNotRecognizeSelector. This exception indicates that the runtime system cannot process the message, which usually causes the program to crash.

[0066] The embodiment of the present invention, through the above scheme, includes: when monitoring an application crash event, recording the crash log of the crash event; when the application is restarted, parsing the crash log to obtain crash details information of the crash event, wherein the crash details information includes the crash type and the crash cause; based on the crash details information, judging whether the crash event is a preset startup crash, wherein the startup crash refers to the crash that occurs during the startup process of the application; if it is a startup crash, repairing the crash event based on the crash details information. The present invention records the crash log of the crash event, and when monitoring that the crash of the application belongs to the startup crash, the crash event is automatically repaired according to the crash type, the crash cause and other information, so that the crash can be repaired in a relatively timely manner to ensure the availability of the user's use of the APP.

[0067] In one embodiment of the present invention, judging whether the crash event is a preset startup crash based on the crash detail information includes:

[0068] Determine a target duration according to the crash time and the application startup time, wherein the target duration refers to the difference between the crash event occurrence time and the application startup time;

[0069] Based on the crash type, the target duration, and the page level where the crash occurs, it is determined whether the crash event is a preset startup crash.

[0070] It should be noted that when an application crash event is monitored, a target duration is determined based on the crash time and the current startup time of the application, where the target duration refers to the difference between the crash event occurrence time and the application startup time; and then combined with the crash type, the target duration and the page level where the crash occurs, it is determined whether the crash event is a preset startup crash. For example, if the crash type is a system crash signal such as SIGABRT, the crash page is the home page, and the crash time is within 5 seconds from the application startup time, it can be determined that the current crash event is a startup crash.

[0071] In one embodiment of the present invention, after repairing the crash event based on the crash detail information, the method further includes:

[0072] Determine whether the application has a crash event with the same crash type and crash cause again within a preset time;

[0073] If yes, generating an emergency crash report based on the crash details information of the crash event and sending it to the administrator;

[0074] If not, a repair success notification is generated and pushed to the administrator.

[0075] Specifically, after the crash event is repaired, the application is monitored to determine whether the application has another crash event of the same crash type and crash cause within a preset time. If there is no crash event of the same crash type and crash cause, the result of the successful repair notification is sent to the management platform for the management personnel to review. If a crash event of the same crash type and crash cause is detected, an emergency crash report is generated based on the crash details information of the crash event and sent to the management personnel. The emergency crash report includes the repair plan and the problem. The platform administrator will analyze the emergency crash report and can decide whether to stop the user's automatic repair function, and review the reasons for the repair failure.

[0076] It should be understood that the order of execution of the steps in the above embodiment does not necessarily mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiment of the present invention.

[0077] In one embodiment, an iOS application crash repair device is provided, and the iOS application crash repair device corresponds to the iOS application crash repair method in the above embodiment. Figure 3 As shown, Figure 3 : is a structural diagram of an iOS application crash repair device in one embodiment of the present invention, the iOS application crash repair device comprises:

[0078] The recording module 21 is used to record a crash log of the crash event when a crash event of the application is monitored;

[0079] The parsing module 22 is used to parse the crash log when the application is restarted to obtain crash details of the crash event, wherein the crash details include the crash type and the crash cause;

[0080] A judgment module 23, configured to judge whether the crash event is a preset startup crash based on the crash detail information, wherein the startup crash refers to a crash that occurs during the startup process of the application;

[0081] The repair module 24 is used to repair the crash event based on the crash detail information if the crash is started.

[0082] iOS app crash repair tool also includes:

[0083] The crash details information also includes the crash time, the page level where the crash occurred, and the class name and function name where the crash event occurred.

[0084] The judging module 23 is also used for:

[0085] Determine a target duration according to the crash time and the application startup time, wherein the target duration refers to the difference between the crash event occurrence time and the application startup time;

[0086] Based on the crash type, the target duration, and the page level where the crash occurs, it is determined whether the crash event is a preset startup crash.

[0087] The repair module 24 is also used for:

[0088] Based on the crash type, the crash cause and the stack function, the crash event is dynamically and automatically repaired.

[0089] The recording module 21 is also used for:

[0090] Determine whether the preset crash signal monitoring function intercepts the crash signal;

[0091] If a crash signal is intercepted, it is determined that a crash event occurs in the application, and a crash log of the crash event is collected;

[0092] If no crash signal is intercepted, it is determined that the application has not crashed.

[0093] The recording module 21 is also used for:

[0094] Get the code data of the application;

[0095] Locating a target position in the code data, and performing point embedding at the target position;

[0096] Parsing feedback data corresponding to the tracking point, and determining whether the feedback data includes crash information;

[0097] If the crash information is included, it is determined that a crash event occurs in the application program, and a crash log of the crash event is collected;

[0098] If no crash information is included, it is determined that no crash event has occurred in the application.

[0099] The recording module 21 is also used for:

[0100] Calling a preset exception callback function to obtain the crash type and crash cause corresponding to the crash event, and capturing the stack trace information of the crash event;

[0101] Based on the crash type, the crash cause and the stack trace information, a crash log is formed and stored.

[0102] iOS app crash repair tool also includes:

[0103] A determination module, used to determine whether the application program has a crash event of the same crash type and crash cause again within a preset time;

[0104] A generating module, configured to generate an emergency crash report based on the crash details information of the crash event and send the report to a management personnel;

[0105] The push module is used to generate a repair success notification and push it to the management personnel if not.

[0106] For the specific definition of the iOS application crash repair device, please refer to the definition of the iOS application crash repair method above, which will not be repeated here. Each module in the above-mentioned iOS application crash repair device can be implemented in whole or in part by software, hardware and a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.

[0107] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 4 As shown, Figure 4 : is a schematic diagram of a computer device in one embodiment of the present invention. The computer device includes a processor, a memory, a network interface and a database connected by a device bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a readable storage medium and an internal memory. The readable storage medium stores an operating device, a computer-readable instruction and a database. The internal memory provides an environment for the operation of the operating device and the computer-readable instructions in the readable storage medium. The database of the computer device is used to store data involved in the iOS application crash repair method. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer-readable instruction is executed by the processor, an iOS application crash repair method is implemented. The readable storage medium provided in this embodiment includes a non-volatile readable storage medium and a volatile readable storage medium.

[0108] In one embodiment, a computer device is provided. The computer device may be a terminal device, and its internal structure diagram may be as follows: Figure 4As shown. The computer device includes a processor, a memory, and a network interface connected by a device bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a readable storage medium. The readable storage medium stores computer-readable instructions. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer-readable instructions are executed by the processor, an iOS application crash repair method is implemented. The readable storage medium provided in this embodiment includes a non-volatile readable storage medium and a volatile readable storage medium.

[0109] In one embodiment, a computer device is provided, including a memory, a processor, and a computer-readable instruction stored in the memory and executable on the processor, and the processor implements the steps of the iOS application crash repair method as described above when executing the computer-readable instruction. The method includes: when a crash event of an application is monitored, a crash log of the crash event is recorded; when the application is restarted, the crash log is parsed to obtain crash details of the crash event, wherein the crash details include the crash type and the crash cause; based on the crash details information, it is determined whether the crash event is a preset startup crash, wherein the startup crash refers to a crash that occurs during the startup process of the application; if it is a startup crash, the crash event is repaired based on the crash details information.

[0110] In one embodiment, a readable storage medium is provided, the readable storage medium stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the steps of the iOS application crash repair method as described above are implemented. A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through computer-readable instructions, and the computer-readable instructions can be stored in a non-volatile readable storage medium or a volatile readable storage medium. When the computer-readable instructions are executed, they may include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include non-volatile and / or volatile memory. Non-volatile memory may include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory may include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0111] Those skilled in the art can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional units and modules is used as an example. In actual applications, the above-mentioned functions can be distributed and completed by different functional units and modules as needed, that is, the internal structure of the device can be divided into different functional units or modules to complete all or part of the functions described above.

[0112] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included in the protection scope of the present invention.

Claims

1. A method for repairing iOS application crashes. It is characterized in that include: When a crash event of an application is detected, a crash log of the crash event is recorded; When the application is started again, the crash log is parsed to obtain crash details information of the crash event, wherein the crash details information includes the crash type and the crash cause; Based on the crash detail information, determining whether the crash event is a preset startup crash, wherein the startup crash refers to a crash that occurs during the startup process of the application; If a crash occurs, the crash event is repaired based on the crash detail information.

2. The iOS application crash repair method according to claim 1, It is characterized in that The crash details information also includes the crash time and the page level where the crash occurred; The determining, based on the crash detail information, whether the crash event is a preset startup crash includes: Determine a target duration according to the crash time and the application startup time, wherein the target duration refers to the difference between the crash event occurrence time and the application startup time; Based on the crash type, the target duration, and the page level where the crash occurs, it is determined whether the crash event is a preset startup crash.

3. The iOS application crash repair method according to claim 1, It is characterized in that The crash details information also includes the class name and function name where the crash event occurred; The repairing the crash event based on the crash detail information includes: Based on the crash type, the crash cause and the stack function, the crash event is dynamically and automatically repaired.

4. The iOS application crash repair method according to claim 1, It is characterized in that When a crash event of the application is monitored, a crash log of the crash event is recorded, including: Determine whether the preset crash signal monitoring function intercepts the crash signal; If a crash signal is intercepted, it is determined that a crash event occurs in the application, and a crash log of the crash event is collected; If no crash signal is intercepted, it is determined that the application has not crashed.

5. The iOS application crash repair method according to claim 1, It is characterized in that When a crash event of the application is monitored, a crash log of the crash event is recorded, including: Get the code data of the application; Locating a target position in the code data, and performing point embedding at the target position; Parsing feedback data corresponding to the tracking point, and determining whether the feedback data includes crash information; If the crash information is included, it is determined that a crash event occurs in the application program, and a crash log of the crash event is collected; If no crash information is included, it is determined that no crash event has occurred in the application.

6. The iOS application crash repair method according to claim 4 or 5, It is characterized in that The collecting of the crash log of the crash event includes: Calling a preset exception callback function to obtain the crash type and crash cause corresponding to the crash event, and capturing the stack trace information of the crash event; Based on the crash type, the crash cause and the stack trace information, a crash log is formed and stored.

7. The iOS application crash repair method according to claim 1, It is characterized in that After repairing the crash event based on the crash detail information, the method further includes: Determine whether the application has a crash event with the same crash type and crash cause again within a preset time; If yes, generating an emergency crash report based on the crash details information of the crash event and sending it to the administrator; If not, a repair success notification is generated and pushed to the administrator.

8. An iOS application crash repair device, It is characterized in that include: A recording module is used to record a crash log of an application crash event when a crash event of the application is detected; A parsing module, used to parse the crash log when the application is restarted to obtain crash details of the crash event, wherein the crash details include the crash type and the crash cause; A judgment module, configured to judge whether the crash event is a preset startup crash based on the crash detail information, wherein the startup crash refers to a crash that occurs during the startup process of the application; The repair module is used to repair the crash event based on the crash detail information if the crash occurs during startup.

9. A computer device comprising a memory, a processor, and computer readable instructions stored on the memory and executed on the processor, It is characterized in that When the processor executes the computer-readable instructions, the iOS application crash repair method according to any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium having computer-readable instructions stored thereon, It is characterized in that When the computer-readable instructions are executed by a processor, the iOS application crash repair method according to any one of claims 1 to 7 is implemented.

Citation Information

Cited By

  • Mobile phone applet flash quit management system and method

    CN119311597A