Abnormality processing method, electronic equipment and server

Abstract

The embodiment of the invention is applied to the technical field of electronics, and provides an exception handling method, electronic equipment and a server. And in response to a feedback operation of the user for the application flash quit exception, the electronic equipment obtains the target log file. Wherein the target log file is a log file generated by a target third-party application, and the target third-party application is a third-party application in the electronic equipment where the application flash quit exception occurs. And then, the electronic equipment sends the target log file to a server. And then, the electronic equipment receives an abnormal positioning result sent by the server. Wherein the exception positioning result is obtained based on analysis of the target log file. And then, the electronic equipment executes a result feedback operation according to the abnormal positioning result. Wherein the result feedback operation comprises the step of feeding back the reason of the application flash quit exception. According to the method and the device, the flash quit problem can be quickly positioned, and the user is timely informed of the reason of the flash quit abnormity.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of electronic technology, and in particular to an exception handling method, an electronic device, and a server. Background Art

[0002] With the continuous development of electronic devices, multiple applications (APPs) may be installed on electronic devices for users to use. However, in some cases, when the application is started, some abnormal problems such as flash back may occur, thereby affecting the user's experience.

[0003] Therefore, how to accurately locate the crash problem and accurately inform users of the cause of the crash is an issue that needs to be solved urgently. Summary of the invention

[0004] The embodiments of the present application provide an exception handling method, an electronic device, and a server for quickly locating a crash problem and promptly informing a user of the cause of the crash problem.

[0005] To achieve the above objectives, the embodiments of the present application adopt the following technical solutions:

[0006] In the first aspect, an exception handling method is provided, which is applied to an electronic device, wherein a third-party application installed in the electronic device has a security reinforcement service, which is implemented by a security reinforcement program, and the electronic device has updated the system version. In this method, in response to a user's feedback operation on an application flashback exception, the electronic device obtains a target log file. Among them, the application flashback exception is an abnormal problem generated when the target third-party application is cold started. The target log file is a log file generated by the target third-party application, and the target third-party application is a third-party application in which the application flashback exception occurs in the electronic device. Afterwards, the electronic device can send the target log file to the server. Afterwards, the electronic device can receive the abnormal location result sent by the server. Among them, the abnormal location result is obtained based on the analysis of the target log file. Afterwards, the electronic device performs a result feedback operation based on the abnormal location result. Among them, the result feedback operation includes feedback on the cause of the application flashback exception.

[0007] Among them, the exception location result is used to indicate whether the reason for the application crash is that the target third-party application is incompatible with the updated system version. When the target third-party application is incompatible with the updated system version, the target third-party application cannot run the security hardening program normally. In the updated system version, if the API used by the security hardening program has been changed or deleted, and the target third-party application is incompatible with the updated system version, the target third-party application will not be able to run the security hardening program normally through the original API, that is, the security hardening service of the target third-party application cannot be realized, which will cause the target third-party application to crash abnormally.

[0008] In the embodiment of the present application, when the user feedback about the application flashback exception is detected, the electronic device can send the acquired target log file to the server so that the server can locate the cause of the application flashback exception. And, when the electronic device receives the abnormal location result sent by the server, it performs the result feedback operation according to the abnormal location result. In this way, not only can the automatic analysis of the application flashback exception be realized, but also the tester does not need to manually analyze the cause of the problem, while reducing the manpower cost, the analysis efficiency of the application flashback exception is improved; and, by performing the result feedback operation, the electronic device can timely feedback the cause of the application flashback exception to the user, so that the user can quickly know the cause of the application flashback exception, minimize the closed loop time of the application flashback exception, and improve the feedback efficiency of the problem location result. In addition, it can reduce the occurrence of the situation where the user mistakenly believes that the application flashback exception is a problem of the electronic device itself, and improve the user's favorability and satisfaction with the electronic device. In addition, since the abnormal location result is obtained by analyzing the target log file, the accurate determination of the abnormal location result can be realized, and the situation where the result feedback display error is caused by inaccurate determination of the cause of the application flashback exception is reduced, thereby improving the user's favorability and satisfaction with the electronic device.

[0009] In a possible implementation of the first aspect, the process of the electronic device performing the result feedback operation may specifically include: the electronic device may display first feedback information, wherein the first feedback information is used to indicate the reason for the abnormal flash back of the application.

[0010] In the embodiment of the present application, the electronic device can intuitively display the reason for the abnormal application crash by displaying the first feedback information, so that the user can quickly know the reason for the abnormal application crash, which minimizes the closed loop time of the abnormal application crash and improves the user experience. In addition, it can reduce the situation where the user mistakenly believes that the abnormal application crash is a problem of the electronic device itself, which affects the user's favorability and satisfaction with the electronic device.

[0011] In a possible implementation manner of the first aspect, the process of the electronic device performing the result feedback operation may further include: the electronic device outputting the first feedback information through a preset voice output manner.

[0012] In the embodiment of the present application, the electronic device outputs the first feedback information by voice, which can reduce the time for the user to trigger the electronic device to display the first feedback information, so that the user can know the reason for the abnormal application flash back more quickly, and the closed loop time of the abnormal application flash back is reduced to the greatest extent, thereby improving the user's experience. In addition, it can reduce the occurrence of situations where the user's favorability and satisfaction with the electronic device is affected by the user's mistaken belief that the abnormal application flash back is a problem of the electronic device itself.

[0013] In a possible implementation of the first aspect, the method further includes: the electronic device receives an abnormal positioning result and an abnormal solution sent by the server. The abnormal positioning result is used to indicate that the reason for the application flash back abnormality is that the target third-party application is incompatible with the updated system version, and the abnormal solution includes abnormal solution progress information and / or abnormal solution time. Afterwards, the electronic device can perform a result feedback operation based on the abnormal positioning result and the abnormal solution. The result feedback operation also includes feedback of the abnormal solution.

[0014] In some cases, the exception resolution progress information may be used to indicate that there is a planned version of the target third-party application that can resolve the application crash exception and is compatible with the updated system version. The exception resolution time includes the release time of the planned version.

[0015] In other cases, the exception resolution progress information is also used to indicate that the above-mentioned planned version does not exist, and to prompt the user to provide feedback on the application crash exception through the preset feedback path of the target third-party application.

[0016] In the embodiment of the present application, since the result feedback operation can be used to provide users with feedback on the reasons for the application crash and the solutions to the exceptions, the user can not only know the reasons for the application crash, but also the solutions to the application crash, which provides convenient conditions for subsequent smoother use of the target third-party application.

[0017] In a possible implementation of the first aspect, the process of the electronic device performing the result feedback operation may specifically include: the electronic device may display second feedback information, wherein the second feedback information is used to indicate the cause of the application crash and a solution to the exception.

[0018] In an embodiment of the present application, the electronic device can intuitively display the cause of the application crash and the solution to the application crash by displaying the second feedback information, so that the user can clearly understand the solution of the target third-party application to solve the application crash, which is convenient for the user to follow up the progress of the solution to the application crash in real time, and provides convenient conditions for the subsequent smoother use of the target third-party application.

[0019] In a possible implementation manner of the first aspect, the process of the electronic device performing the result feedback operation may further include: the electronic device may output the second feedback information in a preset voice output manner.

[0020] In an embodiment of the present application, the electronic device can reduce the time it takes for the user to trigger the electronic device to display the first feedback information by outputting the second feedback information through voice, so that the user can more quickly know the cause of the application crash and the solution to the application crash, so that the user can clearly understand the solution of the target third-party application to solve the application crash, which is convenient for the user to follow up the progress of solving the application crash in real time, and provides convenient conditions for smoother use of the target third-party application in the future.

[0021] In a possible implementation of the first aspect, the process of the electronic device acquiring the target log file may specifically include: in response to a user's feedback operation on the application crash exception, the electronic device acquires multiple log files located within a preset time period before and after the abnormal occurrence time of the application crash exception. Afterwards, the electronic device may determine the target log file from the multiple log files.

[0022] In an embodiment of the present application, the electronic device determines the target log file from multiple log files located within the time of occurrence of the application crash exception and within a preset time period before the exception, which can provide a basis for subsequent accurate determination of the exception location result, reduce the occurrence of incorrect result feedback display due to inaccurate determination of the cause of the application crash exception, and thereby improve the user's favorability and satisfaction with the electronic device.

[0023] In a possible implementation of the first aspect, the process of determining the target log file from the multiple log files may specifically include: the electronic device obtains at least one log file in the first folder from the multiple log files. The first folder is used to store log files generated when an abnormal problem occurs during the operation of an application of the electronic device. The abnormal problem includes an application crash. Afterwards, the electronic device may determine the target log file from the at least one log file.

[0024] The plurality of log files may include at least one log file in a first folder and at least two log files in a second folder. The second folder is used to store all log files generated during the operation of the electronic device. The first folder is a dropbox folder. The second folder is android_logs.

[0025] In the embodiment of the present application, it is considered that the above-mentioned multiple log files may include not only log files in the dropbox folder, but also log files in android_logs. Moreover, the number of log files in android_logs is relatively large. If the electronic device parses each log file in android_logs, it will occupy too many computing resources of the electronic device. Therefore, in order to reduce unnecessary waste of resources, the electronic device can only analyze the log files included in the first folder of the multiple log files. In this way, not only the utilization rate of computing resources can be improved, but also the cause of the application flash back exception can be quickly located, thereby improving the analysis efficiency of the application flash back exception.

[0026] In a possible implementation of the first aspect, the process of the electronic device determining a target log file from a plurality of log files may further include: for each log file in the plurality of log files, the electronic device may detect the log file to obtain a log detection result. The log detection result is used to characterize whether the log file belongs to a log file of a third-party application. In the case where the log detection result characterizes that the log file belongs to a log file of a third-party application, if the third-party application corresponding to the log file is the target third-party application, the electronic device may determine that the log file is the target log file.

[0027] In the embodiment of the present application, only when the log file belongs to the log file of a third-party application and the third-party application corresponding to the log file is the target third-party application, can the log file be used as the target log file to be sent to the server for log analysis, so as to determine the abnormal location result of the application flash back abnormality. In this way, the target log file can be accurately determined, which provides a basis for the subsequent accurate determination of the abnormal location result, reduces the occurrence of result feedback display errors due to inaccurate determination of the cause of the application flash back abnormality, and thus improves the user's favorability and satisfaction with the electronic device.

[0028] In a possible implementation of the first aspect, the process of the above-mentioned electronic device detecting the log file for each of the multiple log files may specifically include: the electronic device detects the log files in chronological order from back to front according to the generation time of the multiple log files, starting from the log file whose generation time is closest to the time when the abnormality occurred.

[0029] In the embodiment of the present application, it is considered that the log files close to the time when the problem occurred can reflect more accurate information, that is, the closer the log files are to the time when the problem occurred, the more accurately they can reflect whether the target third-party application is compatible with the updated system version. Therefore, in order to improve the accuracy of problem location, the electronic device can analyze the log files in order from back to front according to the generation time of the above-mentioned multiple log files, starting from the log file closest to the time when the problem occurred, to determine whether the cause of the application flash back exception is that the target third-party application is incompatible with the updated system version. In this way, the abnormal location result can be determined quickly and accurately, and the closed-loop time of the application flash back exception can be reduced as much as possible, so that users can quickly know the cause of the application flash back exception, thereby improving the user experience.

[0030] In a possible implementation of the first aspect, the process of the above-mentioned electronic device detecting the log file may specifically include: when the file name of the log file includes preset characters, the log detection result obtained by the electronic device can indicate that the log file belongs to a log file of a third-party application; or, when the file name of the log file does not include preset characters, the log detection result obtained by the electronic device can indicate that the log file does not belong to a log file of a third-party application.

[0031] The preset characters may include data_app_native_crash and / or data_app_crash.

[0032] In this application, only when the file name of the log file includes preset characters can it be determined that the log file belongs to a log file of a third-party application. In this way, accurate detection of the log file can be achieved, providing a basis for subsequent accurate determination of the target log file.

[0033] In a possible implementation of the first aspect, before the electronic device obtains the target log file, the method further includes: when the electronic device detects that a log feedback is enabled, if an application crashes, in response to a user triggering an operation to feedback a problem control in a pull-down notification bar, the electronic device may display a problem description interface. Thereafter, the electronic device may obtain description information of the application crash entered by the user on the problem description interface.

[0034] In an embodiment of the present application, the electronic device can determine the application crash exception filled in by the user based on the description information of the application crash exception entered by the user in the problem description interface, so as to obtain the target log file based on the subsequent feedback operation of the application crash exception.

[0035] On the second aspect, the present application also provides an exception handling method, which is applied to a server, in which the server receives a target log file sent by an electronic device. The target log file is a log file generated by a target third-party application, and the target third-party application is a third-party application in which an application flashback exception occurs in the electronic device. Afterwards, the server can analyze the target log file to obtain an exception location result. Afterwards, the server can send the exception location result to the electronic device. The exception location result is used to enable the electronic device to feedback the cause of the application flashback exception to the user.

[0036] Among them, the exception location result is used to indicate whether the reason for the application crash is that the target third-party application is incompatible with the updated system version. When the target third-party application is incompatible with the updated system version, the target third-party application cannot run the security hardening program normally. In the updated system version, if the API used by the security hardening program has been changed or deleted, and the target third-party application is incompatible with the updated system version, the target third-party application will not be able to run the security hardening program normally through the original API, that is, the security hardening service of the target third-party application cannot be realized, which will cause the target third-party application to crash abnormally.

[0037] In an embodiment of the present application, after obtaining the abnormal positioning result, the server can send the abnormal positioning result to the electronic device so that the mobile phone can promptly notify the user of the abnormal positioning result, so that the user can quickly know the reason for the abnormal application flash back, which minimizes the closed-loop time of the abnormal application flash back and improves the feedback efficiency of the abnormal positioning result. In addition, it can reduce the situation where the user mistakenly believes that the abnormal application flash back is a problem with the electronic device itself, and improve the user's favorability and satisfaction with the electronic device. In addition, since the abnormal positioning result is obtained by analyzing the target log file, the accurate determination of the abnormal positioning result can be achieved, reducing the situation where the result feedback display error is caused by inaccurate determination of the cause of the abnormal application flash back, thereby improving the user's favorability and satisfaction with the electronic device.

[0038] In a possible implementation of the second aspect, the process of the server analyzing the target log file may specifically include: the server matches the target log file with the log feature information in the log feature library to obtain an abnormality location result. The log feature library includes log feature information corresponding to multiple security hardening programs, and the log feature information corresponding to the security hardening program is the feature information of the corresponding log file when the application that uses the security hardening program for security hardening crashes.

[0039] In the embodiment of the present application, the server can determine the location result of the application crash exception by matching the target log file with the log feature information in the log feature library. In this way, the abnormal location result can be accurately determined, which provides convenient conditions for promptly informing the user of the reason for the application crash exception.

[0040] In a possible implementation of the second aspect, the process in which the server matches the target log file with the log feature information in the log feature library may specifically include: when the target log file includes any feature string in the log feature library, the server may determine that the abnormal location result indicates that the reason for the application flash back abnormality is that the target third-party application is incompatible with the updated system version of the electronic device. Alternatively, when the target log file does not include the feature string in the log feature library, the server may determine that the abnormal location result indicates that the reason for the application flash back abnormality is not that the target third-party application is incompatible with the updated system version of the electronic device.

[0041] In the embodiment of the present application, only when the target log file includes any characteristic string in the log characteristic library can it be determined that the cause of the application flash back abnormality is that the target third-party application is incompatible with the updated system version of the electronic device. In this way, the accuracy of the abnormal location result can be improved, which provides convenient conditions for promptly informing the user of the cause of the application flash back abnormality.

[0042] In a possible implementation of the second aspect, after obtaining the abnormal location result of the application flash back abnormality, the above method further includes: when the abnormal location result indicates that the cause of the application flash back abnormality is that the target third-party application is incompatible with the updated system version of the electronic device, the server obtains the abnormal solution of the application flash back abnormality from the solution plan library according to the target third-party application. The abnormal solution includes abnormal solution progress information and / or abnormal solution time. Afterwards, the server can send the abnormal location result and the abnormal solution to the electronic device.

[0043] In some cases, the exception resolution progress information may be used to indicate that there is a planned version of the target third-party application that can resolve the application crash exception and is compatible with the updated system version. The exception resolution time includes the release time of the planned version.

[0044] In other cases, the exception resolution progress information is also used to indicate that the above-mentioned planned version does not exist, and to prompt the user to provide feedback on the application crash exception through the preset feedback path of the target third-party application.

[0045] In the embodiment of the present application, the server can obtain the abnormal solution of the application flash back abnormality from the solution plan library according to the target third-party application. In this way, the abnormal solution can be accurately determined, which provides convenient conditions for promptly informing the user of the solution of the application flash back abnormality.

[0046] In a third aspect, the present application provides an electronic device, comprising a memory and one or more processors; the memory and the processor are coupled; the memory is used to store computer program code, and the computer program code comprises computer instructions; when the processor executes the computer instructions, the electronic device executes the method as described above.

[0047] In a fourth aspect, the present application provides a server, comprising a memory and one or more processors; the memory and the processor are coupled; the memory is used to store computer program code, and the computer program code comprises computer instructions; when the processor executes the computer instructions, the server executes the method as described above.

[0048] In a fifth aspect, the present application provides a computer-readable storage medium, comprising computer instructions, which, when executed on an electronic device, enable the electronic device to execute the method described above.

[0049] In a sixth aspect, the present application provides a computer program product, which, when executed on an electronic device, enables the electronic device to execute the method described above.

[0050] In the seventh aspect, a chip is provided, comprising: an input interface, an output interface, a processor and a memory, wherein the input interface, the output interface, the processor and the memory are connected via an internal connection path, and the processor is used to execute the code in the memory. When the code is executed, the processor is used to execute the method as described above.

[0051] Among them, the beneficial effects that can be achieved by the electronic device described in the third aspect, the server described in the fourth aspect, the computer-readable storage medium described in the fifth aspect, the computer program product described in the sixth aspect, and the chip described in the seventh aspect provided above can refer to the beneficial effects in the first aspect, the second aspect and any possible design methods thereof, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0052] Figure 1 A schematic diagram of an interface for running a third-party application provided in an embodiment of the present application;

[0053] Figure 2 A schematic diagram of a positioning result feedback process for an application crash problem provided in an embodiment of the present application;

[0054] Figure 3 A schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present application;

[0055] Figure 4 A schematic diagram of the structure of an exception handling system provided in an embodiment of the present application;

[0056] Figure 5 A schematic diagram of an interface for triggering a mobile phone to display a detection notification bar provided in an embodiment of the present application;

[0057] Figure 6 A schematic diagram of an interface for providing feedback on an application crash problem provided in an embodiment of the present application;

[0058] Figure 7 A flowchart of a first exception handling method provided in an embodiment of the present application;

[0059] Figure 8 A schematic diagram of an interface for displaying feedback information of a problem location result provided in an embodiment of the present application;

[0060] Fig. 9 A flowchart of a second exception handling method provided in an embodiment of the present application;

[0061] Fig.10 A flowchart of a third exception handling method provided in an embodiment of the present application. DETAILED DESCRIPTION

[0062] The technical solutions in the embodiments of the present application are described below in conjunction with the drawings in the embodiments of the present application. Among them, in the description of the embodiments of the present application, the terms used in the following embodiments are only for the purpose of describing specific embodiments, and are not intended to be used as limitations on the present application. As used in the specification and the appended claims of the present application, the singular expressions "a", "said", "above", "the" and "this" are intended to also include expressions such as "one or more", unless there is a clear contrary indication in the context. It should also be understood that in the following embodiments of the present application, "at least one", "one or more" refer to one or more (including two). The term "and / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist; for example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship.

[0063] References to "one embodiment" or "some embodiments" etc. described in this specification mean that one or more embodiments of the present application include specific features, structures or characteristics described in conjunction with the embodiment. Thus, the statements "in one embodiment", "in some embodiments", "in some other embodiments", "in some other embodiments", etc. that appear in different places in this specification do not necessarily refer to the same embodiment, but mean "one or more but not all embodiments", unless otherwise specifically emphasized in other ways. The terms "including", "comprising", "having" and their variations all mean "including but not limited to", unless otherwise specifically emphasized in other ways. The term "connection" includes direct connection and indirect connection, unless otherwise specified. "First" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated.

[0064] In the embodiments of the present application, the words "exemplarily" or "for example" are used to indicate examples, illustrations or explanations. Any embodiment or design described as "exemplarily" or "for example" in the embodiments of the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplarily" or "for example" is intended to present related concepts in a specific way.

[0065] In some embodiments, the electronic device may be installed with multiple applications for users to use. The application may be a built-in application (or system application), or an external application (or third-party application), etc., without specific limitation. A built-in application is an application that comes with the electronic device when it leaves the factory. For example, the built-in application may be a my device application, a settings application, a camera application, etc. An external application is an application provided by a third-party manufacturer, which is an application provided by a non-electronic device manufacturer. The external application may be an application downloaded from the application market of the electronic device, or an application downloaded from the website or platform of a third-party developer, without specific limitation. For example, the external application may be a video application, a social application, a shopping application, etc.

[0066] For example, Figure 1 As shown in (a) of FIG. 1 , the electronic device is taken as a mobile phone as an example, and the mobile phone is displaying the main interface. The main interface includes icons of multiple application programs (APPs). The multiple application programs may include built-in applications and external applications. For example, the built-in application may be a clock application, a calendar application, a gallery application, etc. The external application may be a first video application, a second shopping application, a third social application, etc.

[0067] In one implementation, in order to ensure the security of external applications in electronic devices and reduce the occurrence of attacks on external applications, third-party manufacturers of external applications in electronic devices will perform security reinforcement on their own applications. In other words, all external applications in electronic devices are security-reinforced applications. In this way, the security of external applications can be improved, and the external applications in electronic devices can be reduced from being attacked by reverse engineering, tampering, and injection of malicious code. The operation stability and security of external applications are improved, thereby protecting the user's security and privacy and the interests of the company and enhancing the user's trust.

[0068] In some embodiments, third-party manufacturers can perform security reinforcement on external applications through security reinforcement methods, which may include code obfuscation methods, resource encryption methods, signature verification methods, debugging prevention methods, dynamic injection prevention methods, data encryption methods, repackaging prevention methods, code security verification methods, etc.

[0069] It should be noted that the external application in the above electronic device implements the security reinforcement service through the security reinforcement program, so that the external application has the security reinforcement service. Specifically, the third-party manufacturer can send the security reinforcement program to the external application to be reinforced through the application programming interface (API). Among them, the external application to be reinforced is an application developed by a third-party manufacturer and needs to be security reinforced.

[0070] However, when an electronic device is updating its system version, the system behavior, API, and functions will also change accordingly with the system version, and changes in system behavior, API, and functions may affect the way applications in the electronic device run. In other words, if the system version of the electronic device is updated, the API used in the security hardening program may be modified or abandoned, which will cause the security hardening program to be unable to be sent to the external application to be hardened, that is, the external application to be hardened cannot run the security hardening program, which may cause the external application to be hardened to run abnormally, and further cause the external application to be hardened to have a compatibility crash. Among them, the compatibility crash problem refers to the application crash caused by the application version of the external application not being compatible (i.e. adapted) with the system version of the electronic device.

[0071] Therefore, in order for external applications in electronic devices to run normally, when the electronic devices update the system version, they need to remind third-party manufacturers of external applications to understand and adapt to the updated system version, that is, to understand and adapt to changes in system behavior, API and functions, so that the application manufacturers can promptly promote reinforcement optimization and adaptation, so that the external applications in the electronic devices can receive the security reinforcement program that is adapted to the system version, that is, the external application can re-run the security reinforcement program, thereby solving the compatibility crash problem of the external application.

[0072] It is understood that, under normal circumstances, in response to a user's opening operation for any external application, the electronic device can start the external application, that is, display the initial interface of the external application. Figure 1 , displayed on the phone Figure 1 In the case of the main interface shown in (a), if the icon of the first video application in the main interface is clicked by the user, the mobile phone can display Figure 1 The initial interface shown in (b) is used to display the video content recommended by the first video application, that is, to display the video content released by the account "Xiaohong".

[0073] However, if the third-party manufacturer fails to adapt to the changed API in time, the external application of the third-party manufacturer cannot receive the security reinforcement program through the changed API, and thus cannot implement the security reinforcement of the external application. This will cause the external application to crash during startup, making it impossible for the electronic device to open the external application normally, resulting in a poor user experience. For example, Figure 1 As shown, Figure 1 The first video application in the main interface shown in (a) is an application that has not been adapted to the system version, that is, the first video application has not received the security reinforcement program configured by the third-party manufacturer. For example, when it is detected that the icon of the first video application is clicked by the user, if the mobile phone displays Figure 1 The screen shown in (c) flashes and then returns to display Figure 1 The main interface shown in (a) or the phone still displays Figure 1 The main interface shown in (a) indicates that the first video application has experienced a flashback. It can be understood that the splash screen interface can also be a pure black interface, a pure white interface, or a main interface, etc. As long as the display interface that cannot represent that the electronic device has entered the first video application can be used as a splash screen interface, there is no specific limitation.

[0074] In some cases, when users encounter the above-mentioned application crash problem, they will feedback the application crash problem to the electronic device, for example, to the "My Device Application", so that the tester can capture the corresponding log file according to the application crash problem and obtain the problem location result by analyzing the log file. Among them, the "My Device Application" is a built-in application of the electronic device, which is used to intelligently detect abnormal conditions of the electronic device (such as application crash) to realize the fault location function.

[0075] In one implementation, Figure 2 As shown, the process of locating the cause of the application flashback problem by the captured log file by the electronic device may specifically include: the electronic device obtains the problem filling information and multiple log files when receiving the user's problem filling operation. Among them, the problem filling information may include the filled problem and the time when the problem occurred, and the multiple log files are log files captured by the electronic device. Afterwards, the electronic device can determine whether the filled problem in the problem filling information belongs to the application flashback problem. If the filled problem in the problem filling information belongs to the application flashback problem, the electronic device can record the filled problem in the problem filling information and multiple log files. Afterwards, the tester can view the filled problem in the problem filling information and multiple log files. Afterwards, the tester can analyze the multiple log files to obtain the problem location result of the filled problem. Afterwards, the tester can synchronize the problem location result of the filled problem to the user according to the preset communication method. Among them, the preset communication method can be calling the user's phone, sending a text message to the user, etc., as long as the user can be notified, it is not specifically limited.

[0076] When the problem location result indicates that the cause of the filled-in problem is that the target third-party application is incompatible with the updated system version, the tester can synchronize the problem location result of the filled-in problem with the target manufacturer. Among them, the target manufacturer is the manufacturer of the third-party application to which the filled-in problem belongs. Afterwards, upon receiving the problem location result of the filled-in problem synchronized by the tester, the target manufacturer determines the problem solution for the filled-in problem, that is, determines the plan that can solve the application crash problem and / or the time that can solve the application crash problem. Afterwards, the target manufacturer can send the problem solution for the filled-in problem to the tester. Afterwards, upon receiving the problem solution for the filled-in problem sent by the target manufacturer, the tester synchronizes the problem solution for the filled-in problem to the user according to the preset communication method.

[0077] It is understandable that after receiving the application crash problem (that is, the problem has been filled in) reported by the user, the electronic device only records the application crash problem to facilitate subsequent testers to analyze the problem, that is, the cause of the application crash problem is analyzed manually. In this way, testers will need to spend a lot of time and energy on problem analysis, reducing the efficiency of analyzing the application crash problem. In addition, after obtaining the problem location results, the tester will inform the user of the cause of the application crash problem by calling the user's phone number or other contact methods. In this way, the user may not know the cause of the application crash problem in time, and it is impossible to meet the needs of quickly closing the loop of user-generated problems, reducing the feedback efficiency of the problem location results. Furthermore, it may cause users to mistakenly believe that the application crash problem is a problem with the electronic device itself, which ultimately affects the user's favorability and satisfaction with the electronic device.

[0078] Therefore, in order to improve the efficiency of analyzing abnormal problems and promptly inform users of the causes of abnormal problems, an embodiment of the present application provides an exception handling method. In this method, in response to a user's feedback operation on an application flashback exception, an electronic device obtains a target log file. Among them, the target log file is a log file generated by a target third-party application, and the target third-party application is a third-party application in which an application flashback exception occurs in the electronic device. Afterwards, the electronic device can send the target log file to the server. Afterwards, the electronic device can receive the abnormal location result sent by the server. Among them, the abnormal location result is obtained based on the analysis of the target log file. Afterwards, the electronic device performs a result feedback operation based on the abnormal location result. Among them, the result feedback operation includes feedback on the cause of the application flashback exception.

[0079] The abnormal location result is used to indicate whether the cause of the application crash is that the target third-party application is incompatible with the updated system version. When the target third-party application is incompatible with the updated system version, the target third-party application cannot run the security reinforcement program normally. The application crash is an abnormal problem that occurs when the target third-party application is cold started.

[0080] In the embodiment of the present application, when the user feedback about the application flashback exception is detected, the electronic device can send the acquired target log file to the server so that the server can locate the cause of the application flashback exception. And, when the electronic device receives the abnormal location result sent by the server, it performs the result feedback operation according to the abnormal location result. In this way, not only can the automatic analysis of the application flashback exception be realized, but also the tester does not need to manually analyze the cause of the problem, while reducing the manpower cost, the analysis efficiency of the application flashback exception is improved; and, by performing the result feedback operation, the electronic device can timely feedback the cause of the application flashback exception to the user, so that the user can quickly know the cause of the application flashback exception, minimize the closed loop time of the application flashback exception, and improve the feedback efficiency of the abnormal location result. In addition, it can reduce the occurrence of the situation where the user mistakenly believes that the application flashback exception is a problem of the electronic device itself, and improve the user's favorability and satisfaction with the electronic device. In addition, since the abnormal location result is obtained by analyzing the target log file, the accurate determination of the abnormal location result can be realized, and the situation where the result feedback display error is caused by inaccurate determination of the cause of the application flashback exception is reduced, thereby improving the user's favorability and satisfaction with the electronic device.

[0081] In some examples, the electronic device in the embodiments of the present application may be a mobile phone, a tablet computer, a desktop, a laptop, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, as well as a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, and other devices installed with third-party applications. The embodiments of the present application do not impose any special restrictions on the specific form of the electronic device.

[0082] For example, Figure 3 FIG. 2 shows a schematic diagram of the hardware structure of the electronic device 200. Figure 3As shown, the electronic device 200 may include a processor 210, an external memory interface 220, an internal memory 221, a universal serial bus (USB) interface 230, a charging management module 211, a power management module 212, a battery 213, an antenna 1, an antenna 2, a mobile communication module 240, a wireless communication module 250, an audio module 270, a sensor module 280, a button 290, a motor 291, an indicator 292, cameras 1-N 293, a display screen 294, and a subscriber identification module (SIM) card interface 1-N 295, etc.

[0083] It is to be understood that the structure illustrated in the embodiment of the present application does not constitute a specific limitation on the electronic device 200. In other embodiments of the present application, the electronic device 200 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0084] The processor 210 may include one or more processing units, for example, the processor 210 may include an application processor (AP), a modem processor, a graphics processor (GPU), an image signal processor (ISP), a controller, a memory, a video codec, a digital signal processor (DSP), a baseband processor, and / or a neural-network processing unit (NPU), etc. Different processing units may be independent devices or integrated into one or more processors.

[0085] In some embodiments, the electronic device 200 can implement the exception handling method provided in this application through the processor 210.

[0086] The processor 210 may also be provided with a memory for storing instructions and data to reduce the number of accesses to the internal memory 221 and improve the program execution speed. In some embodiments, the memory in the processor 210 is a cache memory. The memory may store instructions or data that the processor 210 has just used or cyclically used. If the processor 210 needs to use the instruction or data again, it may be directly called from the memory. Repeated access is avoided, the waiting time of the processor 210 is reduced, and the efficiency of the system is improved.

[0087] The wireless communication function of the electronic device 200 can be implemented through the antenna 1, the antenna 2, the mobile communication module 240, the wireless communication module 250, the modem processor and the baseband processor.

[0088] The electronic device 200 implements the display function through a GPU, a display screen 294, and an application processor. The GPU is a microprocessor for image processing, which connects the display screen 294 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. The processor 210 may include one or more GPUs, which execute program instructions to generate or change display information.

[0089] The display screen (or screen) 294 is used to display images, videos, etc. In some embodiments, the electronic device 200 may include 1 or N display screens 294, where N is a positive integer greater than 1. The display screen 294 may be a touch screen.

[0090] The electronic device 200 can realize the shooting function through ISP, camera 293, video codec, GPU, display screen 294 and application processor.

[0091] The digital signal processor is used to process digital signals, and can process not only digital image signals but also other digital signals. For example, when the electronic device 200 is selecting a frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy.

[0092] The external memory interface 220 can be used to connect an external memory card, such as a Micro SD card, to expand the storage capacity of the electronic device 200. The external memory card communicates with the processor 210 through the external memory interface 220 to implement a data storage function, such as storing music, video and other files in the external memory card.

[0093] The internal memory 221 can be used to store computer executable program codes, which include instructions. The processor 210 executes various functional applications and data processing of the electronic device 200 by running the instructions stored in the internal memory 221. The internal memory 221 may include a program storage area and a data storage area. Among them, the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc. The data storage area may store data created during the use of the electronic device 200 (such as audio data, a phone book, etc.), etc.

[0094] The data storage area may also store log files generated by the application or system during the operation of the electronic device 200. The log files may be included in the first folder (i.e., android_logs) or in the second folder (i.e., dropbox folder). The android_logs may include various log files generated during the operation of the system. The dropbox folder may include log files generated when third-party applications and built-in applications crash, application not respond (ANR), and other problems occur during use.

[0095] In addition, the internal memory 221 may include a high-speed random access memory and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, a universal flash storage (UFS), etc.

[0096] The electronic device 200 can implement audio functions through the audio module 270 and the application processor, such as music playing and recording, etc. The audio module 270 may include a speaker, a receiver, a microphone, and an earphone interface, etc.

[0097] The buttons 290 include a power button, a volume button, etc. The indicator 292 may be an indicator light.

[0098] Figure 4 Schematic diagram of the structure of the exception handling system of the embodiment of the present application. Figure 4 As shown, the exception handling system may include an electronic device 200 and a server 300. A communication connection is established between the server 300 and the electronic device 200. The server 300 may be a single server, a server cluster, a distributed server, a centralized server, a cloud server, or a computer, etc., which is not specifically limited.

[0099] The electronic device 200 may include third-party applications and my device applications. Among them, the third-party application is an application provided by a third-party manufacturer, that is, an application provided by a non-electronic device manufacturer or official. For example, the third-party application may be a video application, a social application, a shopping application, etc. My device application is a built-in application of the electronic device, which is equivalent to the application that comes with the electronic device when it leaves the factory.

[0100] In some embodiments, my device application can be used to intelligently detect abnormal conditions of electronic devices (such as application crashes) to implement fault location functions. Specifically, in response to the user's question filling operation, my device application can obtain the filled-in question and capture multiple log files within a preset period before the generation time of the filled-in question. Among them, the filled-in question can be an application crash problem (or called an application crash exception). Afterwards, my device application can compress the multiple log files to obtain a log compression file. Among them, the log compression file can include multiple compressed log files.

[0101] In other embodiments, my device application can also be used to identify whether the above-mentioned filled-in question belongs to the application crash problem. Specifically, my device application can determine whether the filled-in question belongs to the application crash problem. If the filled-in question belongs to the application crash problem, for each log file, my device application can parse the log file to obtain a log parsing result. Among them, the log parsing result is used to characterize whether the log file belongs to a log file of a third-party application. Afterwards, when the log parsing result characterizes that the log file belongs to a log file of a third-party application, my device application can determine whether the third-party application is the third-party application to which the filled-in question belongs. If the third-party application is the third-party application to which the filled-in question belongs, my device application can use the log file as the target log file and send the target log file to the server 300.

[0102] The above-mentioned server 300 may include a problem analysis module, etc. Among them, the problem analysis module is used to analyze the cause of the above-mentioned filled-in problem. In some embodiments, when the problem analysis module receives the target log file sent by the problem identification module, it can analyze the target log file to obtain a problem location result (or abnormal location result). Among them, the problem location result is used to indicate whether the cause of the filled-in problem is that the target third-party application is incompatible with the updated system version. The target third-party application is a third-party application in the electronic device where the filled-in problem occurs. Afterwards, the problem analysis module can send the problem location result to the my device application in the electronic device 200, so that the user can know the cause of the filled-in problem in time, minimize the closed-loop time of the filled-in problem, and improve the user's experience.

[0103] Among them, the above-mentioned problem analysis module stores a log feature library. The log feature library may include multiple log feature character strings. The log feature character string can indicate that the third-party application has been security-reinforced. In some embodiments, the problem analysis module may match the above-mentioned target log file with the log feature character string (or log feature) in the log feature library to determine whether the target log file includes any log feature character string in the log feature library. If the target log file includes any log feature character string in the log feature library, it means that the third-party application of the target log file has been security-reinforced, that is, the third-party application may be incompatible with the updated system version. Therefore, the problem location result obtained by the problem analysis module can indicate that the reason for the filled-in problem is that the target third-party application is incompatible with the updated system version.

[0104] Optionally, the server 300 may further include a problem solving plan module. The problem solving plan module stores a solution plan library for the application crash problem, and the solution plan library includes a plurality of third-party application solutions and solution progress for the application crash problem. In other words, the problem solving plan module is used to obtain a target solution plan and target solution progress for a target application from the solution plan library.

[0105] In some embodiments, when the above-mentioned problem location result indicates that the reason for the filled-in problem attribute is that the target third-party application is incompatible with the updated system version, the problem analysis module can send the application package name and / or application name of the target application to the problem solution plan module. Afterwards, when the problem solution plan module receives the application package name and / or application name of the target application sent by the problem analysis module, it can extract the corresponding solution plan and solution progress from the solution plan library based on the application package name and / or application name of the target application. Afterwards, the problem solution plan module can send the extracted solution plan and solution progress to my device application, so that the user can understand the solution plan of the problem in a timely manner, and it is convenient for the user to update the application version in time, thereby improving the user's usage experience.

[0106] In one implementation, Figure 4As shown, in response to the user's question filling operation, the electronic device (or the replacement description of my device application) can obtain the filled-in question and capture multiple log files within a preset period before the generation time of the filled-in question. Among them, the filled-in question is the flashback problem of the application (or target third-party application) to which the filled-in question belongs, and the application to which the filled-in question belongs is a third-party application that has been security-reinforced. Afterwards, for each log file, when the log file belongs to a log file of a third-party application, and the third-party application is the application to which the filled-in question belongs, the electronic device can use the log file as the target log file, and execute step a to send the target log file to the problem analysis module in the server. Afterwards, the problem analysis module can analyze the target log file to obtain the problem location result. Among them, the problem location result is used to indicate whether the cause of the filled-in question is that the target third-party application is incompatible with the updated system version. Afterwards, the problem analysis module can execute step b to send the problem location result to the electronic device, so that the user can know the cause of the filled-in question in time, minimize the closed-loop time of the filled-in question, and improve the user's experience.

[0107] Furthermore, when the above problem location result indicates that the reason for the filled problem is that the target third-party application is incompatible with the updated system version, the problem analysis module can also execute step c to send the application package name and / or application name of the target application to the problem solution plan module. Afterwards, the problem solution plan module can execute step d to extract the corresponding solution plan and solution progress from the solution plan library based on the application package name and / or application name of the target application. Afterwards, the problem solution plan module can send the extracted solution plan and solution progress to the electronic device, so that the user can understand the solution plan of the problem in a timely manner, and it is convenient for the user to update the application version in a timely manner, thereby improving the user's experience.

[0108] Based on the electronic device described in the above exemplary embodiment, an embodiment of the present application provides an exception handling method. In this method, the electronic device can determine the cause of the abnormal problem based on the abnormal problem (or filled-in problem) reported by the user, and the target log file within a preset period before the occurrence of the abnormal problem, and notify the user through the electronic device, so that the user can know the cause of the filled-in problem in a timely manner, which minimizes the closed-loop time of the filled-in problem and improves the user's experience. Exemplarily, the abnormal problem can be an application flashback exception.

[0109] The abnormal problems reported by the user can be manually filled in by the user or input by voice, and there is no specific limitation. The following example uses a mobile phone as an electronic device, and the abnormal problems reported by the user are manually filled in by the user, to introduce how the mobile phone obtains abnormal problems reported by the user from the perspective of the display interface.

[0110] Specifically, in response to the user's opening operation of any third-party application in the main interface, if the phone still displays the main interface or displays the flash back interface, it means that the opened third-party application has a flash back problem. In other words, the user did not successfully trigger the opening of the third-party application in the phone. Afterwards, the user can report the flash back problem in the My Device application to facilitate the subsequent cause of the flash back problem.

[0111] For example, Figure 5 As shown, the mobile phone displays Figure 5 The main interface shown in (a) in the figure. The main interface includes icons of multiple third-party applications and icons of my device applications. The third-party applications are icons of the first video application, the second shopping application, and the third social application. Afterwards, if it is detected that the icon of the first video application is opened by the user, if the mobile phone still displays the main interface or displays a flash back interface (such as Figure 1 In the (c) interface), it can be determined that an abnormal problem has occurred in the first video application.

[0112] Afterwards, in response to the user clicking the icon of the My Device application in the main interface, the mobile phone may display Figure 5 The device service interface shown in (b) in the figure. The device service interface includes a "device detection" control, a "charging standard" control, a "book an appointment to the store" control, and a "more" control. Afterwards, in response to the user clicking the "device detection" control in the device service interface, the mobile phone can display a smart detection interface. The smart detection interface can include more icons, multiple detection directions, and a "detect now" control. The detection direction can be system performance, application message reception delay, communication and network, etc.

[0113] Afterwards, if more icons in the above smart detection interface are clicked by the user, the mobile phone can overlay and display multiple function controls on the basis of the smart detection interface, that is, display Figure 5 The smart detection interface shown in (c) in the figure. The function controls may be the "diagnosis analysis" control, the "remote service" control, the "problem feedback" control, and the "about" control. Afterwards, if the "problem feedback" control in the smart detection interface is clicked by the user, the mobile phone may display Figure 5The problem feedback interface shown in (d) in the figure. The problem feedback interface includes a switch control 2A for opening the log, a problem category, and a "next item" control. The switch control for opening the log is used to indicate whether the mobile phone can capture the log file to analyze the log file. The problem category may include reliability, performance, power consumption, communication, and application.

[0114] Afterwards, if the switch control 2A for opening the log in the above-mentioned problem feedback interface is turned on by the user, the mobile phone can display the detection notification bar 410 in the pull-down notification bar, that is, display Figure 5 The drop-down notification interface shown in (e). Among them, the detection notification bar 410 may include detection notification information, an "exit" control, and a "feedback problem" control 2B. The "feedback problem" control 2B is used to trigger the mobile phone to capture log files. The detection notification information is used to remind users when to feedback problems, so as to better analyze the causes of abnormal problems later. Exemplarily, the detection notification information may be "The diagnostic mode is turned on. It is recommended that you provide feedback within ten seconds after the problem recurs, and the log validity will be higher. The diagnostic mode will automatically exit at 02:00 on September 27, 2024."

[0115] In some embodiments, when a detection notification bar including a "feedback problem" control is displayed in the drop-down notification bar of the mobile phone, if an abnormal problem occurs in the external application clicked by the user, that is, the mobile phone does not display the display interface of the external application clicked by the user, the user can trigger the "feedback problem" control in the detection notification bar so that the mobile phone can automatically capture relevant log files for analysis, thereby locating the cause of the abnormal problem.

[0116] For example, Figure 6 As shown, the phone is displaying Figure 6 The main interface shown in (a) of FIG. 1 includes an icon of a first video application. Afterwards, in response to a user clicking on the icon of the first video application, if the mobile phone still displays the main interface or displays a flash back interface (such as Figure 1 (c) interface in the figure) indicates that an abnormal problem occurred during the startup of the first video application. Therefore, in response to the user's sliding operation on the top area of ​​the mobile phone, the mobile phone can display Figure 6The drop-down notification interface shown in (b). The drop-down notification interface may include a detection notification bar (or called a drop-down notification bar) 410, and the detection notification bar 410 may include detection notification information, an "exit" control, and a "feedback problem" control 2B. Afterwards, if the "feedback problem" control 2B of the detection notification bar 410 in the drop-down notification interface is clicked by the user, the mobile phone may display a problem description interface. The problem description interface may include a fill-in box 510 for problem details, and the fill-in box 510 for problem details is used to characterize the application crash problem reported by the user, that is, to display the abnormal problem filled in by the user.

[0117] Afterwards, when it is detected that the user has completed the filling operation of the question details filling box 510 in the above question description interface, the mobile phone can superimpose the feedback receiving window content in the form of a pop-up window on the basis of the question description interface, that is, display Figure 6 The problem description interface shown in (c) in the figure. The window content may include a text prompt message (i.e., thank you for your feedback. We will analyze it as soon as possible and solve the related problems in subsequent versions. Please continue to pay attention to the update information of subsequent versions.) and an "Got it" control. Afterwards, when it is detected that the "Got it" control is clicked by the user, the mobile phone can obtain the content filled in by the user in the filling box 510 of the problem details, that is, obtain the abnormal problem filled in by the user.

[0118] In some cases, when a user clicks on the "Got it" control, the phone may display Figure 6 At the same time as the result feedback interface shown in (d) in the figure, the abnormal problem filled in by the user in the filling box 510 of the above question details is obtained, that is, the abnormal problem filled in by the user in the filling box 510 of the above question details is obtained. Figure 6 The description information about the application crash entered in the problem description interface shown in (c) in the figure. In addition, the mobile phone can obtain all log files within a preset period before the occurrence time of the abnormal problem according to the occurrence time of the abnormal problem so that the mobile phone can locate the cause of the abnormal problem according to all the log files.

[0119] The following will describe the exception handling method provided by the embodiment of the present application based on the above problem feedback scenario. Figure 7 As shown, the exception handling method may include S601 to S606.

[0120] S601, the mobile phone receives the user's question filling operation.

[0121] It should be noted that when a new version of the system is installed on the mobile phone, if the third-party application in the mobile phone is not compatible with the new version of the system, the new version of the system may modify or delete the relevant API in the original security reinforcement program, causing the third-party application to be unable to continue to run the original security reinforcement program, thereby causing the third-party application to run abnormally (such as the application flashing back), ultimately affecting the user's experience. Therefore, after the user perceives that the third-party application is running abnormally, the abnormal problem (such as the application flashing back problem) will be fed back to the my device application installed in the mobile phone. That is, my device application can receive the user's question filling operation. Among them, the question filling operation is used to trigger the mobile phone to obtain the relevant information filled in by the user, that is, to trigger the mobile phone to obtain the question filling information. Exemplarily, the question filling operation can be a feedback operation for the application flashing back abnormality. It can be understood that my device application is an application that comes with the mobile phone, that is, the my device application is a built-in application.

[0122] In one example, the above question filling operation can be a trigger operation for a target control in the question description interface of a mobile phone. That is to say, the question filling information obtained by the mobile phone can be obtained based on the information manually filled in by the user. Among them, the trigger operation refers to the operation performed by the user's finger touching the mobile phone display. The trigger operation can be a single-click operation for the filling control, or a double-click operation for the filling control, etc., without specific limitation. The target control in the question description interface is used to enable the mobile phone to extract the relevant information filled in by the user to generate question filling information. For example, Figure 6 The (c) interface in the figure is a problem description interface. The problem description interface includes an "I know" control, which is equivalent to a target control. In other words, if the "I know" control is clicked by the user, it means that the user has completed the question that needs feedback, and the mobile phone can obtain the question filling information.

[0123] In another example, the question filling operation can also be a voice receiving operation when the mobile phone displays the question description interface. That is, the question filling information obtained by the mobile phone can also be obtained based on the information input by the user's voice. Specifically, when the mobile phone displays the question description interface, if the user's voice command is received, the mobile phone can display the relevant information input by the user at the corresponding position in the question description interface according to the user's voice command, that is, display Figure 6 The problem description interface shown in (c).

[0124] S602, the mobile phone obtains question filling information, wherein the question filling information includes the filled question and the time when the question occurred.

[0125] Specifically, after detecting the user's question filling operation, the mobile phone can obtain question filling information. The question filling information may include the filled question and the time when the filled question occurred. In some embodiments, the question filling information may also include a third-party application in the electronic device where the filled question occurred.

[0126] In some embodiments, the mobile phone can obtain the question filling information from the above question description interface. The question filling information may include the filled question and the time when the filled question occurred. For example, Figure 6 As shown in the interface (c) in FIG. 1 , the content displayed in the problem detail filling box 510 in the problem description interface (i.e., application crashes) is the filled problem. The content displayed in the time filling area 5A in the problem description interface (i.e., September 26, 20:00) is the time when the filled problem occurred.

[0127] It should be noted that the time of the problem can be manually filled in by the user according to the time when the problem occurred, or it can be automatically generated by the mobile phone according to the time corresponding to the time when the user triggers the log capture control. There is no specific limitation. Among them, the log capture control is used to trigger the mobile phone to capture multiple log files within a preset time period. Exemplarily, the log capture control can be the above Figure 6 The “Feedback Issue” control 2B in the drop-down notification interface shown in (b).

[0128] S603, the mobile phone obtains a plurality of log files within a preset period of time before the problem occurs.

[0129] Specifically, after obtaining the time when the problem of the filled-in question occurs, the mobile phone can capture multiple log files within a preset time period before and before the time when the problem occurs. The preset time period can be pre-set according to actual conditions. For example, the preset time period can be 10 minutes, 30 minutes, etc., which is not specifically limited.

[0130] Among them, the above-mentioned multiple log files can be log files included in the first folder (i.e., the dropbox folder), or can be log files included in the second folder (i.e., android_logs). The android_logs can include various log files generated during the operation of the system. The dropbox folder can include log files generated when problems such as flashbacks and ANR occur during the operation of the application. The application can be a built-in application (i.e., a system application) or a third-party application, etc., without specific limitation.

[0131] In one implementation, after capturing the multiple log files, the mobile phone can compress the multiple log files to obtain multiple compressed log files, that is, to obtain a log compression file. The log compression file is a plurality of compressed log files. In this way, the transmission time and bandwidth consumption of the log files can be reduced, thereby improving the transmission efficiency of the log files, and providing convenient conditions for the subsequent server to quickly receive the log files.

[0132] It should be noted that the above process of the mobile phone obtaining the question filling information and the process of the mobile phone obtaining multiple log files can be performed simultaneously or in a sequential order, and there is no specific limitation. That is, in response to the user's question filling operation, the mobile phone can obtain the question filling information and multiple log files at the same time, or it can obtain multiple log files first and then obtain the question filling information.

[0133] S604, the mobile phone determines whether the filled-in question in the question filling information is an application crash problem.

[0134] The above-mentioned application flash back problem (or application flash back anomaly) refers to the abnormal problem caused by the third-party application during the cold start process. The cold start means that the third-party application is not running in the system background of the mobile phone, and the third-party application is triggered to start only when the start operation input by the user is received.

[0135] In some embodiments, after obtaining the above-mentioned multiple log files, the mobile phone can determine whether the filled-in problem in the problem filling information belongs to the application crash problem. If the filled-in problem belongs to the application crash problem, it means that the above-mentioned problem filling operation is a feedback operation for the application crash problem, and the filled-in problem is more likely to be a problem of a third-party application, and does not belong to the problem of the mobile phone itself. Therefore, the mobile phone can execute S605 to further analyze the cause of the filled-in problem. If the filled-in problem does not belong to the application crash problem, it means that the filled-in problem cannot be clearly a problem of a third-party application. Therefore, the mobile phone can record the filled-in problems and multiple log files to facilitate subsequent testers to analyze the problem, so as to determine the cause of the filled-in problem, so that users can know the cause of the filled-in problem and improve the user experience.

[0136] S605, when the filled-in problem in the problem filling information is an application crash problem, the mobile phone analyzes multiple log files to obtain a problem location result of the filled-in problem.

[0137] Specifically, after determining that the filled-in problem in the above problem filling information belongs to the application crash problem, the mobile phone can analyze multiple log files to obtain the problem location result (or abnormal location result) of the filled-in problem. Among them, the problem location result is used to indicate whether the filled-in problem belongs to a third-party application problem, that is, whether the cause of the filled-in problem is that the target third-party application is incompatible with the updated system version, and the target third-party application is the third-party application in the mobile phone where the application crashes abnormally. In this way, not only can the automated analysis of the filled-in problem be realized, and there is no need for testers to manually analyze the cause of the problem, while reducing labor costs, the analysis efficiency of the filled-in problem is improved, so that users can quickly know the cause of the filled-in problem, minimize the closed-loop time of the filled-in problem, and improve the user experience. It can also reduce the situation where users mistakenly believe that the filled-in problem is a problem with the electronic device itself, thereby improving users' favorability and satisfaction with the electronic device.

[0138] It is understandable that when the target third-party application is incompatible with the updated system version, the target third-party application cannot run the security hardening program normally, that is, the target third-party application cannot have the security hardening service, which in turn causes the target third-party application to experience an application crash.

[0139] In some embodiments, it is considered that the above-mentioned multiple log files may include not only log files in the dropbox folder, but also log files in android_logs. In addition, the number of log files in android_logs is relatively large. If the mobile phone parses each log file in android_logs, it will occupy too many computing resources of the mobile phone. Therefore, in order to reduce unnecessary waste of resources, the mobile phone can only analyze the log files included in the first folder of the multiple log files. In this way, not only the utilization rate of computing resources can be improved, but also the cause of the filled-in problem can be quickly located, and the analysis efficiency of the filled-in problem can be improved.

[0140] It can be understood that log files close to the time when the problem occurred can reflect more accurate information, that is, the closer the log files are to the time when the problem occurred, the more accurately they can reflect whether the target third-party application is compatible with the updated system version. Therefore, in order to improve the accuracy of problem location, the mobile phone can analyze the log files in order from back to front according to the generation time of the above multiple log files, starting from the log file closest to the time when the problem occurred, to determine whether the cause of the filled-in problem is that the target third-party application is incompatible with the updated system version. In this way, the problem location result can be determined quickly and accurately, and the closed-loop time of the filled-in problem can be reduced as much as possible, so that users can quickly know the cause of the filled-in problem, thereby improving the user experience.

[0141] Specifically, when it is determined based on the above log file that the cause of the filled-in problem is the incompatibility of the target third-party application with the updated system version, the mobile phone can directly execute S606, that is, there is no need to continue analyzing the remaining log files. When it is not determined based on the log file that the cause of the filled-in problem is the incompatibility of the target third-party application with the updated system version, that is, when it can only be determined based on the log file that the cause of the filled-in problem is not the incompatibility of the target third-party application with the updated system version, the mobile phone needs to continue analyzing the next log file until the problem location result obtained indicates that the cause of the filled-in problem is the incompatibility of the target third-party application with the updated system version, or, the above multiple log files are analyzed and the problem location result is obtained.

[0142] S606, the mobile phone performs a result feedback operation based on the question location result of the filled-in question.

[0143] Specifically, after obtaining the problem location result of the filled-in question, the mobile phone can perform a result feedback operation according to the problem location result of the filled-in question. The result feedback operation may include feeding back the cause of the filled-in question.

[0144] In some embodiments, the mobile phone can display the first feedback information about the above-mentioned problem location result based on the result feedback interface. Among them, the first feedback information is used to indicate the cause of the above-mentioned filled-in problem. In this way, the cause of the filled-in problem can be intuitively displayed, so that the user can quickly know the cause of the filled-in problem, which minimizes the closed-loop time of the filled-in problem and improves the user's experience. It can also reduce the situation where the user mistakenly believes that the filled-in problem is a problem with the electronic device itself, thereby improving the user's favorability and satisfaction with the electronic device.

[0145] For example, in the display Figure 6 In the case of the problem description interface shown in (c), if the user clicks the "Got it" control in the problem description interface, the mobile phone can display Figure 8 The result feedback interface shown in (a) in the figure. The feedback record interface may include at least one task feedback box. The task feedback box may include task description information and result viewing controls. The task description information may include task number (40664242), creation time (20:00 on September 26), problem status (created), etc. The result viewing control may be used to trigger the mobile phone to display the problem location result. Afterwards, when it is detected that the result viewing control in the task feedback box is triggered by the user, the mobile phone may display the first feedback information about the problem location result based on the result feedback interface, that is, the mobile phone may display Figure 8The result viewing interface shown in (b) in the figure. The first feedback information may be "After diagnosis, the problem you reported is caused by the incompatibility of the application version with the system version. We have paid attention to the application version for you. Please update the version in time. Thank you~".

[0146] In other embodiments, the mobile phone may only display the result feedback interface. Afterwards, the mobile phone may output the first feedback information about the above-mentioned problem location result by voice broadcast or smart dialing. As long as the first feedback information can be output, the specific voice output method is not limited. In this way, the user can quickly know the cause of the filled-in problem, minimize the closed-loop time of the filled-in problem, and improve the user experience. It can also reduce the situation where the user mistakenly believes that the filled-in problem is a problem with the electronic device itself, thereby improving the user's favorability and satisfaction with the electronic device.

[0147] For example, in the display Figure 6 In the case of the problem description interface shown in (c), if the user clicks the "Got it" control in the problem description interface, the mobile phone can display Figure 6 The result feedback interface shown in (d) in the figure. The feedback record interface may include at least one task feedback box. The task feedback box may only include the above-mentioned task description information, that is, the task feedback box may include the task number (40664242), creation time (20:00 on September 26), problem status (created), etc. Afterwards, the mobile phone may voice output the first feedback information of "After diagnosis, the problem you reported is caused by the incompatibility of the application version with the system version. We have paid attention to the application version for you. Please update the version in time. Thank you~".

[0148] In one implementation, Fig. 9 As shown, the process of the mobile phone analyzing multiple log files to obtain the problem location result of the filled-in question may specifically include: S6051~S6056:

[0149] S6051: For each log file, the mobile phone detects the log file and obtains a log detection result, wherein the log detection result is used to indicate whether the log file belongs to a log file of a third-party application.

[0150] Specifically, after determining that the filled-in question in the question filling information is an application crash problem, the mobile phone can detect the log file based on each captured log file to determine whether the log file is a log file of a third-party application.

[0151] In some embodiments, the mobile phone can determine whether the log file belongs to a log file of a third-party application by determining whether the above-mentioned log file meets the preset conditions. In other words, only when the log file meets the preset conditions can the mobile phone determine that the log file belongs to a log file of a third-party application, that is, the mobile phone can obtain a log detection result characterizing that the log file belongs to a log file of a third-party application. Among them, the preset conditions may include that the file name of the log file includes preset characters. Exemplarily, the preset characters may be data_app_native_crash or data_app_crash. In other words, if the file name of the log file includes data_app_native_crash, it means that the log file belongs to a log file of a third-party application. Therefore, the mobile phone can obtain a log detection result characterizing that the log file belongs to a log file of a third-party application.

[0152] In one implementation, when it is determined that the above-mentioned log detection result indicates that the log file belongs to a log file of a third-party application, it means that the cause of the above-mentioned filled-in problem may be obtained by analyzing the log file. Therefore, the mobile phone can execute S6052 to further detect the log file. When it is determined that the log detection result indicates that the log file does not belong to a log file of a third-party application, it means that the cause of the filled-in problem cannot be obtained by analyzing the log file. Therefore, the mobile phone can continue to determine whether the next log file belongs to a log file of a third-party application until a log file belonging to a third-party application is detected.

[0153] S6052: When the log detection result indicates that the log file belongs to a log file of a third-party application, the mobile phone determines whether the third-party application corresponding to the log file is the third-party application to which the filled-in question belongs.

[0154] In some embodiments, after determining that the above-mentioned log detection result indicates that the log file belongs to a log file of a third-party application, the mobile phone can further determine whether the third-party application corresponding to the log file is the third-party application to which the filled-in question belongs, that is, determine whether the third-party application corresponding to the log file is the target third-party application. If the third-party application corresponding to the log file is the third-party application to which the filled-in question belongs, it means that the log file is a log file generated by the third-party application to which the filled-in question belongs, that is, by analyzing the log file, it can be determined whether the above-mentioned filled-in question belongs to the problem of the third-party application. Therefore, the mobile phone can execute S6053 to further detect the log file to determine the cause of the filled-in question. If the third-party application corresponding to the log file is not the third-party application to which the filled-in question belongs, it means that the log file does not belong to the log file generated by the third-party application to which the filled-in question belongs, that is, by analyzing the log file, it cannot be determined whether the filled-in question belongs to the problem of the third-party application. Therefore, the mobile phone can return to S6051 to continue to determine whether the next log file belongs to the log file of the third-party application until a log file belonging to the third-party application is detected.

[0155] In one implementation, the mobile phone can determine whether the third-party application corresponding to the log file is the third-party application to which the filled-in question belongs by matching the application package name carried by the log file with the application package name of the application to which the filled-in question belongs. Specifically, the mobile phone can determine whether the application package name carried by the log file is the same as the application package name of the application to which the filled-in question belongs. If the application package name carried by the log file is the same as the application package name of the application to which the filled-in question belongs, it means that the third-party application corresponding to the log file is the third-party application to which the filled-in question belongs. If the application package name carried by the log file is different from the application package name of the application to which the filled-in question belongs, it means that the third-party application corresponding to the log file is not the third-party application to which the filled-in question belongs.

[0156] S6053: When the third-party application corresponding to the log file is the third-party application to which the filled-in question belongs, the mobile phone determines the log file as the target log file.

[0157] S6054, the mobile phone sends the target log file to the server.

[0158] Specifically, after determining that the third-party application corresponding to the above log file is the third-party application to which the filled-in question belongs, the mobile phone can send the log file as the target log file to the server, so that the server can locate the cause of the filled-in question based on the log file, providing convenient conditions for subsequent users to quickly know the cause of the filled-in question.

[0159] In some embodiments, the mobile phone may not send the target log file to the server. That is, the mobile phone can directly locate the cause of the filled problem according to the target log file. In this way, the transmission burden of the target log file can be reduced, and the situation where the mobile phone cannot receive the problem location result in time due to the transmission delay of the target log file can be reduced, thereby improving the output efficiency of the problem feedback.

[0160] S6055, when the server receives the target log file sent by the mobile phone, it matches the target log file with the log feature information in the log feature library to obtain the problem location result of the filled-in problem.

[0161] Specifically, after receiving the target log file sent by the mobile phone, the server can analyze the target log file to obtain the problem location result of the filled-in question. Exemplarily, the server can determine the problem location result of the filled-in question by matching the target log file with the log feature information in the log feature library.

[0162] Among them, the above-mentioned server stores a log feature library. The log feature library includes log feature information corresponding to multiple security reinforcement programs, and the log feature information corresponding to the security reinforcement program is the feature information of the corresponding log file when the application that uses the security reinforcement program for security reinforcement crashes. The log feature information is a feature string. It can be understood that each security reinforcement program corresponds to a software operator, that is, by running the security reinforcement program written by the software operator, third-party applications can have security reinforcement services.

[0163] For example, as shown in Table 1, the log feature information corresponding to the security hardening program written by software operator A is libDexHelper, the log feature information corresponding to the security hardening program written by software operator B is libnesec, the log feature information corresponding to the security hardening program written by software operator C is libshell, the log feature information corresponding to the security hardening program written by software operator D is libjiagu, the log feature information corresponding to the security hardening program written by software operator E is java.lang.VerifyError: Verifier rejected, and the log feature information corresponding to the security hardening program written by software operator F and software operator G is anonymous.

[0164] Table 1

[0165]

[0166] In some cases, the server can update the log feature library at a preset interval, which can provide a basis for the subsequent accurate determination of the problem location results.

[0167] It can be understood that if the above-mentioned target log file successfully matches any log feature information in the log feature library, that is, the target log file contains any log feature information in the log feature library, it means that the third-party application to which the target log file belongs has been security reinforced. In other words, during the operation of the third-party application to which the target log file belongs, the application may crash on the mobile phone because the application version is not compatible with the system version. Therefore, after determining that the target log file successfully matches any log feature information in the log feature library, the server can obtain a problem location result indicating that the cause of the problem is incompatibility between the target third-party application and the updated system version.

[0168] In some embodiments, the server can determine whether the above-mentioned target log file has a log feature in the log feature library. If the target log file has any log feature in the log feature library, it means that the third-party application to which the target log file belongs has been security-reinforced. Therefore, the problem location result obtained by the server can indicate that the reason for the filled-in problem is that the target third-party application is incompatible with the updated system version. If the target log file does not have the log feature information in the log feature library, it means that the third-party application to which the target log file belongs has not been security-reinforced. Therefore, the problem location result obtained by the server can indicate that the reason for the filled-in problem is not that the target third-party application is incompatible with the updated system version.

[0169] For example, the target log file includes " / data / app / lib / arm / libDexHelper.so". It can be seen that the target log file includes the log feature information corresponding to the security hardening program written by software operator A in Table 1 (i.e., libDexHelper). Therefore, the problem location result obtained by the server can indicate that the reason for the filled problem is that the target third-party application is incompatible with the updated system version.

[0170] S6056, the server sends the question location result of the filled-in question to the mobile phone.

[0171] Specifically, after obtaining the problem location result of the filled-in question, the server can send the problem location result of the filled-in question to the mobile phone, so that the mobile phone can promptly notify the user of the problem location result of the filled-in question, so that the user can quickly know the cause of the filled-in question, which minimizes the closed-loop time of the filled-in question and improves the user's experience. It can also reduce the situation where the user mistakenly believes that the filled-in question is a problem with the electronic device itself, thereby improving the user's favorability and satisfaction with the electronic device.

[0172] In one implementation, after the server executes step S6055, that is, after obtaining the problem location result of the filled-in question, if the problem location result of the filled-in question indicates that the cause of the filled-in question is that the target third-party application is incompatible with the updated system version, the server can further determine the solution to the filled-in question based on the target third-party application, so as to provide timely feedback to the user on the solution to the filled-in question, so that the user can know the solution to the filled-in question in time, which provides convenient conditions for the subsequent solution of the filled-in question. Specifically, Fig.10 As shown, the exception handling method may further include S6057~S6058 and S606a:

[0173] S6057, when the problem location result of the filled-in problem indicates that the cause of the filled-in problem is that the target third-party application is incompatible with the updated system version, the server obtains a problem solution for the filled-in problem from a solution plan library according to the target third-party application.

[0174] Specifically, after determining that the problem location result of the filled-in problem indicates that the cause of the filled-in problem is that the target third-party application is incompatible with the updated system version, the server can obtain the problem solution of the filled-in problem from the solution plan library according to the target third-party application. In this way, it is convenient for users to know the problem solution of the filled-in problem in a timely manner, which provides convenient conditions for subsequent timely updating of the application version to solve the filled-in problem as soon as possible.

[0175] In some embodiments, the server may obtain a solution plan library for the incompatibility problem between the application version and the system version. The solution plan library includes problem solution plans for multiple third-party applications. The problem solution plan may include the application name of the third-party application, the application package name of the third-party application, and the problem solution. The problem solution may include exception solution progress information and / or exception solution time. Afterwards, the server may obtain the problem solution for the filled problem from the solution plan library based on the application name and / or application package name of the target third-party application.

[0176] In some cases, the above exception resolution progress information can be used to indicate that there is a planned version of the target third-party application that can solve the application crash problem and is compatible with the updated system version, and the above exception resolution time includes the release time of the planned version.

[0177] In other cases, the above-mentioned exception resolution progress information can also be used to indicate that there is no planned version of the target third-party application that can solve the application crash problem and is compatible with the updated system version, and to prompt the user to provide feedback on the application crash exception through the preset feedback path of the target third-party application.

[0178] For example, taking the above solution plan library including multiple problem solution plans in Table 2 as an example, problem solution plan 1 may include the application package name "com.xxx", the application name "XX Bank", the exception solution progress information "XX Bank has not yet adapted to the system version, and it is expected to release a new version on December 30, 2024 to solve it" and the exception solution time "December 30, 2024". Problem solution plan 2 may include the application package name "xxxx", the application name "XX News", the exception solution progress information "XX News has not yet adapted to the system version, and there is no adaptation plan for the application" and the exception solution time "None".

[0179] Table 2

[0180]

[0181] In one implementation, the server may determine whether there is a problem solution that is compatible with the target third-party application in the solution plan library. If there is a problem solution that is compatible with the target third-party application in the solution plan library, the server may determine the problem solution as the problem solution for the filled-in problem. If there is no problem solution that is compatible with the target third-party application in the solution plan library, it means that the target third-party application does not belong to the application program existing in the mobile phone application market, that is, the target third-party application is an application program downloaded through other channels, and the specific cause of the filled-in problem cannot be accurately determined, and the server may not generate a problem solution for the filled-in problem.

[0182] For example, the application name of the target third-party application is XX Bank, and the solution plan library includes multiple problem solution plans in Table 2. It can be seen that the application name corresponding to the problem solution plan 1 in Table 2 is XX Bank, that is, there is a problem solution adapted to the third-party application to which the filled-in problem belongs in the solution plan library. Therefore, the server can use the exception solution progress information "XX Bank has not yet adapted the system version, and it is expected to release a new version on December 30, 2024 to solve it" and the exception solution time "December 30, 2024" in the problem solution plan 1 as the problem solution for the filled-in problem.

[0183] S6058, the server sends a solution to the filled-in question to the mobile phone.

[0184] Specifically, after obtaining the solution to the above-mentioned filled-in question, the server can send the solution to the filled-in question to the mobile phone, so that the mobile phone can promptly inform the solution to the filled-in question, making it convenient for the user to clearly understand the solution to the filled-in question, and providing convenient conditions for subsequent users to use the mobile phone more smoothly.

[0185] It should be noted that the process of the server sending the problem location result of the filled-in question and the process of the server determining the problem solution of the filled-in question can be performed simultaneously or in a preset order, and there is no specific limitation. For example, the server can execute steps S6057~S6058 while executing step S6056. For another example, the server can first execute steps S6057~S6058, and then execute step S6056. For another example, the server can first execute step S6057, and then execute steps S6056 and S6058 at the same time.

[0186] S606a, when the mobile phone receives the problem solution of the filled-in question sent by the server, the mobile phone performs a result feedback operation according to the problem location result of the filled-in question and the problem solution of the filled-in question.

[0187] Specifically, after receiving the problem solution of the filled-in question sent by the server, the mobile phone can perform a result feedback operation according to the problem solution of the filled-in question and the problem location result of the filled-in question. Among them, the result feedback operation also includes feedback of the problem solution of the filled-in question. In this way, the user can know the cause of the filled-in question while also knowing the problem solution of the filled-in question, which is convenient for the user to clearly understand the problem solution of the filled-in question and improve the user's usage experience.

[0188] In some embodiments, the mobile phone can display second feedback information about the above problem solution and problem location result based on the result feedback interface. The second feedback information is used to indicate the cause and solution of the above filled problem. For example, see Figure 8 , upon detection Figure 8 When the result viewing control of the task feedback box in the result feedback interface shown in (a) is triggered by the user, the mobile phone can display the second feedback information about the above problem solution and problem location result based on the result feedback interface, that is, the mobile phone can display Figure 8 The result viewing interface shown in (c) in the figure. The second feedback information may be "After diagnosis, the application you are using is not yet compatible with the system version. A new version is expected to be released on December 30, 2024 to resolve the problem. Please pay attention to the application version update."

[0189] In other embodiments, the mobile phone may only display the result feedback interface. Afterwards, the mobile phone may output the second feedback information about the above-mentioned problem solution and the problem location result by voice broadcast. As long as the second feedback information can be output, the specific voice output method is not limited. Figure 6At the same time as the result feedback interface shown in (d) is displayed, the voice output is the second feedback information "After diagnosis, the application you are using is not yet adapted to the system version. It is expected that a new version will be released on December 30, 2024 to solve the problem. Please pay attention to the application version update."

[0190] It should be noted that the process of the server determining the problem location result of the filled problem and obtaining the problem solution of the filled problem can also be executed by the mobile phone, that is, the mobile phone can regularly store the log feature library and the solution plan library. After determining the target log file, the mobile phone can directly match the target log file with the log feature library stored in the mobile phone without sending the target log file to the server. If the target log file matches any log feature information in the log feature library successfully, the mobile phone can directly obtain the problem location result indicating that the cause of the filled problem is that the target third-party application is incompatible with the updated system version. After that, the mobile phone can directly obtain the problem solution of the filled problem from the solution plan library stored in the mobile phone according to the target third-party application, and perform the result feedback operation according to the problem location result and the problem solution. In this way, the transmission burden of data (such as target log files, problem location results, etc.) can be reduced, and the situation where the mobile phone cannot receive the problem location result in time due to data transmission delay is reduced, thereby improving the output efficiency of problem feedback.

[0191] In some embodiments, the present application provides a computer-readable storage medium, including computer instructions, which, when executed on an electronic device, enable the electronic device to execute the method described above.

[0192] In some embodiments, the present application provides a computer program product. When the computer program product is run on an electronic device, the electronic device executes the method as described above.

[0193] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the division of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

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

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

[0196] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0197] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor (processor) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read only memory (ROM), random access memory (RAM), disk or optical disk and other media that can store program code.

[0198] The same or similar parts between the various embodiments in this application can refer to each other. In the various embodiments in this application, and the various implementation methods / implementation methods / implementation methods in each embodiment, if there is no special explanation and logical conflict, the terms and / or descriptions between different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment are consistent and can be referenced to each other. The technical features in different embodiments and the various implementation methods / implementation methods / implementation methods in each embodiment can be combined to form new embodiments, implementation methods, implementation methods, or implementation methods according to their inherent logical relationships. The above-described implementation methods of this application do not constitute a limitation on the scope of protection of this application.

[0199] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any technician familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims. In short, the above is only a preferred embodiment of the technical solution of the present application, and is not used to limit the protection scope of the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present application should be included in the protection scope of the present application.

Claims

1. An exception handling method, characterized in that: Applied to an electronic device, a third-party application installed in the electronic device has a security reinforcement service, the security reinforcement service is implemented by a security reinforcement program, and the electronic device updates the system version, the method includes: In response to a user's feedback operation regarding an application crash, the electronic device acquires a target log file; wherein the target log file is a log file generated by a target third-party application, and the target third-party application is a third-party application in the electronic device where the application crash occurs; The electronic device sends the target log file to the server; The electronic device receives the abnormality location result sent by the server; the abnormality location result is obtained based on the analysis of the target log file, and the abnormality location result is used to indicate whether the reason for the application crash is that the target third-party application is incompatible with the updated system version, wherein when the target third-party application is incompatible with the updated system version, the target third-party application cannot normally run the security reinforcement program; The electronic device performs a result feedback operation according to the abnormal positioning result; wherein the result feedback operation includes feeding back the cause of the application crash exception.

2. The method according to claim 1, characterized in that: The application crash exception is an abnormal problem that occurs when the target third-party application is cold started.

3. The method according to claim 1, characterized in that The electronic device performs a result feedback operation, including: The electronic device displays first feedback information; wherein the first feedback information is used to indicate the reason why the application crashes; and / or, The electronic device outputs the first feedback information in a preset voice output manner.

4. The method according to claim 1, characterized in that: The electronic device receives the abnormal positioning result sent by the server, including: The electronic device receives the abnormal location result and the abnormal solution sent by the server; wherein the abnormal location result is used to indicate that the reason for the application crash is that the target third-party application is incompatible with the updated system version, and the abnormal solution includes abnormal solution progress information and / or abnormal solution time; The electronic device performs a result feedback operation according to the abnormality positioning result, including: The electronic device performs a result feedback operation according to the abnormal positioning result and the abnormal solution; wherein the result feedback operation also includes feeding back the abnormal solution.

5. The method according to claim 4, characterized in that The exception resolution progress information is used to indicate that there is a planned version of the target third-party application that can resolve the application crash exception and is compatible with the updated system version, and the exception resolution time includes the release time of the planned version; or, The exception resolution progress information is used to indicate that the planned version does not exist, and to prompt the user to provide feedback on the application crash exception through a preset feedback path of the target third-party application.

6. The method according to claim 4, characterized in that The electronic device performs a result feedback operation according to the abnormal positioning result and the abnormal solution, including: The electronic device displays second feedback information; wherein the second feedback information is used to indicate the cause of the application crash exception and the exception solution; and / or, The electronic device outputs the second feedback information in a preset voice output manner.

7. The method according to any one of claims 1 to 6, characterized in that The electronic device obtaining a target log file in response to a user's feedback operation on an abnormal application crash, comprising: In response to the user's feedback operation on the application crash exception, the electronic device obtains a plurality of log files located within a preset time period before and after the abnormal occurrence time of the application crash exception; The electronic device determines the target log file from the multiple log files.

8. The method according to claim 7, characterized in that The electronic device determines the target log file from the multiple log files, including: For each of the multiple log files, the electronic device detects the log file to obtain a log detection result; wherein the log detection result is used to indicate whether the log file belongs to a log file of a third-party application; In a case where the log detection result indicates that the log file belongs to a log file of a third-party application, if the third-party application corresponding to the log file is the target third-party application, the log file is the target log file.

9. The method according to claim 8, characterized in that For each of the multiple log files, the electronic device detects the log file, including: The electronic device detects the log files in a chronological order from the end according to the generation time of the multiple log files, starting from the log file whose generation time is closest to the time when the abnormality occurs.

10. The method according to claim 8, characterized in that In a case where the file name of the log file includes preset characters, the log detection result indicates that the log file belongs to a log file of a third-party application; When the file name of the log file does not include preset characters, the log detection result indicates that the log file does not belong to a log file of a third-party application.

11. The method according to claim 7, characterized in that The multiple log files include log files in a first folder and a second folder, the first folder is used to store log files generated when an abnormal problem occurs during the operation of an application of the electronic device, the abnormal problem includes an application crash exception, and the second folder is used to store all log files generated during the operation of the electronic device; The electronic device determines the target log file from the multiple log files, including: The electronic device obtains the log files in the first folder from the multiple log files; The electronic device determines the target log file from the log files in the first folder.

12. The method according to any one of claims 1 to 6, characterized in that In response to the user's feedback operation on the application crash exception, before the electronic device obtains the target log file, the method further includes: The electronic device detects a log feedback start operation; After an application flashback exception occurs, in response to a user triggering an operation on a feedback problem control in a pull-down notification bar, the electronic device displays a problem description interface; The electronic device obtains description information of the application crash exception input by the user on the problem description interface.

13. An exception handling method, characterized in that: Applied to a server, the method comprises: The server receives a target log file sent by the electronic device; wherein the target log file is a log file generated by a target third-party application, and the target third-party application is a third-party application in which the application crashes abnormally in the electronic device; The server analyzes the target log file to obtain an exception location result; wherein the exception location result is used to indicate whether the cause of the application flash back exception is that the target third-party application is incompatible with the updated system version of the electronic device, and when the target third-party application is incompatible with the updated system version, the target third-party application cannot run the security reinforcement program normally, and the security reinforcement program is used to enable the target third-party application to have a security reinforcement service; The server sends the abnormality location result to the electronic device; wherein the abnormality location result is used for the electronic device to feedback the reason for the abnormal application crash to the user.

14. The method according to claim 13, characterized in that The server analyzes the target log file to obtain an abnormality location result, including: The server matches the target log file with the log feature information in the log feature library to obtain the anomaly location result; wherein the log feature library includes log feature information corresponding to multiple security hardening programs, and the log feature information corresponding to the security hardening program is the feature information of the corresponding log file when an application that uses the security hardening program for security hardening crashes.

15. The method according to claim 14, characterized in that The log feature information is a feature string. The server matches the target log file with the log features in the log feature library to obtain the anomaly locating result, including: In the case where the target log file includes any characteristic string in the log characteristic library, the server determines that the abnormality location result indicates that the reason for the application crash is that the target third-party application is incompatible with the updated system version of the electronic device; or In the case that the target log file does not include a feature string in the log feature library, the server determines that the abnormality locating result indicates that the reason for the application crash exception is not that the target third-party application is incompatible with the updated system version of the electronic device.

16. The method according to any one of claims 13 to 15, characterized in that After the server analyzes the target log file and obtains an abnormality location result of the application crash exception, the method further includes: In the case where the abnormal location result indicates that the reason for the application crash exception is that the target third-party application is incompatible with the updated system version of the electronic device, the server obtains an abnormal solution for the application crash exception from a solution plan library according to the target third-party application; wherein the abnormal solution includes abnormal solution progress information and / or abnormal solution time; The server sending the abnormality positioning result to the electronic device includes: The server sends the abnormal positioning result and the abnormal solution to the electronic device.

17. An electronic device, characterized in that: The electronic device includes a memory and one or more processors; the memory and the processor are coupled; the memory is used to store computer program code, and the computer program code includes computer instructions; when the processor executes the computer instructions, the electronic device executes the method as described in any one of claims 1 to 12.

18. A server, characterized in that: The server includes a memory and one or more processors; the memory and the processor are coupled; the memory is used to store computer program code, and the computer program code includes computer instructions; when the processor executes the computer instructions, the server executes the method as described in any one of claims 13 to 16.

19. A computer-readable storage medium, characterized in that: The method comprises computer instructions, which, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 12 or the method according to any one of claims 13 to 16.

20. A computer program product, characterized in that The method comprises computer instructions, which, when executed by a processor, cause the processor to perform the method according to any one of claims 1 to 12 or the method according to any one of claims 13 to 16.

Images