Application crash processing method and device based on multi-terminal collaboration

Abstract

The invention relates to the technical field of computers, and discloses an application crash processing method and device based on multi-terminal collaboration.The method comprises the steps that when it is detected that a target terminal of a target application captures a crash event, a crash log corresponding to the crash event is generated; analyzing the crash log to obtain a crash analysis result corresponding to the crash event; according to the crash analysis result, based on a function switch pre-embedded in the target application, executing a crash processing operation for the crash event; and controlling at least one associated end of the target application to execute crash protection operation for the crash event according to the crash analysis result and a multi-end protection measure corresponding to the target application. Visibly, the application crash event can be cooperatively processed by using the pre-embedded function switch and the multi-terminal protection measures, and the processing timeliness and the processing accuracy of the application crash can be improved, so that the operation reliability of the application is improved, and the use experience of a user on the application program is improved.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method and device for handling application crashes based on multi-terminal collaboration. Background Art

[0002] In the prior art, usually after an application is launched, the application crash information is captured through the crash capture SDK (Software Development Kit) to which the application is connected. The developer regularly analyzes the crash information and fixes related codes, and then repackages, reviews and launches the application to allow users to update the application.

[0003] However, in actual applications, the series of processes in the above crash handling method require a long processing time, which may cause users to continue to encounter the same crash problem for a long time, affecting the user experience; even when encountering unknown online crashes, it may cause continuous crashes, making the application unusable.

[0004] Therefore, it is particularly important to propose a technical solution that can improve the timeliness and accuracy of application crash processing, thereby improving the operating reliability of the application and improving the user experience of the application. Summary of the invention

[0005] The present invention provides an application crash processing method and device based on multi-terminal collaboration, which can improve the timeliness and accuracy of application crash processing, thereby improving the operating reliability of the application, which is conducive to improving the user experience of the application.

[0006] In order to solve the above technical problems, the first aspect of the present invention discloses an application crash processing method based on multi-terminal collaboration, the method comprising:

[0007] When it is detected that the target end of the target application captures a crash event, a crash log corresponding to the crash event is generated;

[0008] Analyze the crash log to obtain a crash analysis result corresponding to the crash event;

[0009] According to the crash analysis result, based on the function switch embedded in the target application, executing a crash processing operation for the crash event;

[0010] According to the crash analysis result and the multi-terminal protection measures corresponding to the target application, at least one associated terminal of the target application is controlled to perform a crash protection operation for the crash event.

[0011] As an alternative implementation, in the first aspect of the present invention, generating the crash log corresponding to the crash event includes:

[0012] Obtaining the original crash log corresponding to the crash event;

[0013] Based on the first preset interface corresponding to the target end, parsing the original crash log to obtain the parsing result corresponding to the original crash log;

[0014] Based on the first preset interface corresponding to the target end, generating the symbolized log corresponding to the original crash log according to the parsing result as the crash log corresponding to the crash event.

[0015] As an alternative implementation, in the first aspect of the present invention, analyzing the crash log to obtain the crash analysis result corresponding to the crash event includes:

[0016] Based on the crash analysis framework corresponding to the target end, analyzing the crash log to obtain the crash information corresponding to the crash event; the crash information includes the target module where the crash event occurs and the crash reason corresponding to the target module;

[0017] Obtaining the module crash information of the target application stored in advance; the module crash information is used to represent the association relationship between each functional module included in the target application and various crashes;

[0018] According to the crash information, searching whether there is a matching module crash information in the module crash information that matches the crash information to obtain a matching result;

[0019] Wherein, the crash analysis result includes the crash information and / or the matching result.

[0020] As an alternative implementation, in the first aspect of the present invention, the module crash information includes the module table corresponding to the target application and the crash table corresponding to the target application;

[0021] Wherein, the module table records a combination of one or more of the module identifiers of each functional module included in the target application, the function switches corresponding to each functional module, and the conventional crash identifiers corresponding to each functional module;

[0022] Wherein, the crash table records the crash identifiers of each crash and / or the crash reasons corresponding to each crash; wherein, each conventional crash identifier is one of the crash identifiers in the crash table.

[0023] As an optional implementation, in the first aspect of the present invention, performing a crash processing operation for the crash event based on the crash analysis result and the function switch embedded in the target application includes:

[0024] According to the crash analysis result, triggering a target function switch pre-buried by the target application in the target module to enable a protection function corresponding to the target module and repair the crash event;

[0025] After the target function switch is triggered, guidance information for the crash event is generated, and the guidance information is fed back to the target user corresponding to the target terminal; the guidance information is used to prompt the target user that the target module has crashed and / or guide the target user to use other associated terminals in the target application except the target terminal;

[0026] The method of triggering a target function switch pre-embedded in the target module by the target application according to the crash analysis result to enable a protection function corresponding to the target module and repair the crash event includes:

[0027] When the matching result in the crash analysis result is used to indicate that there is matching module crash information matching the crash information in the module crash information, triggering a target function switch pre-embedded in the target module by the target application to enable a protection function corresponding to the target module and repair the crash event;

[0028] When the matching result in the crash analysis result is used to indicate that there is no matching module crash information matching the crash information in the module crash information, a target analysis result fed back by a developer corresponding to the target application for the crash event is received, and based on the target analysis result, a target function switch embedded in the target module of the target application is triggered to turn on the protection function corresponding to the target module and repair the crash event; wherein the target analysis result is obtained based on the analysis of the crash log, the module crash information and the programming code corresponding to the target module.

[0029] As an optional implementation, in the first aspect of the present invention, the multi-terminal protection measures include interface protection measures and / or module protection measures;

[0030] The controlling at least one associated terminal of the target application to perform a crash protection operation for the crash event according to the crash analysis result and the multi-terminal protection measures corresponding to the target application includes:

[0031] Based on the crash analysis result and the interface protection measure corresponding to the target application, and based on the first associated end of the target application, control all second associated ends in the target application to suspend calling the target interface associated with the crash event; the second associated end is the associated end in the target application associated with the first associated end; and / or,

[0032] Based on the crash analysis result and the module protection measure corresponding to the target application, control at least one third associated end of the target application to trigger an associated function switch associated with the crash event, so as to enable the collaborative protection functions corresponding to all the third associated ends.

[0033] As an optional implementation manner, in the first aspect of the present invention, the step of, based on the crash analysis result and the interface protection measure corresponding to the target application, and based on the first associated end of the target application, controlling all second associated ends in the target application to suspend calling the target interface associated with the crash event includes:

[0034] Based on the preset communication method corresponding to the target application, transmit the crash analysis result to the first associated end of the target application, and trigger the first associated end of the target application to enable the interface protection function corresponding to the crash analysis result; the preset communication method includes a preset connection protocol and / or a second preset interface;

[0035] Based on the interface protection function, control the first associated end to suspend all second associated ends in the target application from calling the target interface associated with the crash analysis result;

[0036] Among them, the step of, based on the crash analysis result and the module protection measure corresponding to the target application, controlling at least one third associated end of the target application to trigger an associated function switch associated with the crash event, so as to enable the collaborative protection functions corresponding to all the third associated ends includes:

[0037] Based on the cloud corresponding to the target application, transmit the crash analysis result to at least one third associated end of the target application;

[0038] Control at least one of the third associated ends of the target application to trigger an associated function switch associated with the crash analysis result, so as to enable the collaborative protection functions corresponding to all the third associated ends.

[0039] The second aspect of the present invention discloses an application crash processing device based on multi-end collaboration, and the device includes:

[0040] A generation module, configured to generate a crash log corresponding to the crash event when it is detected that the target end of the target application captures the crash event;

[0041] An analysis module, used to analyze the crash log to obtain a crash analysis result corresponding to the crash event;

[0042] A crash processing module, configured to perform a crash processing operation for the crash event according to the crash analysis result and based on a function switch pre-embedded in the target application;

[0043] A crash protection module is used to control at least one associated terminal of the target application to perform a crash protection operation for the crash event according to the crash analysis result and the multi-terminal protection measures corresponding to the target application.

[0044] As an optional implementation, in the second aspect of the present invention, the specific manner in which the generation module generates the crash log corresponding to the crash event includes:

[0045] Obtaining the original crash log corresponding to the crash event;

[0046] Parsing the original crash log based on a first preset interface corresponding to the target end to obtain a parsing result corresponding to the original crash log;

[0047] Based on the first preset interface corresponding to the target end and according to the parsing result, a symbolized log corresponding to the original crash log is generated as the crash log corresponding to the crash event.

[0048] As an optional implementation, in the second aspect of the present invention, the specific manner in which the analysis module analyzes the crash log to obtain the crash analysis result corresponding to the crash event includes:

[0049] Based on the crash analysis framework corresponding to the target end, the crash log is analyzed to obtain crash information corresponding to the crash event; the crash information includes the target module where the crash event occurs and the crash cause corresponding to the target module;

[0050] Acquire pre-stored module crash information corresponding to the target application; the module crash information is used to indicate the association relationship between each functional module included in the target application and multiple crashes;

[0051] According to the crash information, searching whether there is matching module crash information matching the crash information in the module crash information to obtain a matching result;

[0052] The crash analysis result includes the crash information and / or the matching result.

[0053] As an optional implementation, in the second aspect of the present invention, the module crash information includes a module table corresponding to the target application and a crash table corresponding to the target application;

[0054] The module table records a combination of one or more of a module identifier of each functional module included in the target application, a function switch corresponding to each functional module, and a conventional crash identifier corresponding to each functional module;

[0055] The crash table records the crash identifier of each crash and / or the crash reason corresponding to each crash; and each of the conventional crash identifiers is one of the crash identifiers in the crash table.

[0056] As an optional implementation, in the second aspect of the present invention, the crash processing module performs a specific manner of performing a crash processing operation for the crash event based on the crash analysis result and the function switch embedded in the target application, including:

[0057] According to the crash analysis result, triggering a target function switch pre-buried by the target application in the target module to enable a protection function corresponding to the target module and repair the crash event;

[0058] After the target function switch is triggered, guidance information for the crash event is generated, and the guidance information is fed back to the target user corresponding to the target terminal; the guidance information is used to prompt the target user that the target module has crashed and / or guide the target user to use other associated terminals in the target application except the target terminal;

[0059] The specific manner in which the crash processing module triggers the target function switch pre-embedded in the target module by the target application according to the crash analysis result to enable the protection function corresponding to the target module and repair the crash event includes:

[0060] When the matching result in the crash analysis result is used to indicate that there is matching module crash information matching the crash information in the module crash information, triggering a target function switch pre-embedded in the target module by the target application to enable a protection function corresponding to the target module and repair the crash event;

[0061] When the matching result in the crash analysis result is used to indicate that there is no matching module crash information in the module crash information that matches the crash information, receive the target analysis result feedback by the developer corresponding to the target application for the crash event, and trigger, according to the target analysis result, the target function switch pre-buried in the target module of the target application to turn on the protection function corresponding to the target module and repair the crash event; wherein, the target analysis result is obtained by analyzing the crash log, the module crash information, and the programming code corresponding to the target module.

[0062] As an optional implementation manner, in the second aspect of the present invention, the multi-terminal protection measures include interface protection measures and / or module protection measures;

[0063] Among them, the specific manner in which the crash protection module controls at least one associated end of the target application to perform a crash protection operation for the crash event according to the crash analysis result and the multi-terminal protection measures corresponding to the target application includes:

[0064] Based on the first associated end of the target application, according to the crash analysis result and the interface protection measures corresponding to the target application, control all second associated ends in the target application to suspend calling the target interface associated with the crash event; the second associated end is an associated end in the target application associated with the first associated end; and / or,

[0065] Based on the crash analysis result and the module protection measures corresponding to the target application, control at least one third associated end of the target application to trigger an associated function switch associated with the crash event to turn on the collaborative protection functions corresponding to all the third associated ends.

[0066] As an optional implementation manner, in the second aspect of the present invention, the specific manner in which the crash protection module controls all second associated ends in the target application to suspend calling the target interface associated with the crash event based on the first associated end of the target application according to the crash analysis result and the interface protection measures corresponding to the target application includes:

[0067] Based on the preset communication method corresponding to the target application, transmit the crash analysis result to the first associated end of the target application, and trigger the first associated end of the target application to turn on the interface protection function corresponding to the crash analysis result; the preset communication method includes a preset connection protocol and / or a second preset interface;

[0068] Based on the interface protection function, control the first associated end to suspend all second associated ends in the target application from calling the target interface associated with the crash analysis result;

[0069] Among them, the specific manner in which the crash protection module controls at least one third associated end of the target application to trigger an association function switch associated with the crash event according to the crash analysis result and the module protection measure corresponding to the target application, so as to enable the collaborative protection functions corresponding to all the third associated ends, includes:

[0070] Transmit the crash analysis result to at least one third associated end of the target application based on the cloud corresponding to the target application;

[0071] Control at least one of the third associated ends of the target application to trigger an association function switch associated with the crash analysis result, so as to enable the collaborative protection functions corresponding to all the third associated ends.

[0072] The third aspect of the present invention discloses another application crash processing device based on multi-end collaboration, and the device includes:

[0073] A memory storing executable program code;

[0074] A processor coupled to the memory;

[0075] The processor calls the executable program code stored in the memory and executes some or all of the steps of the application crash processing method based on multi-end collaboration disclosed in the first aspect of the present invention.

[0076] The fourth aspect of the present invention discloses a computer storage medium, and the computer storage medium stores computer instructions, which are used to execute some or all of the steps of the application crash processing method based on multi-end collaboration disclosed in the first aspect of the present invention when called.

[0077] Compared with the prior art, the present invention has the following beneficial effects:

[0078] It can be seen that the implementation of the present invention can generate a crash log corresponding to the crash event when the target end of the target application captures a crash event, and obtain the corresponding crash analysis result by analyzing the crash log, and then execute the crash processing operation for the crash event according to the crash analysis result and through the function switch embedded in the target application, and control the associated end of the target application to execute the crash protection operation according to the crash analysis result and the multi-end protection measures, and can collaboratively process the application crash event by using the local embedded function switch and the multi-end protection measures of the other end, thereby improving the timeliness, accuracy and comprehensiveness of the application crash processing, and then realizing the online timely capture and analysis of the crash and preventing various program design defects or unknown sudden crashes from spreading to other ends, which is beneficial to improving the crash protection reliability and comprehensiveness of the application, and then is beneficial to improving the operation security and reliability of the application, and is beneficial to improving the user experience of the application. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0080] Figure 1 It is a flowchart of a method for handling application crash based on multi-terminal collaboration disclosed in an embodiment of the present invention;

[0081] Figure 2 It is a flowchart of another application crash processing method based on multi-terminal collaboration disclosed in an embodiment of the present invention;

[0082] Figure 3 It is a flowchart of another method for handling application crash based on multi-terminal collaboration disclosed in an embodiment of the present invention;

[0083] Figure 4 It is a timing diagram of an application crash processing method based on multi-terminal collaboration disclosed in an embodiment of the present invention;

[0084] Figure 5 It is a structural schematic diagram of an application crash processing device based on multi-terminal collaboration disclosed in an embodiment of the present invention;

[0085] Figure 6 It is a structural schematic diagram of another application crash processing device based on multi-terminal collaboration disclosed in an embodiment of the present invention. DETAILED DESCRIPTION

[0086] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below 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 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.

[0087] The terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, device, product or end including a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units inherent to these processes, methods, products or ends.

[0088] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present invention. The appearance of the phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0089] The present invention discloses a method and device for processing application crashes based on multi-terminal collaboration, which can generate a crash log corresponding to the crash event when the target end of the target application captures the crash event, and obtain the corresponding crash analysis result by analyzing the crash log, and then perform the crash processing operation for the crash event according to the crash analysis result and through the function switch pre-embedded by the target application, and control the associated end of the target application to perform the crash protection operation according to the crash analysis result and the multi-terminal protection measures, and can collaboratively process the application crash event by using the local pre-embedded function switch and the multi-terminal protection measures of the other end, thereby improving the timeliness, accuracy and comprehensiveness of the application crash processing, and then realizing the online timely capture and analysis of the crash and preventing various program design defects or unknown sudden crashes from spreading to other ends, thereby facilitating the improvement of the crash protection reliability and comprehensiveness of the application, thereby facilitating the improvement of the operation safety and reliability of the application, and improving the user experience of the application. The following are detailed descriptions.

[0090] Embodiment 1

[0091] See also Figure 1 , Figure 1It is a schematic flowchart of a method for handling application crashes based on multi - device collaboration disclosed in an embodiment of the present invention. Among them, Figure 1 The described method for handling application crashes based on multi - device collaboration can be applied to a device for handling application crashes based on multi - device collaboration. This device can include one of a crash - handling terminal, a crash - handling device, a crash - handling system, and a server. Among them, the server can include a local server or a cloud server, which is not limited in the embodiments of the present invention. As Figure 1 shown, the method for handling application crashes based on multi - device collaboration can include the following operations:

[0092] 101. When it is detected that a target end of a target application captures a crash event, generate a crash log corresponding to the crash event.

[0093] In the embodiments of the present invention, the target application can be any application program, which is not limited in the embodiments of the present invention; the target application can correspond to multiple associated ends. Among them, the target application can run on each associated end or provide services related to the target application, which is not limited in the embodiments of the present invention; among them, exemplarily, each associated end can be a client end or a firmware end; among them, the client end can be one of an iOS end, an Android end, a PC (Personal Computer) end, a Web (web page) end, or can also be other types of client ends, which is not limited in the embodiments of the present invention; the firmware end can be a hardware end connected to the client end. Exemplarily, the firmware end can be a NAS (Network Attached Storage) device, which is not limited in the embodiments of the present invention. Among them, the target end of the target application is one of the above - mentioned associated ends.

[0094] In the embodiments of the present invention, optionally, at least one of a crash capture plugin, a crash capture library, and a crash capture interface corresponding to the target end can be used to capture the crash event, which is not limited in the embodiments of the present invention; exemplarily, KCrash can be used to capture the crash event, which is not limited in the embodiments of the present invention.

[0095] In the embodiments of the present invention, optionally, after generating the crash log corresponding to the crash event, the crash log can be reported to the background of the target application to perform the operation in step 102 through the background, which is not limited in the embodiments of the present invention; further optionally, when the target application is reopened after a crash event occurs, the crash log can be automatically reported to the background of the target application, which is not limited in the embodiments of the present invention.

[0096] 102. Analyze the crash log to obtain a crash analysis result corresponding to the crash event.

[0097] 103. Based on the crash analysis result and the function switches pre-embedded in the target application, perform crash handling operations for the crash event.

[0098] In an embodiment of the present invention, optionally, during the development of the target application, function switches can be pre-embedded in each function module of the target application, which is not limited in the embodiments of the present invention; further optionally, function switches can be pre-embedded at the entrance of each function module, which is not limited in the embodiments of the present invention; wherein, the function switch is used to control whether the function provided by the function module can be used. Exemplarily, if the function switch is turned off, the function provided by the function module cannot be used, and if the function switch is turned on, the user can use the function provided by the function module.

[0099] In an embodiment of the present invention, optionally, the crash handling operation can include one or a combination of more of a function closing operation, a user guidance operation, and a crash repair operation, which is not limited in the embodiments of the present invention; wherein, the function closing operation can be used to close the function module where the crash event occurs, the user guidance operation can be used to guide the user to use other associated terminals of the target application except the target terminal, and the crash repair operation is used to repair the crash event.

[0100] 104. According to the crash analysis result and the multi-terminal protection measures corresponding to the target application, control at least one associated terminal of the target application to perform crash protection operations for the crash event.

[0101] In an embodiment of the present invention, optionally, the crash protection operation can be used to suspend the invocation of the interface of the function module where the crash event occurs and / or suspend the provision of the function corresponding to the function module where the crash event occurs, which is not limited in the embodiments of the present invention.

[0102] It should be noted that there is no sequence relationship between step 103 and step 104, that is, step 103 can occur before or after step 104 or occur simultaneously with step 104, which is not limited in the embodiments of the present invention.

[0103] It can be seen that the method described in the embodiment of the present invention can generate a crash log corresponding to the crash event when the target end of the target application captures a crash event, and obtain the corresponding crash analysis result by analyzing the crash log, and then perform a crash processing operation for the crash event based on the crash analysis result and through the function switch embedded in the target application, and control the associated end of the target application to perform a crash protection operation based on the crash analysis result and multi-end protection measures, and can collaboratively process application crash events by using the local embedded function switch and the multi-end protection measures of the other end, thereby improving the timeliness, accuracy and comprehensiveness of application crash processing, and further realizing timely capture and analysis of crashes online, and preventing various program design defects or unknown sudden crashes from spreading to other ends, which is beneficial to improving the crash protection reliability and comprehensiveness of the application program, and further beneficial to improving the operating security and reliability of the application, and is beneficial to improving the user experience of the application.

[0104] In an optional embodiment, generating a crash log corresponding to a crash event may include the following operations:

[0105] Get the original crash log corresponding to the crash event;

[0106] Parsing the original crash log based on the first preset interface corresponding to the target end to obtain a parsing result corresponding to the original crash log;

[0107] Based on the first preset interface corresponding to the target end, according to the parsing result, a symbolized log corresponding to the original crash log is generated as the crash log corresponding to the crash event.

[0108] The original crash log corresponding to the crash event may be log information generated when the crash event occurs, and the symbolized log is a log obtained by performing a symbolization operation on the parsing result corresponding to the original crash log.

[0109] Among them, the first preset interface corresponding to the target end may be an interface that can provide parsing and symbolization of log information; exemplarily, when the target end is an iOS end, the first preset interface corresponding to the target end may be an API (Application Programming Interface) provided by iOS, and further, the API may be a Symbolization API, which is not limited in the embodiments of the present invention.

[0110] It can be seen that this optional embodiment can parse the obtained original crash log corresponding to the crash event based on the first preset interface corresponding to the target end, obtain the parsing result corresponding to the original crash log, and then generate a symbolized log as the crash log corresponding to the crash event according to the parsing result, which can realize the preliminary parsing of the crash event and generate a more standardized crash log, improving the generation accuracy and standardization of the crash log, and being beneficial to improving the subsequent analysis accuracy of the crash log.

[0111] In another optional embodiment, analyzing the crash log to obtain the crash analysis result corresponding to the crash event may include the following operations:

[0112] Based on the crash analysis framework corresponding to the target end, analyze the crash log to obtain the crash information corresponding to the crash event; the crash information includes the target module where the crash event occurs and the crash reason corresponding to the target module;

[0113] Obtain the module crash information corresponding to the target application stored in advance; the module crash information is used to represent the association relationship between each functional module included in the target application and various crashes;

[0114] According to the crash information, check whether there is a matching module crash information in the module crash information that matches the crash information, and obtain the matching result.

[0115] Optionally, the crash analysis result may include the crash information and / or the matching result.

[0116] Among them, by way of example, when the target end is the iOS end, the crash analysis framework may be MetricKit, which is not limited in the embodiments of the present invention.

[0117] Among them, the target module where the crash event occurs is one of the functional modules of the target application.

[0118] Among them, optionally, the module crash information may be stored in advance in the database corresponding to the target application, or may be stored in advance in the local storage of each associated end of the target application, which is not limited in the embodiments of the present invention.

[0119] Among them, optionally, the association relationship between each functional module included in the target application and various crashes may be used to represent one or more of the crash information that has occurred in each functional module, the conventional crash information corresponding to each functional module, and the specific information of each crash, which is not limited in the embodiments of the present invention; among them, the conventional crash information is the relevant information of the crash type with a crash occurrence frequency higher than the preset frequency; further optionally, the conventional crash information may include the conventional crash identifier corresponding to each functional module, and optionally, may also include the crash occurrence frequency corresponding to each conventional crash identifier, which is not limited in the embodiments of the present invention.

[0120] It can be seen that this optional embodiment can analyze the crash log based on the crash analysis framework corresponding to the target end, obtain crash information including the target module where the crash event occurs and the crash cause corresponding to the target module, and according to the crash information, search whether there is a matching module crash information in the pre-stored module crash information of the target application to obtain a matching result, which can improve the analysis accuracy and comprehensiveness of the crash log, thus facilitating the improvement of the determination accuracy of subsequent crash handling measures, and further facilitating the improvement of the handling accuracy of application crashes.

[0121] In this optional embodiment, optionally, the module crash information may include a module table corresponding to the target application and a crash table corresponding to the target application;

[0122] Among them, the module table may record a combination of one or more of the module identifier of each functional module included in the target application, the function switch corresponding to each functional module, and the regular crash identifier corresponding to each functional module;

[0123] Among them, the crash table may record the crash identifier of each type of crash and / or the crash cause corresponding to each type of crash; among them, each regular crash identifier is one of the crash identifiers in the crash table.

[0124] Among them, each functional module may correspond to one or more regular crash identifiers, which is not limited in the embodiments of the present invention.

[0125] Optionally, the module identifier of each functional module may include the module ID (IDentity, identification number) of the functional module and / or the module name of the functional module, which is not limited in the embodiments of the present invention.

[0126] Optionally, the crash identifier of each type of crash may include the crash ID of the type of crash and / or the crash symbol of the type of crash, which is not limited in the embodiments of the present invention.

[0127] It can be seen that this optional embodiment can also record the information types specifically recorded in the module table and the crash table included in the module crash information, which is conducive to efficiently searching in the module table and the crash table whether there is information matching the current crash when a crash event occurs to determine the crash type, conducive to quickly ruling out unknown sudden crashes, and can improve the determination accuracy of the subsequent handling method for the crash event to improve the handling efficiency and accuracy of the crash event.

[0128] In this optional embodiment, optionally, according to the crash information, searching whether there is a matching module crash information in the module crash information to obtain a matching result may include the following operations:

[0129] Check whether there is target module information matching the target module in the module table and whether the target module information contains target crash information matching the crash cause corresponding to the target module;

[0130] When it is found that there is target module information matching the target module in the module table and the target module information contains target crash information matching the crash cause corresponding to the target module, it is determined that there is matching module crash information matching the crash information in the module crash information;

[0131] When it is found that there is no target module information matching the target module in the module table or the target module information does not record target crash information matching the crash cause corresponding to the target module, it is determined that there is no matching module crash information matching the crash information in the module crash information.

[0132] It can be seen that this optional embodiment can also determine that there is matching module crash information matching the crash information in the module crash information if target module information matching the target module is found in the module table and the target module information contains target crash information matching the crash cause corresponding to the target module. Otherwise, it is determined that there is no matching module crash information matching the crash information in the module crash information, which can improve the accuracy of determining the matching result, thereby facilitating improving the accuracy and flexibility of determining the processing method corresponding to the application crash.

[0133] In this optional embodiment, optionally, according to the crash analysis result and based on the function switch embedded in the target application, executing the crash processing operation for the crash event may include the following operations:

[0134] According to the crash analysis results, trigger the target function switch embedded in the target module of the target application to enable the corresponding protection function of the target module and repair the crash event;

[0135] After the target function switch is triggered, guidance information for the crash event is generated and fed back to the target user corresponding to the target end; the guidance information is used to prompt the target user that the target module has crashed and / or guide the target user to use other associated ends in the target application except the target end.

[0136] Among them, the protection function corresponding to the target module can be used to suspend the user from using the function provided by the target module. Among them, for example, it can be achieved by turning off the target function switch of the target module, which is not limited in the embodiment of the present invention.

[0137] Exemplarily, when the target end is an iOS end, the above guidance information can be used to guide the user to use the Android end or PC end of the target application, which is not limited in the embodiment of the present invention.

[0138] It can be seen that this optional embodiment can also trigger the target function switch pre-embedded in the target module of the target application according to the crash analysis result, so as to activate the protection function corresponding to the target module and repair the crash event. After triggering the target function switch, it can prompt the target user that the target module has crashed and / or guide the target user to use other associated terminals in the target application except the target terminal. It can activate the protection function and repair the crash event in time through the pre-embedded function switch, thereby improving the timeliness of handling application crashes and the timeliness of protecting application crashes. In addition, it can also guide users to avoid using the crashed function or the crashed terminal, so that users can still use the target application through other terminals in case of a crash, reducing the possibility that users cannot use the target application, which is beneficial to improving the user experience of the target application.

[0139] In this optional embodiment, optionally, triggering the target function switch pre-embedded in the target module of the target application according to the crash analysis result to activate the protection function corresponding to the target module and repair the crash event includes:

[0140] When the matching result in the crash analysis result is used to indicate that there is a matching module crash information in the module crash information that matches the crash information, trigger the target function switch pre-embedded in the target module of the target application to activate the protection function corresponding to the target module and repair the crash event;

[0141] When the matching result in the crash analysis result is used to indicate that there is no matching module crash information in the module crash information that matches the crash information, receive the target analysis result feedback by the developer corresponding to the target application for the crash event, and trigger the target function switch pre-embedded in the target module of the target application according to the target analysis result to activate the protection function corresponding to the target module and repair the crash event; wherein, the target analysis result is obtained by analyzing the crash log, the module crash information, and the programming code corresponding to the target module.

[0142] Optionally, after detecting that there is no matching module crash information in the module crash information that matches the crash information, a crash analysis request or a crash warning message can be sent to the developer corresponding to the target application first, and then the target analysis result feedback by the developer corresponding to the target application for the crash event is received. The embodiments of the present invention do not make any limitations.

[0143] It can be seen that this optional embodiment can also directly trigger the target function switch pre-buried in the target module of the target application if there is matching module crash information in the module crash information that matches the crash information; otherwise, it is necessary to first receive the target analysis results fed back by the developer for the crash event, and then trigger the above-mentioned target function switch according to the target analysis results to turn on the protection function corresponding to the target module and repair the crash event. Different crash handling methods can be proposed based on different crash analysis results, and the protection function can be automatically triggered when the crash is analyzed to be a known crash. When the crash is analyzed to be an unknown crash, the crash needs to be further analyzed and then the protection function is automatically triggered. The processing flexibility and efficiency of application crashes can be improved, which is conducive to further improving the protection flexibility and reliability of application crashes.

[0144] Embodiment 2

[0145] See also Figure 2 , Figure 2 : is a flowchart of a method for handling application crash based on multi-terminal collaboration disclosed in an embodiment of the present invention. Figure 2 The described multi-terminal collaborative application crash processing method can be applied to a multi-terminal collaborative application crash processing device, which may include a crash processing terminal, a crash processing device, a crash processing system, and a server, wherein the server may include a local server or a cloud server, which is not limited in the embodiments of the present invention. Figure 2 As shown, the application crash processing method based on multi-terminal collaboration may include the following operations:

[0146] 201. When it is detected that the target end of the target application captures a crash event, a crash log corresponding to the crash event is generated.

[0147] 202. Analyze the crash log to obtain a crash analysis result corresponding to the crash event.

[0148] 203. According to the crash analysis result, based on the function switch embedded in the target application, a crash processing operation for the crash event is executed.

[0149] In the embodiment of the present invention, optionally, after executing step 203, the operations of step 204 and / or step 205 may be executed, which is not limited in the embodiment of the present invention.

[0150] In the embodiment of the present invention, the multi-terminal protection measures corresponding to the target application include interface protection measures and / or module protection measures.

[0151] 204. According to the crash analysis result and the interface protection measures corresponding to the target application, based on the first associated end of the target application, control all second associated ends in the target application to suspend calling the target interface associated with the crash event.

[0152] In an embodiment of the present invention, the second associated end is an associated end in the target application that is associated with the first associated end; for example, when the first associated end is a firmware end, the second associated end may be a client connected to the firmware end, and the embodiment of the present invention does not make any limitations.

[0153] In an embodiment of the present invention, for example, the target interface associated with the crash event may be the interface corresponding to the target module where the crash event occurs, and the embodiment of the present invention does not make any limitations.

[0154] 205. According to the crash analysis result and the module protection measures corresponding to the target application, control at least one third associated end of the target application to trigger an associated function switch associated with the crash event, so as to enable a collaborative protection function corresponding to at least one third associated end.

[0155] In an embodiment of the present invention, for example, the third associated end may be any client of the target application, and the embodiment of the present invention does not make any limitations.

[0156] It should be noted that when steps 204 and 205 need to be executed, there is no sequence relationship between step 204 and step 205, that is, step 204 may occur before or after step 205 or occur simultaneously with step 205, and the embodiment of the present invention does not make any limitations.

[0157] In an embodiment of the present invention, for other detailed descriptions of steps 201 to 203, please refer to the detailed descriptions of steps 101 to 103 in Embodiment 1, and the embodiment of the present invention will not repeat them here.

[0158] It can be seen that the method described in the embodiment of the present invention can generate a crash log corresponding to the crash event when the target end of the target application captures a crash event, and obtain the corresponding crash analysis result by analyzing the crash log, and then perform a crash processing operation for the crash event based on the crash analysis result and through the function switch embedded in the target application, and control the associated end of the target application to perform a crash protection operation based on the crash analysis result and multi-end protection measures, and can collaboratively process application crash events by using the local embedded function switch and the multi-end protection measures of the other end, thereby improving the timeliness, accuracy and comprehensiveness of application crash processing, and further realizing timely capture and analysis of crashes online, and preventing various program design defects or unknown sudden crashes from spreading to other ends, which is beneficial to improving the crash protection reliability and comprehensiveness of the application program, and further beneficial to improving the operating security and reliability of the application, and is beneficial to improving the user experience of the application. In addition, through the interface protection measures and the first associated end of the target application, the second associated end can be controlled to suspend calling the target result related to the crash event, and / or, through the module protection measures, the third associated end can be controlled to trigger the associated function switch associated with the crash event. Protection against crash events from multiple ends can be achieved in a variety of ways, and the flexibility in determining the protection method for application crashes can be improved, which is conducive to improving the flexibility and comprehensiveness of protection against application crashes, and further helps to reduce the possibility of the crash spreading to other ends, so that users can use other functions of other ends normally, which is conducive to further improving the operating reliability of the application.

[0159] In an optional embodiment, according to the crash analysis result and the interface protection measures corresponding to the target application, based on the first associated end of the target application, controlling all second associated ends in the target application to suspend calling the target interface associated with the crash event may include the following operations:

[0160] Based on a preset communication mode corresponding to the target application, the crash analysis result is transmitted to the first associated end of the target application, and the first associated end of the target application is triggered to enable an interface protection function corresponding to the crash analysis result; the preset communication mode includes a preset connection protocol and / or a second preset interface;

[0161] Based on the interface protection function, the first association end is controlled to suspend all second association ends in the target application from calling the target interface associated with the crash analysis result.

[0162] The preset connection protocol may be a pre-set communication protocol, which is not limited in the embodiment of the present invention.

[0163] It can be seen that this optional embodiment can transmit the crash analysis result to the first associated end based on the preset communication method, and trigger the first associated end of the target application to enable the interface protection function corresponding to the crash analysis result, thereby controlling the first associated end to suspend the second associated end associated with it from calling the target interface, which can improve the timeliness and accuracy of control over the interface related to the crash event, thereby helping to reduce the possibility of other ends using the interface of the crash function module, and further helping to improve the flexibility of application crash protection, and further helping to reduce the possibility of the crash spreading to other ends.

[0164] In another optional embodiment, according to the crash analysis result and the module protection measures corresponding to the target application, controlling at least one third associated terminal of the target application to trigger an associated function switch associated with the crash event to enable a collaborative protection function corresponding to the at least one third associated terminal may include the following operations:

[0165] Based on the cloud corresponding to the target application, transmitting the crash analysis result to at least one third associated end of the target application;

[0166] At least one third associated terminal of the target application is controlled to trigger an associated function switch associated with the crash analysis result, so as to enable a collaborative protection function corresponding to the at least one third associated terminal.

[0167] Among them, optionally, the above-mentioned associated function switch can be a function switch pre-embedded in the module corresponding to the target module in the third associated terminal; further, the collaborative protection function corresponding to the third associated terminal can be used to suspend the user from using the function provided by the function module corresponding to the target module on the third associated terminal. Exemplarily, when the target terminal is an iOS terminal and the target module is a login module, the above-mentioned associated function switch can be a function switch pre-embedded in the login module of the Android terminal, which is not limited in the embodiment of the present invention.

[0168] It can be seen that this optional embodiment can also transmit the crash analysis results to at least one third associated end based on the cloud corresponding to the target application, and control the third associated end to trigger the associated function switch to turn on the collaborative protection function corresponding to at least one third associated end, which can improve the timeliness and accuracy of control of the embedded function switches of the function modules related to the crash event, thereby helping to reduce the possibility of other ends using the crash function modules, and further helping to improve the flexibility of protection against application crashes, and further helping to further reduce the possibility of the crash spreading to other ends.

[0169] In the embodiment of the present invention, the process of the application crash processing method based on multi-terminal collaboration can be referred to as follows: Figure 3 , Figure 3 is a flowchart of another method for handling application crash based on multi-terminal collaboration disclosed in an embodiment of the present invention.Figure 3 As shown, the method may include the following operations:

[0170] After capturing the Crash, the original crash log is symbolized and reported as a symbolized log; after analyzing the symbolized log, the local function switch embedded in the target module where the crash occurred is triggered, and instructions are issued to the corresponding other terminals to control the other terminals to suspend the use of the target module, so as to control multiple terminals to suspend the use of the target module and prevent the crash from spreading; the application can only run normally after the crash of the target module is repaired.

[0171] In the embodiment of the present invention, for example, the timing diagram of the multi-terminal collaboration-based application crash processing method can be found in Figure 4 , Figure 4 is a timing diagram of an application crash processing method based on multi-terminal collaboration disclosed in an embodiment of the present invention. Among them, for example, Figure 4 As shown, assuming that the target application includes an iOS end, a background, a firmware end, an Android end, a PC end, and a Web end, and the target end where the crash occurs is an iOS end, the timing flow of the method can be described as follows:

[0172] After the original crash log, that is, the crash event, is captured on the iOS side, the original crash log is first symbolized, and then the symbolized log is automatically reported to the background. The target module where the crash occurred and the cause of the crash are analyzed in the background, and then the pre-buried function switch of the target module is triggered to close the target module and guide the user to use other ends of the target application. The background can also simultaneously inform other associated ends (such as: Android, PC and Web) of the crash analysis results to trigger the pre-buried function switches of other associated ends. The background can also trigger the interface protection function of the firmware end, thereby controlling the associated end connected to the firmware end to suspend calling the interface corresponding to the target module, which is not limited in the embodiments of the present invention.

[0173] Embodiment 3

[0174] See also Figure 5 , Figure 5 1 is a schematic diagram of a structure of an application crash processing device based on multi-terminal collaboration disclosed in an embodiment of the present invention. Figure 5 The described application crash processing device based on multi-terminal collaboration may include one of a crash processing terminal, a crash processing device, a crash processing system and a server, wherein the server may include a local server or a cloud server, which is not limited in the embodiment of the present invention. Figure 5 As shown, the application crash processing device based on multi-terminal collaboration may include:

[0175] A generation module 301, configured to generate a crash log corresponding to a crash event when it is detected that a target end of a target application captures a crash event;

[0176] An analysis module 302, configured to analyze the crash log to obtain a crash analysis result corresponding to the crash event;

[0177] A crash handling module 303, configured to perform a crash handling operation for the crash event based on the crash analysis result and a function switch pre-buried in the target application;

[0178] A crash protection module 304, configured to control at least one associated end of the target application to perform a crash protection operation for the crash event according to the crash analysis result and multi-end protection measures corresponding to the target application.

[0179] It can be seen that implementing the device described in the embodiments of the present invention can generate a crash log corresponding to a crash event when a target end of a target application captures a crash event, obtain a corresponding crash analysis result by analyzing the crash log, and then perform a crash handling operation for the crash event according to the crash analysis result and through a function switch pre-buried in the target application, and control the associated end of the target application to perform a crash protection operation according to the crash analysis result and multi-end protection measures. It can cooperate to process application crash events by using local pre-buried function switches and multi-end protection measures of other ends, thereby improving the timeliness, accuracy, and comprehensiveness of processing application crashes, and further realizing timely capture, analysis of crashes online, and prevention of various programming defects or unknown sudden crashes from spreading to other ends. Furthermore, it is beneficial to improve the reliability and comprehensiveness of crash protection of application programs, and further beneficial to improve the running security and running reliability of applications, and beneficial to improve the user experience of application programs.

[0180] In an optional embodiment, the specific manner in which the generation module 301 generates a crash log corresponding to a crash event may include:

[0181] Obtain the original crash log corresponding to the crash event;

[0182] Based on a first preset interface corresponding to the target end, parse the original crash log to obtain a parsing result corresponding to the original crash log;

[0183] Based on a first preset interface corresponding to the target end, generate a symbolized log corresponding to the original crash log according to the parsing result as the crash log corresponding to the crash event.

[0184] It can be seen that the device described in implementing this optional embodiment can parse the original crash log corresponding to the obtained crash event based on the first preset interface corresponding to the target end, obtain the parsing result corresponding to the original crash log, and then generate a symbolized log as the crash log corresponding to the crash event based on the parsing result, which can implement the preliminary parsing of the crash event and generate a more standardized crash log, improving the generation accuracy and standardization of the crash log and being beneficial to improving the analysis accuracy of the subsequent crash log.

[0185] In another optional embodiment, the specific manner in which the analysis module 302 analyzes the crash log to obtain the crash analysis result corresponding to the crash event may include:

[0186] Analyze the crash log based on the crash analysis framework corresponding to the target end to obtain the crash information corresponding to the crash event; the crash information includes the target module where the crash event occurs and the cause of the crash corresponding to the target module;

[0187] Obtain the module crash information corresponding to the target application stored in advance; the module crash information is used to represent the association relationship between each functional module included in the target application and various crashes;

[0188] According to the crash information, check whether there is a matching module crash information in the module crash information that matches the crash information to obtain a matching result;

[0189] Among them, the crash analysis result includes the crash information and / or the matching result.

[0190] It can be seen that the device described in implementing this optional embodiment can analyze the crash log based on the crash analysis framework corresponding to the target end to obtain the crash information including the target module where the crash event occurs and the cause of the crash corresponding to the target module, and according to the crash information, check whether there is a matching module crash information in the module crash information corresponding to the target application stored in advance to obtain a matching result, which can improve the analysis accuracy and comprehensiveness of the crash log, thus being beneficial to improving the determination accuracy of subsequent crash handling measures and further being beneficial to improving the handling accuracy of application crashes.

[0191] In this optional embodiment, optionally, the module crash information includes the module table corresponding to the target application and the crash table corresponding to the target application;

[0192] Among them, the module table records one or more combinations of the module identifiers of each functional module included in the target application, the function switches corresponding to each functional module, and the regular crash identifiers corresponding to each functional module;

[0193] The crash table records the crash identifier of each crash and / or the crash cause corresponding to each crash; and each conventional crash identifier is one of the crash identifiers in the crash table.

[0194] It can be seen that the device described in implementing this optional embodiment can also record the module table contained in the module crash information and the type of information specifically recorded in the crash table, which is beneficial to efficiently search the module table and the crash table for information matching the current crash when a crash event occurs, so as to determine the crash type, which is beneficial to quickly eliminate unknown sudden crashes, and can improve the accuracy of determining the subsequent handling method for the crash event, so as to improve the processing efficiency and accuracy of the crash event.

[0195] In this optional embodiment, optionally, the specific manner in which the crash processing module 303 performs the crash processing operation for the crash event based on the crash analysis result and the function switch embedded in the target application may include:

[0196] According to the crash analysis results, trigger the target function switch embedded in the target module of the target application to enable the corresponding protection function of the target module and repair the crash event;

[0197] After the target function switch is triggered, guidance information for the crash event is generated and fed back to the target user corresponding to the target terminal; the guidance information is used to prompt the target user that the target module has crashed and / or guide the target user to use other associated terminals in the target application except the target terminal;

[0198] The crash processing module 303 triggers the target function switch embedded in the target module of the target application according to the crash analysis result to enable the protection function corresponding to the target module and repair the specific manner of the crash event, including:

[0199] When the matching result in the crash analysis result is used to indicate that there is matching module crash information in the module crash information that matches the crash information, triggering a target function switch embedded in the target module of the target application to enable a protection function corresponding to the target module and repair the crash event;

[0200] When the matching result in the crash analysis result is used to indicate that there is no matching module crash information in the module crash information that matches the crash information, a target analysis result fed back by a developer corresponding to the target application for the crash event is received, and based on the target analysis result, a target function switch embedded in the target module of the target application is triggered to turn on the protection function corresponding to the target module and repair the crash event; wherein the target analysis result is obtained based on the analysis of the crash log, the module crash information and the programming code corresponding to the target module.

[0201] It can be seen that the device described in the optional embodiment can also trigger the target function switch pre-embedded by the target application in the target module according to the crash analysis result, so as to turn on the protection function corresponding to the target module and repair the crash event. After triggering the target function switch, it can prompt the target user that the target module has crashed and / or guide the target user to use other associated ends in the target application except the target end. The protection function can be turned on and the crash event can be repaired in time through the pre-embedded function switch, thereby improving the timeliness of handling application crashes and the timeliness of protecting application crashes. In addition, it can also guide users to avoid using the crashed function or the crashed end, so that users can still use the target application through other ends in case of a crash, reducing the possibility that users cannot use the target application, which is beneficial to improving the user experience of the target application. Moreover, if there is matching module crash information in the module crash information that matches the crash information, the target function switch pre-embedded by the target application in the target module can be directly triggered; otherwise, it is necessary to first receive the target analysis result feedback by the developer for the crash event, and then trigger the above target function switch according to the target analysis result to turn on the protection function corresponding to the target module and repair the crash event. Different crash handling methods can be proposed based on different crash analysis results, and the protection function can be automatically triggered when the crash is analyzed as a known crash, and the protection function needs to be further analyzed and then automatically triggered when the crash is analyzed as an unknown crash, which can improve the flexibility and efficiency of handling application crashes, and thus is beneficial to further improving the flexibility and reliability of protecting application crashes.

[0202] In another optional embodiment, the multi-end protection measures include interface protection measures and / or module protection measures;

[0203] Among them, the specific manner in which the crash protection module 304 controls at least one associated end of the target application to perform a crash protection operation for the crash event according to the crash analysis result and the multi-end protection measures corresponding to the target application may include:

[0204] According to the crash analysis result and the interface protection measures corresponding to the target application, based on the first associated end of the target application, control all second associated ends in the target application to suspend calling the target interface associated with the crash event; the second associated end is an associated end in the target application associated with the first associated end; and / or,

[0205] According to the crash analysis result and the module protection measures corresponding to the target application, control at least one third associated end of the target application to trigger the associated function switch associated with the crash event, so as to turn on the collaborative protection function corresponding to at least one third associated end.

[0206] It can be seen that the device described in implementing this optional embodiment can, through interface protection measures and the first associated end of the target application, control the second associated end to suspend invoking the target result related to the crash event, and / or, through module protection measures, control the third associated end to trigger the associated function switch related to the crash event. It can implement crash protection from multiple ends in various ways, improving the determination flexibility of the application crash protection method, thereby facilitating improving the protection flexibility and comprehensiveness of application crashes, and further facilitating reducing the possibility of crashes spreading to other ends, enabling users to normally use other functions of other ends, and facilitating further improving the running reliability of the application program.

[0207] In this optional embodiment, optionally, the specific manner in which the crash protection module 304 controls all second associated ends in the target application to suspend invoking the target interface related to the crash event based on the crash analysis result and the interface protection measures corresponding to the target application, through the first associated end of the target application, may include:

[0208] Based on the preset communication method corresponding to the target application, transmit the crash analysis result to the first associated end of the target application, and trigger the first associated end of the target application to enable the interface protection function corresponding to the crash analysis result; the preset communication method includes a preset connection protocol and / or a second preset interface;

[0209] Based on the interface protection function, control the first associated end to suspend all second associated ends in the target application from invoking the target interface related to the crash analysis result;

[0210] Among them, the specific manner in which the crash protection module 304 controls at least one third associated end of the target application to trigger the associated function switch related to the crash event, based on the crash analysis result and the module protection measures corresponding to the target application, to enable the collaborative protection function corresponding to at least one third associated end may include:

[0211] Based on the cloud corresponding to the target application, transmit the crash analysis result to at least one third associated end of the target application;

[0212] Control at least one third associated end of the target application to trigger the associated function switch related to the crash analysis result, to enable the collaborative protection function corresponding to at least one third associated end.

[0213] It can be seen that the device described in this alternative embodiment can also transmit the crash analysis result to the first associated end based on a preset communication method, and trigger the first associated end of the target application to enable the interface protection function corresponding to the crash analysis result, thereby controlling the first associated end to suspend the second associated end associated therewith from calling the target interface, which can improve the timeliness and accuracy of controlling the interface related to the crash event, thereby facilitating reducing the possibility of other ends using the interface of the crash function module, further facilitating improving the protection flexibility of application crashes, and further facilitating reducing the possibility of the crash spreading to other ends; and, it can also transmit the crash analysis result to at least one third associated end based on the cloud corresponding to the target application, and control the third associated end to trigger the associated function switch to enable the collaborative protection function corresponding to at least one third associated end, which can improve the timeliness and accuracy of controlling the pre-buried function switch of the function module related to the crash event, thereby facilitating reducing the possibility of other ends using the crash function module, further facilitating improving the protection flexibility of application crashes, and further facilitating reducing the possibility of the crash spreading to other ends.

[0214] Embodiment 4

[0215] Please refer to Figure 6 , Figure 6 which is a schematic structural diagram of another application crash handling device based on multi-end collaboration disclosed in the embodiments of the present invention. As Figure 6 shown, the application crash handling device based on multi-end collaboration may include:

[0216] A memory 401 storing executable program code;

[0217] A processor 402 coupled to the memory 401;

[0218] The processor 402 calls the executable program code stored in the memory 401 and executes some or all of the steps in the application crash handling method based on multi-end collaboration described in Embodiment 1 or Embodiment 2 of the present invention.

[0219] Embodiment 5

[0220] The embodiments of the present invention disclose a computer storage medium, which stores computer instructions that, when called, are used to execute some or all of the steps in the application crash handling method based on multi-end collaboration described in Embodiment 1 or Embodiment 2 of the present invention.

[0221] Embodiment 6

[0222] An embodiment of the present invention discloses a computer program product, which includes a non-transitory computer-readable storage medium storing a computer program, and the computer program is operable to cause a computer to execute some or all of the steps of the application crash handling method based on multi-terminal collaboration described in Embodiment 1 or Embodiment 2.

[0223] The device embodiments described above are only illustrative. The modules described as separate components may or may not be physically separated. The components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed to multiple network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment. A person of ordinary skill in the art can understand and implement it without creative effort.

[0224] Through the specific descriptions of the above embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware. Based on such an understanding, the essence of the above technical solution, or the part that contributes to the prior art, can be embodied in the form of a software product. The computer software product can be stored in a computer-readable storage medium, and the storage medium includes a read-only memory (ROM), a random access memory (RAM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), a one-time programmable read-only memory (OTPROM), an electrically-erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc memories, a magnetic disk memory, a tape memory, or any other computer-readable medium capable of carrying or storing data.

[0225] Finally, it should be noted that: What is disclosed by an application crash handling method and device based on multi-terminal collaboration disclosed in the embodiments of the present invention is only the preferred embodiments of the present invention, which are only used to illustrate the technical solutions of the present invention, rather than limiting it; Although the present invention has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: They can still modify the technical solutions recorded in the foregoing embodiments, or perform equivalent replacements on some of the technical features; And these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for handling application crash based on multi-terminal collaboration, characterized in that: The method comprises: When it is detected that the target end of the target application captures a crash event, a crash log corresponding to the crash event is generated; Analyze the crash log to obtain a crash analysis result corresponding to the crash event; According to the crash analysis result, based on the function switch embedded in the target application, executing a crash processing operation for the crash event; According to the crash analysis result and the multi-terminal protection measures corresponding to the target application, at least one associated terminal of the target application is controlled to perform a crash protection operation for the crash event.

2. The method for handling application crash based on multi-terminal collaboration according to claim 1, characterized in that: The generating a crash log corresponding to the crash event includes: Obtaining the original crash log corresponding to the crash event; Parsing the original crash log based on a first preset interface corresponding to the target end to obtain a parsing result corresponding to the original crash log; Based on the first preset interface corresponding to the target end and according to the parsing result, a symbolized log corresponding to the original crash log is generated as the crash log corresponding to the crash event.

3. The method for handling application crash based on multi-terminal collaboration according to claim 1, characterized in that: The analyzing the crash log to obtain a crash analysis result corresponding to the crash event includes: Based on the crash analysis framework corresponding to the target end, the crash log is analyzed to obtain crash information corresponding to the crash event; the crash information includes the target module where the crash event occurs and the crash cause corresponding to the target module; Acquire pre-stored module crash information corresponding to the target application; the module crash information is used to indicate the association relationship between each functional module included in the target application and multiple crashes; According to the crash information, searching whether there is matching module crash information matching the crash information in the module crash information to obtain a matching result; The crash analysis result includes the crash information and / or the matching result.

4. The method for handling application crash based on multi-terminal collaboration according to claim 3 is characterized in that: The module crash information includes a module table corresponding to the target application and a crash table corresponding to the target application; The module table records a combination of one or more of a module identifier of each functional module included in the target application, a function switch corresponding to each functional module, and a conventional crash identifier corresponding to each functional module; The crash table records the crash identifier of each crash and / or the crash reason corresponding to each crash; and each of the conventional crash identifiers is one of the crash identifiers in the crash table.

5. The method for handling application crash based on multi-terminal collaboration according to claim 3, characterized in that: The performing a crash processing operation for the crash event according to the crash analysis result and based on the function switch embedded in the target application includes: According to the crash analysis result, triggering a target function switch pre-buried by the target application in the target module to enable a protection function corresponding to the target module and repair the crash event; After the target function switch is triggered, guidance information for the crash event is generated, and the guidance information is fed back to the target user corresponding to the target terminal; the guidance information is used to prompt the target user that the target module has crashed and / or guide the target user to use other associated terminals in the target application except the target terminal; The method of triggering a target function switch pre-embedded in the target module by the target application according to the crash analysis result to enable a protection function corresponding to the target module and repair the crash event includes: When the matching result in the crash analysis result is used to indicate that there is matching module crash information matching the crash information in the module crash information, triggering a target function switch pre-embedded in the target module by the target application to enable a protection function corresponding to the target module and repair the crash event; When the matching result in the crash analysis result is used to indicate that there is no matching module crash information matching the crash information in the module crash information, a target analysis result fed back by a developer corresponding to the target application for the crash event is received, and based on the target analysis result, a target function switch embedded in the target module of the target application is triggered to turn on the protection function corresponding to the target module and repair the crash event; wherein the target analysis result is obtained based on the analysis of the crash log, the module crash information and the programming code corresponding to the target module.

6. The method for handling application crash based on multi-terminal collaboration according to any one of claims 1 to 5, characterized in that: The multi-terminal protection measures include interface protection measures and / or module protection measures; The controlling at least one associated terminal of the target application to perform a crash protection operation for the crash event according to the crash analysis result and the multi-terminal protection measures corresponding to the target application includes: According to the crash analysis result and the interface protection measures corresponding to the target application, based on the first association end of the target application, all second association ends in the target application are controlled to suspend calling the target interface associated with the crash event; the second association end is the association end associated with the first association end in the target application; and / or, According to the crash analysis result and the module protection measures corresponding to the target application, at least one third associated end of the target application is controlled to trigger an associated function switch associated with the crash event to enable collaborative protection functions corresponding to all the third associated ends.

7. The method for handling application crash based on multi-terminal collaboration according to claim 6, characterized in that: The step of controlling all second associated ends in the target application to suspend calling a target interface associated with the crash event based on the first associated end of the target application according to the crash analysis result and the interface protection measures corresponding to the target application comprises: Based on a preset communication mode corresponding to the target application, the crash analysis result is transmitted to a first associated end of the target application, and the first associated end of the target application is triggered to enable an interface protection function corresponding to the crash analysis result; the preset communication mode includes a preset connection protocol and / or a second preset interface; Based on the interface protection function, controlling the first association end to suspend all second association ends in the target application from calling a target interface associated with the crash analysis result; The controlling, according to the crash analysis result and the module protection measures corresponding to the target application, at least one third associated terminal of the target application to trigger an associated function switch associated with the crash event to enable the collaborative protection functions corresponding to all the third associated terminals includes: Based on the cloud corresponding to the target application, transmitting the crash analysis result to at least one third associated end of the target application; Control at least one of the third associated terminals of the target application to trigger an associated function switch associated with the crash analysis result, so as to enable collaborative protection functions corresponding to all the third associated terminals.

8. An application crash processing device based on multi-terminal collaboration, characterized in that: The device comprises: A generating module, configured to generate a crash log corresponding to a crash event when detecting that a target end of a target application captures a crash event; An analysis module, used to analyze the crash log to obtain a crash analysis result corresponding to the crash event; A crash processing module, configured to perform a crash processing operation for the crash event according to the crash analysis result and based on a function switch pre-embedded in the target application; A crash protection module is used to control at least one associated terminal of the target application to perform a crash protection operation for the crash event according to the crash analysis result and the multi-terminal protection measures corresponding to the target application.

9. An application crash processing device based on multi-terminal collaboration, characterized in that: The device comprises: A memory storing executable program code; a processor coupled to the memory; The processor calls the executable program code stored in the memory to execute the application crash handling method based on multi-terminal collaboration as described in any one of claims 1-7.

10. A computer storage medium, characterized in that: The computer storage medium stores computer instructions, which, when called, are used to execute the application crash processing method based on multi-terminal collaboration as described in any one of claims 1-7.

Images