CN109800100B - Method and terminal for preventing IOS project from being crashed - Google Patents
Method and terminal for preventing IOS project from being crashed Download PDFInfo
- Publication number
- CN109800100B CN109800100B CN201811586938.0A CN201811586938A CN109800100B CN 109800100 B CN109800100 B CN 109800100B CN 201811586938 A CN201811586938 A CN 201811586938A CN 109800100 B CN109800100 B CN 109800100B
- Authority
- CN
- China
- Prior art keywords
- crash
- ios
- project
- class
- ios project
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The invention provides a method and a terminal for preventing an IOS project from being crashed, which intercept all possible crashing methods in the IOS project; judging whether the intercepted method can cause the IOS project to crash, if so, acquiring crash information corresponding to the method; uploading the crash information to a server, and sending notification information of the crash occurrence to the IOS project; the hidden interception breakdown is realized, the breakdown of the IOS project can be monitored, when the breakdown occurs, the breakdown is positioned, specific breakdown information is acquired, the notice is sent to the IOS project, the project can provide corresponding response for a user, the bug can be conveniently positioned and repaired at the later stage, and the user experience of the project is enhanced.
Description
Technical Field
The invention relates to the field of software project management, in particular to a method and a terminal for preventing an IOS project from being crashed.
Background
In the development process of the IOS project, the software is crashed for various reasons, and if the crash occurs in the development process, the cause of the crash can be found. However, if the item is a project that has already been published online, the user experience will be greatly affected by the crash. And because the collapse collection mechanism carried by the apple is not perfect, and many collapse collections can not be obtained, the specific problem can not be known in time where the problem is located, and meanwhile, according to the shelf-loading rule of the apple, thermal repair is forbidden and the audit time is slightly long, so that the collapse of the IOS project can not be repaired in time.
Disclosure of Invention
The technical problem to be solved by the invention is as follows: provided are a method and a terminal for preventing an IOS project from being crashed, wherein when the IOS project is crashed, the crash can be repaired in time.
In order to solve the technical problems, the invention adopts a technical scheme that:
a method of preventing an IOS project crash, comprising the steps of:
s1, intercepting all methods which possibly cause crash in an IOS project;
s2, judging whether the intercepted method can cause the IOS project to be crashed or not, and if so, acquiring crash information corresponding to the method;
and S3, uploading the crash information to a server, and sending the crash occurrence notification information to the IOS project.
In order to solve the technical problem, the invention adopts another technical scheme as follows:
a terminal for preventing IOS project crash, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor implementing the computer program when executing the computer program:
s1, intercepting all methods which possibly cause crash in an IOS project;
s2, judging whether the intercepted method can cause the IOS project to be crashed or not, and if so, acquiring crash information corresponding to the method;
and S3, uploading the crash information to a server, and sending the crash occurrence notification information to the IOS project.
The invention has the beneficial effects that: screening all methods which possibly cause the IOS project crash, intercepting and downloading the methods which possibly cause the IOS project crash, uploading corresponding crash information to a server, informing the IOS project, realizing recessive interception crash, realizing monitoring on the IOS project crash, realizing positioning crash and acquiring specific crash information when the crash occurs, sending the notice to the IOS project, enabling the project to provide corresponding response to a user, facilitating later positioning and repairing bugs, timely repairing the crash and enhancing the user experience of the project.
Drawings
FIG. 1 is a flowchart illustrating steps of a method for preventing an IOS project from crashing according to an embodiment of the present invention;
FIG. 2 is a schematic structural diagram of a terminal for preventing IOS project breakdown according to an embodiment of the present invention;
description of the reference symbols:
1. a terminal for preventing an IOS project from collapsing; 2. a memory; 3. a processor.
Detailed Description
In order to explain technical contents, achieved objects, and effects of the present invention in detail, the following description is made with reference to the accompanying drawings in combination with the embodiments.
The most key concept of the invention is as follows: screening all the methods which possibly cause the IOS project crash, intercepting and downloading the methods which cause the IOS project crash, uploading the corresponding crash information to the server, and informing the IOS project to realize the recessive interception crash.
Referring to fig. 1, a method for preventing IOS project crash includes the steps of:
s1, intercepting all methods which possibly cause crash in an IOS project;
s2, judging whether the intercepted method can cause the IOS project to crash, and if so, acquiring crash information corresponding to the method;
and S3, uploading the crash information to a server, and sending the crash occurrence notification information to the IOS project.
As can be seen from the above description, the beneficial effects of the present invention are: screening all the methods which possibly cause the IOS project crash, intercepting and downloading the methods which can cause the IOS project crash, uploading corresponding crash information to a server, informing the IOS project, realizing hidden interception crash, realizing monitoring on the IOS project crash, positioning the crash and obtaining specific crash information when the crash occurs, sending the information to the IOS project, enabling the project to provide corresponding response to a user, facilitating later positioning and repairing bugs, timely repairing the crash, and enhancing user experience of the project.
Further, all the possible methods for causing a crash in step S1 include: general class, array class, dictionary class, and string class.
According to the description, all the methods which can cause the crash are determined according to the methods in the general class, the array class, the dictionary class and the character string class, so that the comprehensiveness of the collection of all the methods which can cause the crash can be ensured.
Further, the step S2 includes:
and judging whether the intercepted method can cause the IOS project to be crashed or not by adopting a judging mode corresponding to the intercepted method, if so, stopping the continuous operation of the method, and acquiring the crash information corresponding to the method through a stack, otherwise, normally operating the method.
According to the description, different methods adopt adaptive judging modes to judge whether the crash is caused, the accuracy is high, the pertinence is strong, and the accuracy of the acquired crash information can be ensured through the corresponding crash information of the stack acquisition method.
Further, obtaining the crash information corresponding to the method through a stack includes:
stack information corresponding to the method is obtained through stacking;
acquiring a class name and a method name which generate collapse according to the stack information through a regular expression;
and taking the stack information and the class name and the method name which generate the crash as the crash information corresponding to the method.
From the above description, it can be known that the crash can be accurately located and specific crash information can be obtained by obtaining the stack information corresponding to the stack obtaining method and obtaining the class name and the method name of the crash through the regular expression.
Further, the step S3 is followed by the step of:
receiving a processing response of the IOS item to the crash;
according to the processing response, automatically returning to the previous page of the current page, and prompting that an error occurs;
receiving a retry request, and if the received retry requests exceed a preset number of times and all responses fail, jumping to a temporary webpage and executing a function corresponding to the method;
or directly prompting that unknown errors occur according to the processing response;
receiving retry requests, jumping to a temporary webpage and prompting that unknown errors occur if the received retry requests exceed a preset number of times and all responses fail, and receiving operation aiming at the method at the temporary webpage.
As can be seen from the above description, by sending the notification information of the occurrence of the crash to the IOS item, it is possible to receive a processing response of the IOS item to the crash, execute a friendly processing manner, and enhance user experience.
Referring to fig. 2, a terminal for preventing IOS project crash includes a memory, a processor and a computer program stored in the memory and running on the processor, wherein the processor executes the computer program to implement the following steps:
s1, intercepting all methods which may cause crash in an IOS project;
s2, judging whether the intercepted method can cause the IOS project to be crashed or not, and if so, acquiring crash information corresponding to the method;
and S3, uploading the crash information to a server, and sending the crash occurrence notification information to the IOS project.
As can be seen from the above description, the beneficial effects of the present invention are: screening all methods which possibly cause the IOS project crash, intercepting and downloading the methods which possibly cause the IOS project crash, uploading corresponding crash information to a server, informing the IOS project, realizing recessive interception crash, realizing monitoring on the IOS project crash, realizing positioning crash and acquiring specific crash information when the crash occurs, sending the notice to the IOS project, enabling the project to provide corresponding response to a user, facilitating later positioning and repairing bugs, timely repairing the crash and enhancing the user experience of the project.
Further, all the possible methods for causing a crash in step S1 include: general class, array class, dictionary class, and string class.
According to the description, all the methods which can cause the crash are determined according to the methods in the general class, the array class, the dictionary class and the character string class, so that the comprehensiveness of the collection of all the methods which can cause the crash can be ensured.
Further, the step S2 includes:
and judging whether the intercepted method can cause the IOS project to be crashed or not by adopting a judging mode corresponding to the intercepted method, if so, stopping the continuous operation of the method, and acquiring the crash information corresponding to the method through a stack, otherwise, normally operating the method.
According to the description, different methods adopt adaptive judging modes to judge whether the crash is caused, the accuracy is high, the pertinence is strong, and the accuracy of the acquired crash information can be ensured through the crash information corresponding to the stack acquisition method.
Further, obtaining the crash information corresponding to the method through a stack includes:
acquiring stack information corresponding to the method through a stack;
acquiring a class name and a method name which generate collapse according to the stack information through a regular expression;
and taking the stack information and the class name and the method name which generate the crash as the crash information corresponding to the method.
From the above description, it can be known that the crash can be accurately located and specific crash information can be obtained by obtaining the stack information corresponding to the stack obtaining method and obtaining the class name and the method name of the crash through the regular expression.
Further, the step S3 is followed by the step of:
receiving a processing response of the IOS item to the crash;
according to the processing response, automatically returning to the previous page of the current page, and prompting that an error occurs;
receiving a retry request, and if the received retry requests exceed a preset number of times and all responses fail, jumping to a temporary webpage and executing a function corresponding to the method;
or directly prompting that unknown errors occur according to the processing response;
receiving retry requests, jumping to a temporary webpage and prompting that unknown errors occur if the received retry requests exceed a preset number of times and all responses fail, and receiving operation aiming at the method at the temporary webpage.
As can be seen from the above description, by sending the notification information of the occurrence of the crash to the IOS project, it is possible to receive a processing response of the IOS project to the crash, execute a friendly processing manner, and enhance user experience.
Example one
Referring to fig. 1, a method for preventing IOS project crash includes the steps of:
s1, intercepting all methods which possibly cause crash in an IOS project;
intercepting all methods which may cause crash in the IOS project in an Aspect Programming (AOP) mode, and specifically intercepting all methods which may cause crash in a category + AOP + method exchange mode;
the conditions that are prone to causing a crash mainly come from mapping of methods or classes, processing of network data requested by a server, and the like, wherein the processing of the network data requested by the server is dispersed into classes such as an array (NSArray), a dictionary (NSDictionary), a string (NSString), and the like, so that some methods in these classes need to be intercepted, and all methods that may cause a crash include: general class, array class, dictionary class and character string class;
specific examples are as follows:
intercepting the following method for the general class NSobject class:
methodSignatureForSelector:、setValue:forKey:、setValue:forKeyPath:、setValue:forUndefinedKey:、setValuesForKeysWithDictionary:；
intercepting the following method for the array class NSarray class:
arrayWithObjects:count:、objectsAtIndexes:、objectAtIndex:、getObjects:range:、setObject:atIndexedSubscript:、removeObjectAtIndex:、insertObject:atIndex:；
intercepting the following method for a dictionary class NSDictionary class:
dictionaryWithObjects:forKeys:count:、
setObject:forKey:、setObject:forKeyedSubscript:、removeObjectForKey:；
intercepting the following method for the string class NSString class:
characterAtIndex:、
substringFromIndex:、
substringToIndex:、
substringWithRange:、
stringByReplacingOccurrencesOfString:withString:、
stringByReplacingOccurrencesOfString:withString:options:range:、
tringByReplacingCharactersInRange:withString:、
replaceCharactersInRange:withString:、insertString:atIndex:、
deleteCharactersInRange:、initWithString:、initWithAttributedString:、
initWithString:attributes:；
because the OC language is a dynamic language, a method _ exchange implementation method can be executed on a method to be intercepted in a + (void) load method in the classification, so that method exchange is realized, and a program can call a code written by us first when calling a corresponding method each time, thereby realizing processing of AOP;
s2, judging whether the intercepted method can cause the IOS project to be crashed or not, and if so, acquiring crash information corresponding to the method;
specifically, a judgment mode corresponding to the intercepted method is adopted to judge whether the intercepted method can cause the IOS project to be crashed or not, if yes, the continuous operation of the method is stopped, and crash information corresponding to the method is obtained through a stack, otherwise, the method is normally operated;
in the method for executing the AOP, according to the requirement, a universal type can judge whether the crash is caused by a try catch method, the original method is operated in a try module, and if the corresponding error is caught in the catch, the crash is caused;
the array type can judge whether the crash occurs during the insertion or deletion by a method of judging nil;
the type of the character string can judge whether the length or the position of the intercepted character string exceeds the length of the character string to judge whether the crash occurs;
after judging that the corresponding method can cause breakdown, if the array or the character string can be specially judged, corresponding accurate error information can be directly compiled, and the general type or the special type can acquire the current stack information by a [ NSThreadCallStackSymbols ] method;
acquiring the crash information corresponding to the method through the stack comprises the following steps:
stack information corresponding to the method is obtained through stacking;
acquiring a class name and a method name which generate collapse according to the stack information through a regular expression;
taking the stack information and the class name and the method name which generate the crash as the crash information corresponding to the method;
s3, uploading the crash information to a server, and sending the crash occurrence notification information to the IOS project;
specifically, the crash information may be stored locally by using a method such as nseserdefault or sql lite, and the crash information is sent to the server at an appropriate time according to a service requirement of the IOS project, in this embodiment, the nseserdefault is used, and the nseserdefault is sent to the server at a viewdidload;
wherein, using NSNotification center to execute the push of the notice information of the crash occurrence;
the step S3 is followed by the step of:
receiving a processing response of the IOS item to the crash;
according to the processing response, automatically returning to the previous page of the current page, and prompting that an error occurs;
receiving a retry request, and if the received retry requests exceed a preset number of times and all responses fail, jumping to a temporary webpage and executing a function corresponding to the method;
or directly prompting that unknown errors occur according to the processing response;
receiving retry requests, jumping to a temporary webpage and prompting that unknown errors occur if the received retry requests exceed a preset number of times and all responses fail, and receiving operation aiming at the method at the temporary webpage;
specifically, when the user receives a crash, several conditions can be set by himself/herself, and corresponding relatively friendly processing methods are performed respectively, in this embodiment, the crash is divided into two conditions, one is a crash sent when entering the controller, which is generally caused by a problem occurring in a data format transmitted by the server, and the other is a crash caused by an action of the user, which is generally caused by a problem occurring in mapping or a problem occurring in the server;
when a crash is initiated for the access controller, then the corresponding friendly processing is performed: automatically returning to the previous page of the current page, prompting a user to 'make an error, please try again later', requesting the network again according to the received retry request, and jumping to a temporary webpage and executing the function corresponding to the method if the three retry requests fail, wherein the server provides the address corresponding to the temporary webpage;
when the crash is caused by the action of the user, the user is directly prompted to 'unknown error occurs, please try again', if the three retries still fail, the user jumps to a temporary webpage and prompts 'unknown problem appears, please continue to operate in the webpage', and the operation aiming at the method is received in the temporary webpage.
Example two
Referring to fig. 2, a terminal 1 for preventing IOS project crash includes a memory 2, a processor 3, and a computer program stored on the memory 2 and capable of running on the processor 3, wherein the processor 3 implements the steps of the first embodiment when executing the computer program.
In summary, according to the method and the terminal for preventing the IOS project from collapsing provided by the present invention, the AOP processing is realized through the classification + method exchange and the characteristics of the dynamic language of the IOS, and different methods (methods which are prone to collapse) are exchanged for different modules, so as to realize the overall preliminary interception; calling the intercepted original method, and if the method is crashed, intercepting the method, thereby preventing the collapse of the iOS project; in addition, when the collapse occurs, the stack information is acquired and the stack information is screened to acquire the corresponding collapse information, the corresponding collapse information is stored to the local and uploaded to the service area at a proper time, so that the monitoring on the collapse of the iOS project is realized, and the problem can be repaired in time; in addition, when the crash happens, a notification is sent to tell the project, so that the project provides a friendly interactive mode to remind the user, and the user experience of the project is enhanced.
The above description is only an embodiment of the present invention, and is not intended to limit the scope of the present invention, and all equivalent modifications made by the present invention and the contents of the accompanying drawings, which are directly or indirectly applied to the related technical fields, are included in the scope of the present invention.
Claims (8)
1. A method for preventing an IOS project crash, comprising the steps of:
s1, intercepting all methods which possibly cause crash in an IOS project;
s2, judging whether the intercepted method can cause the IOS project to crash, and if so, acquiring crash information corresponding to the method;
s3, uploading the crash information to a server, and sending notification information of the crash occurrence to the IOS project;
the step S1 includes:
intercepting all methods which may cause crash in the IOS project by a section-oriented programming mode;
the section-oriented programming mode comprises the following steps:
in a + (void) load method in the classification, a method _ exchange interactions method is executed for the method needing to be intercepted, and the exchange of the methods is realized;
the step S2 includes:
judging whether the intercepted method can cause the IOS project to crash or not by adopting a judging mode corresponding to the intercepted method, if so, stopping the continuous operation of the method, and acquiring the crash information corresponding to the method through a stack, otherwise, normally operating the method, and calling the intercepted original method in the judging process.
2. The method of claim 1, wherein all possible crashes in step S1 include: general class, array class, dictionary class, and string class.
3. The method of claim 1, wherein obtaining crash information corresponding to the method via a stack comprises:
stack information corresponding to the method is obtained through stacking;
acquiring a class name and a method name which generate collapse according to the stack information through a regular expression;
and taking the stack information and the class name and the method name which generate the crash as the crash information corresponding to the method.
4. A method for preventing IOS project crash according to any of claims 1 to 3, characterized in that said step S3 is followed by the further steps of:
receiving a processing response of the IOS item to the crash;
according to the processing response, automatically returning to the previous page of the current page, and prompting that an error occurs;
receiving a retry request, and if the received retry request exceeds a preset number of times and all responses fail, jumping to a temporary webpage and executing a function corresponding to the method;
or directly prompting that unknown errors occur according to the processing response;
receiving retry requests, jumping to a temporary webpage and prompting that unknown errors occur if the received retry requests exceed a preset number of times and all responses fail, and receiving operation aiming at the method at the temporary webpage.
5. A terminal for preventing IOS project crash, comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the computer program implements the steps of:
s1, intercepting all methods which possibly cause crash in an IOS project;
s2, judging whether the intercepted method can cause the IOS project to be crashed or not, and if so, acquiring crash information corresponding to the method;
s3, uploading the crash information to a server, and sending the crash occurrence notification information to the IOS project;
the step S1 includes:
intercepting all methods which may cause crash in the IOS project by a section-oriented programming mode;
the section-oriented programming mode comprises the following steps:
in a + (void) load method in classification, executing a method _ exchange interactions method on a method needing to be intercepted, and realizing the exchange of the methods;
the step S2 includes:
judging whether the intercepted method can cause the IOS project to crash or not by adopting a judging mode corresponding to the intercepted method, if so, stopping the continuous operation of the method, and acquiring the crash information corresponding to the method through a stack, otherwise, normally operating the method, and calling the intercepted original method in the judging process.
6. The terminal of claim 5, wherein all possible crashes in step S1 include: general class, array class, dictionary class, and string class.
7. The terminal of claim 5, wherein the obtaining crash information corresponding to the method via a stack comprises:
stack information corresponding to the method is obtained through stacking;
acquiring a class name and a method name which generate collapse according to the stack information through a regular expression;
and taking the stack information and the class name and the method name which generate the crash as the crash information corresponding to the method.
8. The terminal of any one of claims 5 to 7, wherein the step S3 is further followed by the steps of:
receiving a processing response of the IOS item to the crash;
according to the processing response, automatically returning to the previous page of the current page, and prompting that an error occurs;
receiving a retry request, and if the received retry requests exceed a preset number of times and all responses fail, jumping to a temporary webpage and executing a function corresponding to the method;
or directly prompting that unknown errors occur according to the processing response;
receiving a retry request, jumping to a temporary webpage and prompting that an unknown error occurs if the received retry request exceeds a preset number of times and all responses fail, and receiving operation aiming at the method at the temporary webpage.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811586938.0A CN109800100B (en) | 2018-12-25 | 2018-12-25 | Method and terminal for preventing IOS project from being crashed |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811586938.0A CN109800100B (en) | 2018-12-25 | 2018-12-25 | Method and terminal for preventing IOS project from being crashed |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109800100A CN109800100A (en) | 2019-05-24 |
| CN109800100B true CN109800100B (en) | 2023-02-28 |
Family
ID=66557478
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811586938.0A Active CN109800100B (en) | 2018-12-25 | 2018-12-25 | Method and terminal for preventing IOS project from being crashed |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109800100B (en) |
Families Citing this family (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110865898B (en) * | 2019-10-12 | 2023-09-05 | 北京字节跳动网络技术有限公司 | Method, device, medium and equipment for converging crash call stack |
| CN112925667B (en) * | 2021-03-29 | 2024-03-08 | 北京奇艺世纪科技有限公司 | Method, device and equipment for preventing SDK from crashing and readable storage medium |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102694817A (en) * | 2012-06-08 | 2012-09-26 | 奇智软件（北京）有限公司 | Method, device and system for identifying abnormality of network behavior of program |
| CN106294134A (en) * | 2016-07-29 | 2017-01-04 | 腾讯科技（深圳）有限公司 | The collapse localization method of code and device |
| CN107085550A (en) * | 2017-03-31 | 2017-08-22 | 武汉斗鱼网络科技有限公司 | A kind of method and system for being used to collect application crashes information in iOS system |
| CN108459921A (en) * | 2018-02-23 | 2018-08-28 | 北京奇艺世纪科技有限公司 | Collapse file memory method, device and electronic equipment |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20140032255A1 (en) * | 2011-03-21 | 2014-01-30 | Tarek Mohamed Mohamed HEGAZI | System and method for schedule optimization |
-
2018
- 2018-12-25 CN CN201811586938.0A patent/CN109800100B/en active Active
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102694817A (en) * | 2012-06-08 | 2012-09-26 | 奇智软件（北京）有限公司 | Method, device and system for identifying abnormality of network behavior of program |
| CN106294134A (en) * | 2016-07-29 | 2017-01-04 | 腾讯科技（深圳）有限公司 | The collapse localization method of code and device |
| CN107085550A (en) * | 2017-03-31 | 2017-08-22 | 武汉斗鱼网络科技有限公司 | A kind of method and system for being used to collect application crashes information in iOS system |
| CN108459921A (en) * | 2018-02-23 | 2018-08-28 | 北京奇艺世纪科技有限公司 | Collapse file memory method, device and electronic equipment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109800100A (en) | 2019-05-24 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108108297B (en) | Method and device for automatic testing | |
| CN109062809B (en) | Online test case generation method and device and electronic equipment | |
| US9069903B2 (en) | Multi-platform test automation enhancement | |
| US20080133978A1 (en) | System and Method for Determining Fault Isolation in an Enterprise Computing System | |
| US7536599B2 (en) | Methods and systems for validating a system environment | |
| CN109800100B (en) | Method and terminal for preventing IOS project from being crashed | |
| US11893331B2 (en) | Device verification method, UVM verification platform, electronic apparatus and storage medium | |
| CN112684982B (en) | Data migration method, system, equipment and computer readable storage medium | |
| CN105786636B (en) | A kind of system repair and device | |
| CN110716878A (en) | Automatic interface testing method, device and system | |
| CN110737548B (en) | Data request method and server | |
| CN112000582A (en) | Server-side automatic test early warning method, device, equipment and storage medium | |
| US11676114B2 (en) | Automated control of distributed computing devices | |
| US20220043728A1 (en) | Method, apparatus, device and system for capturing trace of nvme hard disc | |
| CN107704365B (en) | Monitoring data reporting method and device for mobile terminal hybrid application | |
| US9477490B2 (en) | Milestone based dynamic multiple watchdog timeouts and early failure detection | |
| CN112822248A (en) | OTA upgrading method, OTA upgrading device, readable medium and electronic equipment | |
| CN116302738A (en) | Method, system, equipment and storage medium for testing chip | |
| CN111756594A (en) | Control method of pressure test, computer device and computer readable storage medium | |
| CN114675989A (en) | Data verification method and device, electronic equipment and storage medium | |
| CN110362464B (en) | Software analysis method and equipment | |
| CN107995273B (en) | iOS network management method | |
| CN108008972A (en) | Restorative procedure, the apparatus and system of the application program of client | |
| US7010781B1 (en) | Methods and apparatus for managing debugging I/O | |
| CN111026575B (en) | Abnormality processing method and device and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |