CN112882950A - Application debugging method and device, electronic equipment and computer readable storage medium - Google Patents
Application debugging method and device, electronic equipment and computer readable storage medium Download PDFInfo
- Publication number
- CN112882950A CN112882950A CN202110289363.1A CN202110289363A CN112882950A CN 112882950 A CN112882950 A CN 112882950A CN 202110289363 A CN202110289363 A CN 202110289363A CN 112882950 A CN112882950 A CN 112882950A
- Authority
- CN
- China
- Prior art keywords
- debugging
- terminal
- interface
- application
- software development
- 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.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/362—Software debugging
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/36—Preventing errors by testing or debugging software
- G06F11/3664—Environments for testing or debugging software
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The invention provides an application debugging method and device, electronic equipment and a computer readable storage medium, wherein the method comprises the following steps: acquiring an application debugging request sent by a first terminal; judging whether an interface called by the debugging method of the application debugging request exists in a software development kit of the first terminal or not; responding to that the software development kit of the first terminal does not have the interface, and acquiring interface debugging information of the debugging method; sending the interface debugging information to a second terminal so that the second terminal can call the debugging method in the second terminal based on the interface debugging information and determine a debugging result; and receiving and displaying the debugging result. By the technical scheme, the manual participation in the application debugging process is reduced, the debugging error rate is reduced, and the debugging efficiency is improved.
Description
[ technical field ] A method for producing a semiconductor device
The present invention relates to the field of application debugging technologies, and in particular, to an application debugging method and apparatus, an electronic device, and a computer-readable storage medium.
[ background of the invention ]
With the development of mobile terminal technology, mobile phone applications for mobile terminals, such as games, social contact, financing, shopping, and the like, are emerging. The application manufacturer firstly needs to debug the mobile phone application of the mobile terminal at the PC terminal, and then exports the mobile phone application of the mobile terminal to the mobile terminal or the mobile terminal simulator after the debugging is finished, and the mobile phone application is checked and accepted at the mobile terminal or the mobile terminal simulator.
However, the mobile phone application of the mobile terminal needs to use a mobile terminal-specific SDK (Software Development Kit), and the mobile terminal-specific SDK cannot be automatically debugged at the PC, which requires an application manufacturer to manually debug the mobile terminal-specific SDK or manually export the mobile terminal-specific SDK to the mobile terminal or a mobile terminal simulator and then debug the mobile terminal-specific SDK. The debugging difficulty is high, the consumed time is long, and the debugging efficiency is seriously influenced.
Therefore, how to improve the debugging efficiency becomes a technical problem to be solved urgently at present.
[ summary of the invention ]
The embodiment of the invention provides an application debugging method and device, electronic equipment and a computer readable storage medium, and aims to solve the technical problem of low debugging efficiency caused by a scheme of manually debugging or manually exporting and then debugging a special software development kit for a mobile terminal in the related technology.
In a first aspect, an embodiment of the present invention provides an application debugging method, including: acquiring an application debugging request sent by a first terminal; judging whether an interface called by the debugging method of the application debugging request exists in a software development kit of the first terminal or not; responding to that the software development kit of the first terminal does not have the interface, and acquiring interface debugging information of the debugging method; sending the interface debugging information to a second terminal so that the second terminal can call the debugging method in the second terminal based on the interface debugging information and determine a debugging result; and receiving and displaying the debugging result.
In the above embodiment of the present invention, optionally, the first terminal is a PC terminal, the second terminal is a mobile terminal, and the software development kit is a software development kit running on the mobile terminal.
In the above embodiment of the present invention, optionally, the acquiring the interface debugging information of the debugging method includes: acquiring interface debugging information of the debugging method through an engine bridging layer of a mobile terminal application in the first terminal; or acquiring interface debugging information of the debugging method through a hook function, wherein the hook function replaces the debugging method of the application debugging request, and is used for acquiring the interface debugging information and obtaining the debugging result after being called.
In the above embodiment of the present invention, optionally, the interface debugging information includes: the software development kit comprises a name of a method related to the software development kit, a name of parameters used by the method related to the software development kit, the number of the parameters, the type of the parameters and the values of the parameters.
In the above embodiment of the present invention, optionally, the sending the interface debugging information to the second terminal includes: serializing the interface debugging information and sending the interface debugging information after the serialization processing through a communication agent module applied to a mobile terminal in the first terminal; the receiving and displaying the debugging result comprises: receiving the debugging result and performing deserialization processing on the debugging result through the communication agent module; and sending the debugging result after the deserialization processing to an engine bridging layer of the mobile terminal application in the first terminal, so that the mobile terminal application obtains and displays the debugging result after the deserialization processing.
In the above embodiment of the present invention, optionally, the method further includes: in response to that the software development kit of the first terminal does not have the interface, stopping the current debugging process while acquiring the interface debugging information of the debugging method; after receiving the debugging result, the method further comprises: and continuing the current debugging process based on the debugging result.
In a second aspect, an embodiment of the present invention provides an application debugging method, including: acquiring interface debugging information, wherein the interface debugging information is interface debugging information of a debugging method of an application debugging request sent by a first terminal; calling the debugging method in the second terminal based on the interface debugging information and a software development kit of the second terminal, and determining a debugging result, wherein the software development kit of the second terminal has an interface called by the debugging method of the application debugging request; and sending the debugging result.
In the above embodiment of the present invention, optionally, the first terminal is a PC terminal, the second terminal is a mobile terminal, and the software development kit is a software development kit running on the mobile terminal.
In the above embodiment of the present invention, optionally, the acquiring the interface debugging information includes: receiving the interface debugging information and performing deserialization processing on the interface debugging information through a communication agent module of the second terminal; the sending the debugging result comprises: and carrying out serialization processing on the debugging result and sending the debugging result after the serialization processing through the communication agent module.
In the above embodiment of the present invention, optionally, the interface debugging information includes: the software development kit comprises a name of a method related to the software development kit, a name of parameters used by the method related to the software development kit, the number of the parameters, the type of the parameters and the values of the parameters.
In the foregoing embodiment of the present invention, optionally, the sending the debugging result includes: and sending the debugging result to the first terminal based on a sending mode indicated by the software development kit of the second terminal, wherein the sending mode indicated by the software development kit of the second terminal comprises a synchronous mode or an asynchronous mode.
In a third aspect, an embodiment of the present invention provides an application debugging apparatus, including: the first acquisition unit is used for acquiring an application debugging request sent by a first terminal; the judging unit is used for judging whether an interface called by the debugging method of the application debugging request exists in a software development kit of the first terminal; the second acquisition unit is used for responding to the situation that the software development kit of the first terminal does not have the interface, and acquiring the interface debugging information of the debugging method; the sending unit is used for sending the interface debugging information to a second terminal so that the second terminal can call the debugging method in the second terminal based on the interface debugging information and determine a debugging result; and the receiving unit is used for receiving and displaying the debugging result.
In the above embodiment of the present invention, optionally, the first terminal is a PC terminal, the second terminal is a mobile terminal, and the software development kit is a software development kit running on the mobile terminal.
In the above embodiment of the present invention, optionally, the second obtaining unit is configured to: acquiring interface debugging information of the debugging method through an engine bridging layer of a mobile terminal application in the first terminal; or acquiring interface debugging information of the debugging method through a hook function, wherein the hook function replaces the debugging method of the application debugging request, and is used for acquiring the interface debugging information and obtaining the debugging result after being called.
In the above embodiment of the present invention, optionally, the interface debugging information includes: the software development kit comprises a name of a method related to the software development kit, a name of parameters used by the method related to the software development kit, the number of the parameters, the type of the parameters and the values of the parameters.
In the foregoing embodiment of the present invention, optionally, the sending unit is configured to: serializing the interface debugging information and sending the interface debugging information after the serialization processing through a communication agent module applied to a mobile terminal in the first terminal; the receiving unit is used for: receiving the debugging result and performing deserialization processing on the debugging result through the communication agent module; and sending the debugging result after the deserialization processing to an engine bridging layer of the mobile terminal application in the first terminal, so that the mobile terminal application obtains and displays the debugging result after the deserialization processing.
In the above embodiment of the present invention, optionally, the method further includes: a process control unit, configured to, in response to that the software development kit of the first terminal does not have the interface, while obtaining interface debugging information of the debugging method, suspend a current debugging process, and after receiving the debugging result, further include: and continuing the current debugging process based on the debugging result.
In a fourth aspect, an embodiment of the present invention provides an application debugging apparatus, including: the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring interface debugging information, and the interface debugging information is interface debugging information of a debugging method of an application debugging request sent by a first terminal; the debugging unit is used for calling the debugging method in the second terminal and determining a debugging result based on the interface debugging information and a software development kit of the second terminal, wherein the software development kit of the second terminal has an interface called by the debugging method of the application debugging request; and the sending unit is used for sending the debugging result.
In the above embodiment of the present invention, optionally, the first terminal is a PC terminal, the second terminal is a mobile terminal, and the software development kit is a software development kit running on the mobile terminal.
In the above embodiment of the present invention, optionally, the obtaining unit is configured to: receiving the interface debugging information and performing deserialization processing on the interface debugging information through a communication agent module of the second terminal; the sending unit is used for: and carrying out serialization processing on the debugging result and sending the debugging result after the serialization processing through the communication agent module.
In the above embodiment of the present invention, optionally, the interface debugging information includes: the software development kit comprises a name of a method related to the software development kit, a name of parameters used by the method related to the software development kit, the number of the parameters, the type of the parameters and the values of the parameters.
In the foregoing embodiment of the present invention, optionally, the sending unit is configured to: and sending the debugging result to the first terminal based on a sending mode indicated by the software development kit of the second terminal, wherein the sending mode indicated by the software development kit of the second terminal comprises a synchronous mode or an asynchronous mode.
In a fifth aspect, an embodiment of the present invention provides an electronic device, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor, the instructions being arranged to perform the method of any of the first and/or second aspects above.
In a sixth aspect, an embodiment of the present invention provides a computer-readable storage medium storing computer-executable instructions for performing the method according to any one of the first and/or second aspects.
According to the technical scheme, aiming at the problem of low application debugging efficiency in the related technology, when a software development kit special for a mobile terminal needs to be debugged at a PC terminal, interface debugging information required by debugging the software development kit is automatically sent to the mobile terminal for debugging, and then a debugging result provided by the mobile terminal is directly obtained. Therefore, manual participation in the application debugging process is reduced, the debugging error rate is reduced, and the debugging efficiency is improved.
[ description of the drawings ]
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
FIG. 1 shows a flow diagram of an application debugging method according to one embodiment of the invention;
FIG. 2 shows a flow diagram of an application debugging method according to another embodiment of the invention;
FIG. 3 shows a flow diagram of an application debugging method according to yet another embodiment of the invention;
FIG. 4 shows a schematic diagram of application debugging according to an embodiment of the invention;
FIG. 5 shows a schematic diagram of application debugging according to another embodiment of the invention;
FIG. 6 shows a timing diagram of application debugging according to one embodiment of the invention;
FIG. 7 shows a block diagram of an application debugging apparatus according to an embodiment of the present invention;
FIG. 8 shows a block diagram of an application debugging apparatus according to another embodiment of the present invention;
FIG. 9 shows a block diagram of an electronic device according to an embodiment of the invention.
[ detailed description ] embodiments
For better understanding of the technical solutions of the present invention, the following detailed descriptions of the embodiments of the present invention are provided with reference to the accompanying drawings.
It should be understood that the described embodiments are only some embodiments of the invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The terminology used in the embodiments of the invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention. As used in the examples of the present invention and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise.
Example one
FIG. 1 shows a flow diagram of an application debugging method according to one embodiment of the invention.
As shown in fig. 1, an application debugging method according to an embodiment of the present invention includes:
And 104, judging whether an interface called by the debugging method of the application debugging request exists in the software development kit of the first terminal.
The first terminal is a PC terminal, the software development kit is a software development kit running on the mobile terminal, and the software development kit running on the mobile terminal cannot be automatically debugged on the PC terminal. When the mobile terminal is debugged at the PC terminal, the PC terminal sends an application debugging request, and in order to timely identify the problem that the software development kit may not be automatically debugged at the PC terminal, after the application debugging request is obtained, it is necessary to determine whether the content of the debugging requested by the application debugging request relates to debugging the software development kit (hereinafter referred to as software development kit) running at the mobile terminal.
Specifically, the software development kit cannot be automatically debugged at the PC, that is, the debugging method and the interface related to the software development kit, which are described in the application debugging request sent by the first terminal, cannot be provided by the PC. At this time, it may be determined whether the software development kit of the first terminal has an interface called by the debugging method of the application debugging request. If the result of the determination is yes, the debugging method and the corresponding interface can be directly called to execute the content of the application debugging request, otherwise, if the result of the determination is no, the first terminal does not have the capability of debugging the software development kit, that is, the content of the application debugging request, which is requested to be debugged, cannot be debugged directly at the first terminal.
And 106, responding to that the software development kit of the first terminal does not have the interface, and acquiring interface debugging information of the debugging method.
And step 110, receiving and displaying the debugging result.
It should be known that, the main body of the technical solution is the first terminal itself, the debugging device connected to the first terminal, or the debugging device arranged in the first terminal (hereinafter, the main body of the technical solution is collectively referred to as the first terminal), so that the interface debugging information can be sent to the second terminal, and since the second terminal is the mobile terminal or the mobile terminal simulator, the second terminal has the capability of debugging the software development kit running at the mobile terminal, therefore, the second terminal can directly call the corresponding debugging method based on the interface debugging information, and finally, the debugging result is sent to the first terminal, so that the first terminal can be used as a PC terminal to automatically debug the software development kit running at the mobile terminal.
The interface debugging information of the debugging method is information required for debugging the software development kit, and includes, but is not limited to, a name of a method related to the software development kit, a name of a parameter used by the method related to the software development kit, the number of the parameters, the type of the parameter, the parameter value, and the like.
Example two
Fig. 2 shows a flow diagram of an application debugging method according to another embodiment of the invention.
As shown in fig. 2, the application debugging method according to another embodiment of the present invention includes the following steps:
In one possible design, the manner of obtaining the interface debugging information of the debugging method includes: and acquiring interface debugging information of the debugging method through an engine bridging layer of a mobile terminal application in the first terminal. Specifically, an engine Bridge layer (Unity Bridge) of the mobile application in the first terminal can intercept the interface debugging information of the software development kit through the plug-in, so that the acquisition of the interface debugging information can be quickly realized.
In another possible design, the interface debugging information of the debugging method is acquired through a hook function, wherein the hook function replaces the debugging method of the application debugging request, and is used for acquiring the interface debugging information and obtaining the debugging result after being called. Specifically, the method for debugging the application debugging request is replaced by a hook function, so that the hook function can realize the function of the debugging method and can also have the function of acquiring interface debugging information for the debugging method. Therefore, the acquisition of the interface debugging information can be quickly realized in a hook mode.
And 208, serializing the interface debugging information and sending the interface debugging information after the serialization processing through a communication agent module applied to a mobile terminal in the first terminal.
Optionally, the communication Proxy module is a Proxy (Proxy class), and the Proxy operates in an application layer, and is configured to back up information to be remotely transmitted, and perform other operations that the first terminal does not want or cannot perform on the backed-up information. Specifically, the Proxy may back up interface debugging information of a software development kit that cannot be debugged by the first terminal, and send the back-up to the second terminal after performing serialization processing on the back-up. .
In addition, the interface debugging information is subjected to Proxy joint debugging through Proxy, so that the occupation of resources of the first terminal can be reduced, the internal access speed of the first terminal can be increased, the safety of the first terminal can be improved, and the direct action of illegal attacks on the interface of the mobile terminal special software development kit on the first terminal is avoided.
In an actual scene, the first terminal and the second terminal are both provided with a plurality of software development kit methods, so that the software development kit methods do not need to be transmitted between the first terminal and the second terminal, and only the interface debugging information of the software development kit running at the mobile terminal in the first terminal is sent to the second terminal. In the calling process, the software development kit method is equivalent to a frame, and the interface debugging information is equivalent to the specific setting information of the frame, so that the second terminal can call the corresponding debugging method based on the interface debugging information to realize the debugging of the software development kit. And finally, the first terminal executes the debugging function on the interface debugging information through the second terminal to obtain a debugging result.
In the process, in order to improve the information security level, when the first terminal sends the interface debugging information to the outside through the communication agent module applied to the mobile terminal in the first terminal, the interface debugging information can be serialized, and finally the interface debugging information after the serialization processing is sent. Similarly, when feeding back the debugging result to the first terminal, the second terminal also serializes the debugging result to ensure safety, and specifically, the second terminal can call an interface which is provided by itself and corresponds to the interface debugging information through a GBridge (bridge layer) to obtain the debugging result, and then serializes the debugging result through the GBridge and returns the debugging result to the first terminal.
The engine bridge layer of the mobile application is associated with the engine of the mobile application, and based on the above, the interface debugging information is intercepted at the engine bridge layer of the mobile application, so that the debugging result after the deserialization processing is received can be fed back to the engine bridge layer of the mobile application. Therefore, the engine bridging layer equivalent to the mobile terminal application automatically acquires the debugging result aiming at the interface debugging information based on the interface debugging information of the software development kit, reduces the manual participation of the application debugging process, reduces the debugging error rate and improves the debugging efficiency.
In this regard, the first terminal may receive the debug result and deserialize the debug result via the communication agent module. And finally, the first terminal provides the debugging result after the deserialization processing to the mobile terminal application through an engine bridging layer of the mobile terminal application in the first terminal, so that the mobile terminal application finally obtains and displays the debugging result after the deserialization processing, and the automatic debugging of the software development kit is completed.
According to the technical scheme, when the special software development kit for the mobile terminal needs to be debugged, the interface debugging information of the software development kit can be automatically sent to the mobile terminal for debugging, and then the debugging result provided by the mobile terminal is directly obtained. Therefore, the debugging of the special software development kit of the mobile terminal at the PC terminal can be realized without manual operation, the manual participation in the application debugging process is reduced, the debugging error rate is reduced, and the debugging efficiency is improved.
EXAMPLE III
FIG. 3 shows a flow diagram of an application debugging method according to yet another embodiment of the invention.
As shown in fig. 3, the application debugging method according to another embodiment of the present invention is applied to a second terminal, and the process thereof includes:
The second terminal is a mobile terminal or a mobile terminal simulator and has the capability of debugging the software development kit running at the mobile terminal, so that the corresponding debugging method can be directly called by the second terminal based on the interface debugging information of the debugging method of the application debugging request sent by the first terminal to obtain a debugging result, and finally the debugging result is sent to the first terminal, thereby realizing the automatic debugging of the software development kit running at the mobile terminal by the first terminal as a PC terminal.
Specifically, step 302 includes: receiving the interface debugging information and performing deserialization processing on the interface debugging information through a communication agent module of the second terminal; step 306 includes: and carrying out serialization processing on the debugging result and sending the debugging result after the serialization processing through the communication agent module.
Proxy in the first terminal needs to interact with the communication agent module of the second terminal, and joint debugging of the interface debugging information can be realized, so that the second terminal is configured with the communication agent module, and after the second terminal receives the interface debugging information through the communication agent module of the second terminal, the interface debugging information is debugged.
Optionally, the communication agent module of the second terminal is a MagicBox, and the MagicBox is a docking object of the Proxy, has a relay function, and meanwhile, has the capability of reducing signal interference, and can accurately and effectively obtain, for the second terminal, the interface debugging information received from the first terminal.
When the first terminal sends the interface debugging information to the outside through the Proxy of the mobile terminal application in the first terminal, the interface debugging information can be serialized, and the interface debugging information after the serialization processing is finally sent. Similarly, when feeding back the debugging result to the first terminal, the second terminal also serializes the debugging result to ensure safety, and specifically, the second terminal can call an interface which is provided by itself and corresponds to the interface debugging information through a GBridge (bridge layer) to obtain the debugging result, and then serializes the debugging result through the GBridge and returns the debugging result to the first terminal.
Therefore, the debugging of the special software development kit of the mobile terminal at the PC terminal can be realized without manual operation, the manual participation in the application debugging process is reduced, the debugging error rate is reduced, and the debugging efficiency is improved.
As shown in fig. 4, when the game debugging PC debugs the game application of the mobile terminal, a need for debugging the mobile terminal software development kit of the game application of the mobile terminal is encountered. At this time, the Proxy module in the game debugging PC (i.e., the first terminal) may intercept, at the engine bridge layer of the game debugging PC, interface debugging information of the mobile terminal software development kit of the game application of the mobile terminal, and send the interface debugging information to the MagicBox module of the local/remote mobile terminal (i.e., the second terminal) after performing serialization processing on the interface debugging information.
And the MagicBox module of the local/remote mobile terminal performs deserialization processing on the received information to obtain interface debugging information. Furthermore, the local/remote mobile terminal calls the self mobile terminal software development kit interface to execute debugging based on the interface debugging information, and a debugging result is obtained. And the MagicBox module of the local/remote mobile terminal carries out serialization processing on the debugging result and sends the debugging result after the serialization processing to the Proxy module of the game debugging PC terminal.
The communication between the game debugging PC end and the remote mobile end can be realized by forwarding through the server. In a possible design, the remote mobile terminal can provide a control path, and external research and development personnel can check the debugging process and the debugging result of the remote mobile terminal based on the interface debugging information of the mobile terminal software development kit to be debugged through the control path, so that the controllability of the debugging process of the mobile terminal software development kit is increased, the debugging work of the mobile terminal software development kit at the game debugging PC terminal is facilitated, the integral difficulty of game debugging is reduced, and the integral efficiency of game debugging is improved.
As shown in fig. 5, when the game debugging PC debugs the game application of the mobile terminal, a need for debugging the mobile terminal software development kit of the game application of the mobile terminal is encountered. At this time, the Proxy module in the game debugging PC (i.e., the first terminal) may intercept, at the engine bridge layer of the game debugging PC, interface debugging information of the mobile software development kit of the game application of the mobile terminal, and send the interface debugging information to the MagicBox module of the mobile simulator (i.e., the second terminal) after performing serialization processing on the interface debugging information.
And the MagicBox module of the mobile terminal simulator performs deserialization processing on the received information to obtain interface debugging information. Further, the mobile terminal simulator calls a self mobile terminal software development kit interface to execute debugging based on the interface debugging information to obtain a debugging result. And the MagicBox module of the mobile terminal simulator carries out serialization processing on the debugging result and sends the debugging result after the serialization processing to the Proxy module of the game debugging PC terminal.
On the basis of any one of the above technical solutions, finally, the Proxy module of the game debugging PC performs deserialization on the received content to obtain a debugging result, and returns the debugging result to the engine bridge layer that intercepts the interface debugging information. Thus, for the engine bridge layer, the debugging result of the interface debugging information is automatically obtained based on the interface debugging information.
Additionally, the technical solution of the present application may include: in response to that the software development kit of the first terminal does not have the interface, stopping the current debugging process while acquiring the interface debugging information of the debugging method; after receiving the debugging result, the method further comprises: and continuing the current debugging process based on the debugging result.
Specifically, for a first terminal, when a current debugging process for debugging a mobile-end application encounters a mobile-end-specific software development kit interface which cannot be debugged by itself, the current debugging process is halted while debugging work is transferred to an external second terminal. And finally, restarting the current debugging process when the debugging result from the second terminal is received. Therefore, the current debugging process is equivalent to directly obtaining the debugging result based on the interface debugging information of the mobile terminal software development kit to be debugged based on the interface debugging information, so that the negative influence of the application debugging process caused by the fact that the interface of the mobile terminal software development kit cannot be debugged is avoided, and the reliability of the debugging result is improved.
On the basis of any one of the above technical solutions, referring to fig. 6, in a game debugging PC end environment, a PC end connects a Unity Bridge through an interface methodA, the Unity Bridge intercepts interface debugging information of a mobile end software development kit to be debugged in a game engine Unity/unregeal or the like through a plug-in, and sends the interface debugging information to a Proxy at the PC end, and the Proxy serializes the interface debugging information and forwards the serialized information to a MagicBox in a mobile end environment through a Server. After the MagicBox calls the GBridge to process the information from the Proxy, a Native Module is called to obtain a debugging result, and the debugging result is synchronously returned or asynchronously returned to the PC end.
Specifically, the second terminal may send the debugging result to the first terminal based on a sending manner indicated by a software development kit of the second terminal, where the sending manner indicated by the software development kit of the second terminal includes a synchronous manner or an asynchronous manner.
Based on this, the synchronization mode refers to that the first terminal sends the interface debugging information of the mobile terminal software development kit to be debugged to the second terminal, and the second terminal returns the debugging result to the first terminal as a complete process, so that the integrity of the process can be ensured, and the probability of process errors is reduced.
The method comprises the steps that a first terminal sends interface debugging information of a mobile terminal software development kit to be debugged to a second terminal, and the second terminal returns a debugging result to the first terminal. Therefore, the asynchronous mode takes the interface debugging information of the mobile terminal software development kit to be debugged sent by the first terminal to the second terminal and the debugging result returned by the second terminal to the first terminal as two processes, so that the fluency of application debugging of the first terminal is improved.
Fig. 7 shows a block diagram of an application debugging apparatus according to an embodiment of the present invention.
As shown in fig. 7, an application debugging apparatus 700 according to an embodiment of the present invention includes: a first obtaining unit 702, configured to obtain an application debugging request sent by a first terminal; a determining unit 704, configured to determine whether an interface called by the debugging method of the application debugging request is in a software development kit of the first terminal; a second obtaining unit 706, configured to obtain, in response to that the software development kit of the first terminal does not have the interface, interface debugging information of the debugging method; a sending unit 708, configured to send the interface debugging information to a second terminal, so that the second terminal calls the debugging method in the second terminal based on the interface debugging information, and determines a debugging result; and a receiving unit 710, configured to receive and display the debugging result.
In the above embodiment of the present invention, optionally, the first terminal is a PC terminal, the second terminal is a mobile terminal, and the software development kit is a software development kit running on the mobile terminal.
In the foregoing embodiment of the present invention, optionally, the second obtaining unit 706 is configured to: acquiring interface debugging information of the debugging method through an engine bridging layer of a mobile terminal application in the first terminal; or acquiring interface debugging information of the debugging method through a hook function, wherein the hook function replaces the debugging method of the application debugging request, and is used for acquiring the interface debugging information and obtaining the debugging result after being called.
In the above embodiment of the present invention, optionally, the interface debugging information includes: the software development kit comprises a name of a method related to the software development kit, a name of parameters used by the method related to the software development kit, the number of the parameters, the type of the parameters and the values of the parameters.
In the above embodiment of the present invention, optionally, the sending unit 708 is configured to: serializing the interface debugging information and sending the interface debugging information after the serialization processing through a communication agent module applied to a mobile terminal in the first terminal; the receiving unit 710 is configured to: receiving the debugging result and performing deserialization processing on the debugging result through the communication agent module; and sending the debugging result after the deserialization processing to an engine bridging layer of the mobile terminal application in the first terminal, so that the mobile terminal application obtains and displays the debugging result after the deserialization processing.
In the above embodiment of the present invention, optionally, the method further includes: a process control unit, configured to, in response to that the software development kit of the first terminal does not have the interface, while obtaining interface debugging information of the debugging method, suspend a current debugging process, and after receiving the debugging result, further include: and continuing the current debugging process based on the debugging result.
The application debugging apparatus 700 uses the solutions described in any of the above embodiments, and therefore, has all the technical effects described above, and is not described herein again.
Fig. 8 shows a block diagram of an application debugging apparatus according to another embodiment of the present invention.
As shown in fig. 8, an application debugging apparatus 800 according to another embodiment of the present invention includes: an obtaining unit 802, configured to obtain interface debugging information, where the interface debugging information is interface debugging information of a debugging method of an application debugging request sent by a first terminal; a debugging unit 804, configured to call the debugging method in the second terminal based on the interface debugging information and a software development kit of the second terminal, and determine a debugging result, where the software development kit of the second terminal has an interface called by the debugging method of the application debugging request; a sending unit 806, configured to send the debugging result.
In the above embodiment of the present invention, optionally, the first terminal is a PC terminal, the second terminal is a mobile terminal, and the software development kit is a software development kit running on the mobile terminal.
In the above embodiment of the present invention, optionally, the obtaining unit 802 is configured to: receiving the interface debugging information and performing deserialization processing on the interface debugging information through a communication agent module of the second terminal; the sending unit 806 is configured to: and carrying out serialization processing on the debugging result and sending the debugging result after the serialization processing through the communication agent module.
In the above embodiment of the present invention, optionally, the interface debugging information includes: the software development kit comprises a name of a method related to the software development kit, a name of parameters used by the method related to the software development kit, the number of the parameters, the type of the parameters and the values of the parameters.
In the above embodiment of the present invention, optionally, the sending unit 806 is configured to: and sending the debugging result to the first terminal based on a sending mode indicated by the software development kit of the second terminal, wherein the sending mode indicated by the software development kit of the second terminal comprises a synchronous mode or an asynchronous mode.
The application debugging apparatus 800 uses the solutions described in any of the above embodiments, and therefore, has all the technical effects described above, and is not described herein again.
FIG. 9 shows a block diagram of an electronic device according to an embodiment of the invention.
As shown in fig. 9, an electronic device 900 of one embodiment of the invention includes at least one memory 902; and a processor 904 communicatively coupled to the at least one memory 902; wherein the memory stores instructions executable by the at least one processor 904, the instructions being configured to perform the scheme of any of the embodiments described above. Therefore, the electronic device 900 has the same technical effects as any of the above embodiments, and the details are not repeated herein.
The electronic device of embodiments of the present invention exists in a variety of forms, including but not limited to:
(1) mobile communication devices, which are characterized by mobile communication capabilities and are primarily targeted at providing voice and data communications. Such terminals include smart phones (e.g., iphones), multimedia phones, functional phones, and low-end phones, among others.
(2) The ultra-mobile personal computer equipment belongs to the category of personal computers, has calculation and processing functions and generally has the characteristic of mobile internet access. Such terminals include PDA, MID, and UMPC devices, such as ipads.
(3) Portable entertainment devices such devices may display and play multimedia content. Such devices include audio and video players (e.g., ipods), handheld game consoles, electronic books, as well as smart toys and portable car navigation devices.
(4) The server is similar to a general computer architecture, but has higher requirements on processing capability, stability, reliability, safety, expandability, manageability and the like because of the need of providing highly reliable services.
(5) And other electronic devices with data interaction functions.
In addition, an embodiment of the present invention provides a computer-readable storage medium, which stores computer-executable instructions for executing the method flow described in any of the above embodiments.
The technical scheme of the invention is described in detail with reference to the attached drawings, and aiming at the problem of low application debugging efficiency in the related technology, the interface debugging information of the mobile terminal software development kit to be debugged can be automatically sent to the external debugging main body for debugging when the software development kit needs to be debugged, and then the debugging result provided by the external debugging main body can be directly obtained. Therefore, manual participation in the application debugging process is reduced, the debugging error rate is reduced, and the debugging efficiency is improved.
It should be understood that the term "and/or" as used herein is merely one type of association that describes an associated object, meaning that three relationships may exist, e.g., a and/or B may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
It should be understood that although the terms first, second, etc. may be used to describe terminals in embodiments of the present invention, these terminals should not be limited by these terms. These terms are only used to distinguish one terminal from another. For example, a first terminal may also be referred to as a second terminal, and similarly, a second terminal may also be referred to as a first terminal, without departing from the scope of embodiments of the present invention.
The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination" or "in response to a detection", depending on the context. Similarly, the phrases "if determined" or "if detected (a stated condition or event)" may be interpreted as "when determined" or "in response to a determination" or "when detected (a stated condition or event)" or "in response to a detection (a stated condition or event)", depending on the context.
In the embodiments provided in the present invention, it should be understood that the disclosed system, apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and there may be other divisions in actual implementation, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, or in a form of hardware plus a software functional unit.
The integrated unit implemented in the form of a software functional unit may be stored in a computer readable storage medium. The software functional unit is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device) or a Processor (Processor) to execute some steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: various media capable of storing program codes, such as a usb disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk, or an optical disk.
The above description is only for the purpose of illustrating the preferred embodiments of the present invention and is not to be construed as limiting the invention, and any modifications, equivalents, improvements and the like made within the spirit and principle of the present invention should be included in the scope of the present invention.
Claims (15)
1. An application debugging method, comprising:
acquiring an application debugging request sent by a first terminal;
judging whether an interface called by the debugging method of the application debugging request exists in a software development kit of the first terminal or not;
responding to that the software development kit of the first terminal does not have the interface, and acquiring interface debugging information of the debugging method;
sending the interface debugging information to a second terminal so that the second terminal can call the debugging method in the second terminal based on the interface debugging information and determine a debugging result;
and receiving and displaying the debugging result.
2. The application debugging method according to claim 1,
the first terminal is a PC terminal, the second terminal is a mobile terminal, and the software development kit is a software development kit running on the mobile terminal.
3. The application debugging method of claim 2, wherein the obtaining interface debugging information of the debugging method comprises:
acquiring interface debugging information of the debugging method through an engine bridging layer of a mobile terminal application in the first terminal; or
And acquiring interface debugging information of the debugging method through a hook function, wherein the hook function replaces the debugging method of the application debugging request, and is used for acquiring the interface debugging information and obtaining the debugging result after being called.
4. The application debugging method according to claim 2,
the interface debugging information includes: the software development kit comprises a name of a method related to the software development kit, a name of parameters used by the method related to the software development kit, the number of the parameters, the type of the parameters and the values of the parameters.
5. The application debugging method according to any one of claims 2 to 4, wherein the sending the interface debugging information to the second terminal includes:
serializing the interface debugging information and sending the interface debugging information after the serialization processing through a communication agent module applied to a mobile terminal in the first terminal;
the receiving and displaying the debugging result comprises:
receiving the debugging result and performing deserialization processing on the debugging result through the communication agent module;
and sending the debugging result after the deserialization processing to an engine bridging layer of the mobile terminal application in the first terminal, so that the mobile terminal application obtains and displays the debugging result after the deserialization processing.
6. The application debugging method of claim 1, further comprising:
in response to that the software development kit of the first terminal does not have the interface, stopping the current debugging process while acquiring the interface debugging information of the debugging method;
after receiving the debugging result, the method further comprises:
and continuing the current debugging process based on the debugging result.
7. An application debugging method, comprising:
acquiring interface debugging information, wherein the interface debugging information is interface debugging information of a debugging method of an application debugging request sent by a first terminal;
calling the debugging method in the second terminal based on the interface debugging information and a software development kit of the second terminal, and determining a debugging result, wherein the software development kit of the second terminal has an interface called by the debugging method of the application debugging request;
and sending the debugging result.
8. The application debugging method according to claim 7,
the first terminal is a PC terminal, the second terminal is a mobile terminal, and the software development kit is a software development kit running on the mobile terminal.
9. The application debugging method of claim 8, wherein the obtaining interface debugging information comprises:
receiving the interface debugging information and performing deserialization processing on the interface debugging information through a communication agent module of the second terminal;
the sending the debugging result comprises:
and carrying out serialization processing on the debugging result and sending the debugging result after the serialization processing through the communication agent module.
10. The application debugging method of claim 8,
the interface debugging information includes: the software development kit comprises a name of a method related to the software development kit, a name of parameters used by the method related to the software development kit, the number of the parameters, the type of the parameters and the values of the parameters.
11. The application debugging method according to any one of claims 8 to 10, wherein the sending the debugging result comprises:
transmitting the debugging result to the first terminal based on a transmission mode indicated by a software development kit of the second terminal, wherein,
the sending mode indicated by the software development kit of the second terminal comprises a synchronous mode or an asynchronous mode.
12. An application debugging apparatus, comprising:
the first acquisition unit is used for acquiring an application debugging request sent by a first terminal;
the judging unit is used for judging whether an interface called by the debugging method of the application debugging request exists in a software development kit of the first terminal;
the second acquisition unit is used for responding to the situation that the software development kit of the first terminal does not have the interface, and acquiring the interface debugging information of the debugging method;
the sending unit is used for sending the interface debugging information to a second terminal so that the second terminal can call the debugging method in the second terminal based on the interface debugging information and determine a debugging result;
and the receiving unit is used for receiving and displaying the debugging result.
13. An application debugging apparatus, comprising:
the device comprises an acquisition unit, a processing unit and a processing unit, wherein the acquisition unit is used for acquiring interface debugging information, and the interface debugging information is interface debugging information of a debugging method of an application debugging request sent by a first terminal;
the debugging unit is used for calling the debugging method in the second terminal and determining a debugging result based on the interface debugging information and a software development kit of the second terminal, wherein the software development kit of the second terminal has an interface called by the debugging method of the application debugging request;
and the sending unit is used for sending the debugging result.
14. An electronic device, comprising: at least one processor; and a memory communicatively coupled to the at least one processor;
wherein the memory stores instructions executable by the at least one processor, the instructions being arranged to perform the method of any of the preceding claims 1 to 11.
15. A computer-readable storage medium having stored thereon computer-executable instructions for performing the method flow of any of claims 1-11.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110289363.1A CN112882950B (en) | 2021-03-18 | 2021-03-18 | Application debugging method and device, electronic equipment and computer readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110289363.1A CN112882950B (en) | 2021-03-18 | 2021-03-18 | Application debugging method and device, electronic equipment and computer readable storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112882950A true CN112882950A (en) | 2021-06-01 |
| CN112882950B CN112882950B (en) | 2023-07-25 |
Family
ID=76042686
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110289363.1A Active CN112882950B (en) | 2021-03-18 | 2021-03-18 | Application debugging method and device, electronic equipment and computer readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112882950B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115543853A (en) * | 2022-11-23 | 2022-12-30 | 北京蔚领时代科技有限公司 | Mobile terminal native SDK debugging method and system |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102075389A (en) * | 2011-01-27 | 2011-05-25 | 大唐移动通信设备有限公司 | Debugging method and equipment |
| US9471466B1 (en) * | 2015-05-28 | 2016-10-18 | Sap Se | End-to-end in-browser web-application debugging |
| CN110502418A (en) * | 2018-05-17 | 2019-11-26 | 长沙博为软件技术股份有限公司 | A method of realizing remote debugging |
| CN111078530A (en) * | 2019-11-22 | 2020-04-28 | 北京奇艺世纪科技有限公司 | Application program debugging method and system, electronic equipment and computer readable storage medium |
| CN111831538A (en) * | 2019-04-18 | 2020-10-27 | 腾讯科技（深圳）有限公司 | Debugging method, device and storage medium |
-
2021
- 2021-03-18 CN CN202110289363.1A patent/CN112882950B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102075389A (en) * | 2011-01-27 | 2011-05-25 | 大唐移动通信设备有限公司 | Debugging method and equipment |
| US9471466B1 (en) * | 2015-05-28 | 2016-10-18 | Sap Se | End-to-end in-browser web-application debugging |
| CN110502418A (en) * | 2018-05-17 | 2019-11-26 | 长沙博为软件技术股份有限公司 | A method of realizing remote debugging |
| CN111831538A (en) * | 2019-04-18 | 2020-10-27 | 腾讯科技（深圳）有限公司 | Debugging method, device and storage medium |
| CN111078530A (en) * | 2019-11-22 | 2020-04-28 | 北京奇艺世纪科技有限公司 | Application program debugging method and system, electronic equipment and computer readable storage medium |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115543853A (en) * | 2022-11-23 | 2022-12-30 | 北京蔚领时代科技有限公司 | Mobile terminal native SDK debugging method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112882950B (en) | 2023-07-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN108563567B (en) | Automated testing method, apparatus, device and computer readable storage medium | |
| US11845451B2 (en) | Automobile diagnostic method, apparatus, device and system, and diagnostic connection device | |
| US20120151446A1 (en) | Automatic reconnection of debugger to a reactivated application | |
| CN102967815B (en) | Chip testing method, automated testing equipment and system | |
| CN114880977A (en) | Software and hardware joint simulation system, method, device, equipment and storage medium | |
| CN110167192B (en) | Bluetooth connection management method and device, electronic equipment and non-transient storage medium | |
| CN111330280A (en) | Data processing method and device in game, storage medium and electronic equipment | |
| CN112882950A (en) | Application debugging method and device, electronic equipment and computer readable storage medium | |
| CN110990116B (en) | Method, device and system for transmitting data between intelligent network card and virtual machine | |
| CN113849356B (en) | Equipment testing method and device, electronic equipment and storage medium | |
| CN106681714A (en) | Method and device for setting program environments and electronic equipment | |
| CN103209255B (en) | Mobile terminal network games system | |
| CN116974636B (en) | Multi-path interconnection system and bus interface initialization method and device thereof | |
| CN115656788B (en) | Chip testing system, method, equipment and storage medium | |
| CN106713446A (en) | Relocation method and device, server and mobile terminal | |
| CN107645430B (en) | Data processing method, system and related equipment | |
| CN114567571B (en) | Performance test method, device, electronic equipment and computer readable storage medium | |
| CN113407044B (en) | Method, device, equipment and storage medium for simulating terminal handle input | |
| CN115952561A (en) | Data processing method, device, equipment and medium applied to rail transit system | |
| CN114217927A (en) | Thread calling method and device, computer equipment and storage medium | |
| CN113849267A (en) | Virtual display method, system, terminal and storage medium for display card | |
| CN114091909A (en) | Collaborative development method, system, device and electronic equipment | |
| CN113704032A (en) | Embedded heterogeneous multi-core processor architecture parallel debugging system and method | |
| CN111209086A (en) | Bare metal virtualization implementation method based on autonomous platform | |
| CN114168498B (en) | Broken line maintaining method, device, equipment and computer storage medium |
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 | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: 100041 B-0035, 2 floor, 3 building, 30 Shixing street, Shijingshan District, Beijing. Applicant after: Tiktok vision (Beijing) Co.,Ltd. Address before: 100041 B-0035, 2 floor, 3 building, 30 Shixing street, Shijingshan District, Beijing. Applicant before: BEIJING BYTEDANCE NETWORK TECHNOLOGY Co.,Ltd. Address after: 100041 B-0035, 2 floor, 3 building, 30 Shixing street, Shijingshan District, Beijing. Applicant after: Douyin Vision Co.,Ltd. Address before: 100041 B-0035, 2 floor, 3 building, 30 Shixing street, Shijingshan District, Beijing. Applicant before: Tiktok vision (Beijing) Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |