CN112882950B - 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
- CN112882950B CN112882950B CN202110289363.1A CN202110289363A CN112882950B CN 112882950 B CN112882950 B CN 112882950B CN 202110289363 A CN202110289363 A CN 202110289363A CN 112882950 B CN112882950 B CN 112882950B
- 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.)
- Active
Links
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 a debugging method of the application debugging request exists in a software development kit of the first terminal or not; acquiring interface debugging information of the debugging method in response to the fact that the software development kit of the first terminal does not have the interface; the interface debugging information is sent 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 a debugging result is determined; 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
[ field of technology ]
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 Art ]
With the development of mobile terminal technology, mobile phone applications for mobile terminal such as games, social contact, financial management, shopping and the like are born. The application manufacturer firstly needs to debug the mobile terminal mobile phone application on the PC terminal, and after the debugging is finished, the mobile terminal mobile phone application is exported and applied to the mobile terminal or the mobile terminal simulator, and the mobile terminal or the mobile terminal simulator checks and accepts the mobile terminal application.
However, the mobile phone application of the mobile terminal needs to use the SDK (Software Development Kit ) dedicated to the mobile terminal, but the SDK dedicated to the mobile terminal cannot be automatically debugged at the PC terminal, which requires the application manufacturer to manually debug or manually export the SDK dedicated to the mobile terminal or the mobile terminal simulator and then debug. In this way, the debugging difficulty is high, the consumed time is long, and the debugging efficiency is seriously affected.
Therefore, how to improve the debugging efficiency is a technical problem to be solved in the present day.
[ 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 a debugging method of the application debugging request exists in a software development kit of the first terminal or not; acquiring interface debugging information of the debugging method in response to the fact that the software development kit of the first terminal does not have the interface; the interface debugging information is sent 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 a debugging result is determined; and receiving and displaying the debugging result.
In the foregoing 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 obtaining interface debug information of the debug 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 obtaining 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 obtaining the interface debugging information and obtaining the debugging result after being called.
In the foregoing embodiment of the present invention, optionally, the interface debug information includes: the method comprises a method name related to the software development kit, a parameter name, a parameter number, a parameter type and a parameter value used by the method related to the software development kit.
In the foregoing embodiment of the present invention, optionally, the sending the interface debug information to the second terminal includes: the interface debugging information is subjected to serialization processing and the interface debugging information after the serialization processing is sent through a communication proxy module applied by a mobile terminal in the first terminal; the step of receiving and displaying the debugging result comprises the following steps: receiving the debugging result and performing deserialization processing on the debugging result through the communication proxy module; and sending the anti-serialization debugging result to an engine bridging layer of the mobile terminal application in the first terminal, so that the mobile terminal application obtains and displays the anti-serialization debugging result.
In the above embodiment of the present invention, optionally, the method further includes: responding to the fact that the software development kit of the first terminal does not have the interface, and suspending the current debugging process while acquiring interface debugging information of the debugging method; after receiving the debug result, further comprising: 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 is provided with an interface called by the debugging method of the application debugging request; and sending the debugging result.
In the foregoing 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 obtaining interface debug information includes: receiving the interface debugging information and performing deserialization processing on the interface debugging information through a communication proxy module of the second terminal; the sending the debug result includes: and carrying out serialization processing on the debugging result and sending the debugging result after the serialization processing through the communication proxy module.
In the foregoing embodiment of the present invention, optionally, the interface debug information includes: the method comprises a method name related to the software development kit, a parameter name, a parameter number, a parameter type and a parameter value used by the method related to the software development kit.
In the foregoing embodiment of the present invention, optionally, the sending the debug result includes: and transmitting the debugging result to the first terminal based on a transmission mode indicated by the software development kit of the second terminal, wherein the transmission 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 the first terminal; the judging unit is used for judging whether the software development kit of the first terminal is provided with an interface called by the debugging method of the application debugging request or not; the second obtaining unit is used for obtaining interface debugging information of the debugging method in response to the fact that the software development kit of the first terminal does not have the interface; 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 foregoing 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 obtaining 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 obtaining the interface debugging information and obtaining the debugging result after being called.
In the foregoing embodiment of the present invention, optionally, the interface debug information includes: the method comprises a method name related to the software development kit, a parameter name, a parameter number, a parameter type and a parameter value used by the method related to the software development kit.
In the above embodiment of the present invention, optionally, the transmitting unit is configured to: the interface debugging information is subjected to serialization processing and the interface debugging information after the serialization processing is sent through a communication proxy module applied by 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 proxy module; and sending the anti-serialization debugging result to an engine bridging layer of the mobile terminal application in the first terminal, so that the mobile terminal application obtains and displays the anti-serialization debugging result.
In the above embodiment of the present invention, optionally, the method further includes: a process control unit, configured to suspend a current debugging process while obtaining interface debugging information of the debugging method in response to the software development kit of the first terminal not having the interface, and configured to, 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 system comprises an acquisition unit, a first terminal and a second terminal, wherein the acquisition unit is used for acquiring interface debugging information, wherein the interface debugging information is the interface debugging information of a debugging method of an application debugging request sent by the first terminal; the debugging unit is used for 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 is provided with an interface called by the debugging method for applying the debugging request; and the sending unit is used for sending the debugging result.
In the foregoing 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 proxy module of the second terminal; the transmitting 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 proxy module.
In the foregoing embodiment of the present invention, optionally, the interface debug information includes: the method comprises a method name related to the software development kit, a parameter name, a parameter number, a parameter type and a parameter value used by the method related to the software development kit.
In the above embodiment of the present invention, optionally, the transmitting unit is configured to: and transmitting the debugging result to the first terminal based on a transmission mode indicated by the software development kit of the second terminal, wherein the transmission 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, embodiments of the present invention provide a computer-readable storage medium storing computer-executable instructions for performing the method of any one of the first and/or second aspects above.
According to the technical scheme, aiming at the problem of low application debugging efficiency in the related technology, when the special software development kit of the mobile terminal needs to be debugged at the 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, the 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 that are needed 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 that other drawings can be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 illustrates a flow chart of an application debugging method according to one embodiment of the invention;
FIG. 2 shows a flow chart of an application debugging method according to another embodiment of the invention;
FIG. 3 shows a flow chart of an application debugging method according to yet another embodiment of the present invention;
FIG. 4 shows a schematic diagram of application debugging according to one embodiment of the invention;
FIG. 5 shows a schematic diagram of application debugging according to another embodiment of the invention;
FIG. 6 illustrates a timing diagram for application debugging according to one embodiment of the invention;
FIG. 7 shows a block diagram of an application debugging device according to one embodiment of the invention;
FIG. 8 shows a block diagram of an application debugging device 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 ] of the invention
For a better understanding of the technical solution of the present invention, the following detailed description of the embodiments of the present invention refers to the accompanying drawings.
It should be understood that the described embodiments are merely some, but not all, embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the 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 this application 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 1
FIG. 1 illustrates a flow chart 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:
step 102, an application debugging request sent by a first terminal is obtained.
Step 104, judging whether the software development kit of the first terminal has an interface called by the debugging method of the application debugging request.
The first terminal is a PC end, the software development tool kit is a software development tool kit running on the mobile end, and the software development tool kit running on the mobile end cannot be automatically debugged on the PC end. When the mobile terminal application is debugged at the PC terminal, the PC terminal can send out an application debugging request, and after the application debugging request is obtained, whether the content of the debugging requested by the application debugging request relates to the software development kit (hereinafter referred to as the software development kit) running at the mobile terminal is judged in order to timely identify the problem that the software development kit possibly cannot be automatically debugged at the PC terminal.
Specifically, the software development kit cannot automatically debug on the PC side, that is, the debugging method and interface related to the software development kit, which are described in the application debug request sent by the first terminal, cannot be provided by the PC side. 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 judging result is that the content of the application debugging request is required to be debugged, the debugging method and the corresponding interface can be directly called, otherwise, if the judging result is that the content of the application debugging request is not required to be debugged, the first terminal does not have the capability of debugging the software development kit, namely the content of the application debugging request can not be directly debugged at the first terminal, and at the moment, an effective debugging mode can be provided for the first terminal as shown in the following steps.
And step 106, obtaining interface debugging information of the debugging method in response to the fact that the software development kit of the first terminal does not have the interface.
Step 108, the interface debugging information is sent 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 a debugging result is determined.
And step 110, receiving and displaying the debugging result.
It is known that the main body of the technical scheme is the first terminal itself, the debugging device connected with the first terminal or the debugging device built in the first terminal (hereinafter, the main body of the technical scheme is collectively referred to as the first terminal), so that interface debugging information can be sent to the second 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 method name related to the software development kit, a parameter name, a parameter number, a parameter type, a parameter value and the like of the method related to the software development kit.
Example two
Fig. 2 shows a flow chart 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:
step 202, an application debugging request sent by a first terminal is obtained.
Step 204, determining whether the software development kit of the first terminal has an interface called by the debugging method of the application debugging request.
Step 206, obtaining interface debugging information of the debugging method through an engine bridging layer of a mobile terminal application in the first terminal in response to the fact that the software development kit of the first terminal does not have the interface; or obtaining 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 obtaining the interface debugging information and obtaining the debugging result after being called.
In one possible design, the method for obtaining interface debug information of the debug method includes: and acquiring interface debugging information of the debugging method through an engine bridging layer of the mobile terminal application in the first terminal. Specifically, an engine Bridge layer (Unity Bridge) of the mobile terminal application in the first terminal can intercept interface debugging information of the software development kit through the plug-in, and can rapidly acquire the interface debugging information.
In another possible design, the interface debugging information of the debugging method is obtained through a hook function, wherein the hook function replaces the debugging method of the application debugging request, and is used for obtaining the interface debugging information and obtaining the debugging result after being called. Specifically, the hook function replaces the debugging method for applying the debugging request, so that the hook function can realize the function of the debugging method and simultaneously can also have the function of acquiring interface debugging information for the debugging method. Therefore, the interface debugging information can be quickly obtained in a hook mode.
Step 208, performing serialization processing on the interface debugging information and sending the interface debugging information after the serialization processing through a communication proxy module of the mobile terminal application in the first terminal.
Optionally, the communication Proxy module is Proxy (Proxy class), where Proxy works in an application layer and is used to backup information to be remotely transmitted, and perform other operations on the backup information that the first terminal does not want or cannot perform. Specifically, proxy can backup interface debugging information of the software development kit which cannot be debugged by the first terminal, and send the backup to the second terminal after the backup is subjected to serialization processing. .
In addition, the Proxy joint debugging is carried out on the interface debugging information 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 improved, the safety of the first terminal can be improved, and the illegal attack on the interface of the special software development kit of the mobile terminal can be prevented from directly acting on the first terminal.
Step 210, receiving the debug result and performing deserialization processing on the debug result through the communication proxy module.
Step 212, sending the anti-serialization processed debug result to the engine bridging layer of the mobile terminal application in the first terminal, so that the mobile terminal application obtains and displays the anti-serialization processed debug result.
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 are not required to be transmitted between the two, but only interface debugging information of the software development kit running on the mobile terminal in the first terminal is transmitted to the second terminal. In the calling process, the software development kit method is equivalent to a framework, and the interface debugging information is equivalent to specific setting information of the framework, 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. Finally, the first terminal executes the debugging function on the interface debugging information through the second terminal, and a debugging result is obtained.
In this process, in order to improve the information security level, when the first terminal sends the interface debugging information outwards through the communication proxy module applied by the mobile terminal in the first terminal, the interface debugging information can be subjected to serialization processing, and finally the interface debugging information after the serialization processing is sent. Similarly, when the second terminal feeds back the debug result to the first terminal, the debug result is also subjected to serialization processing to ensure safety, specifically, the second terminal can call an interface which is self-owned and corresponds to the interface debug information through a GBridge (bridging layer) to obtain the debug result, and then the debug result is subjected to serialization processing through the GBridge and returned to the first terminal.
Based on the above, it can be known that the interface debug information is intercepted at the engine bridge layer of the mobile terminal application, and then after receiving the debug result after the deserialization processing, the debug result can be fed back to the engine bridge layer of the mobile terminal 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 in 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 perform deserialization processing on the debug result through the communication proxy module. And finally, the first terminal provides the anti-serialization debugging result for 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 anti-serialization debugging result, and the automatic debugging of the software development kit is completed.
According to the technical scheme, when the special software development kit of 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 software development kit special for 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 chart of an application debugging method according to a further embodiment of the invention.
As shown in fig. 3, an application debugging method according to still another embodiment of the present invention is used for a second terminal, and the flow thereof includes:
Step 302, obtaining 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.
Step 304, 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 is provided with an interface called by the debugging method for applying the debugging request.
And step 306, sending the debugging result.
The second terminal is a mobile terminal or a mobile terminal simulator and has the capability of debugging the software development kit running on the mobile terminal, so that the second terminal can directly call a corresponding debugging method through interface debugging information of the debugging method based on 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 to realize the automatic debugging of the first terminal as a PC terminal on the software development kit running on the mobile terminal.
Specifically, step 302 includes: receiving the interface debugging information and performing deserialization processing on the interface debugging information through a communication proxy 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 proxy module.
The Proxy in the first terminal needs to interact with the communication Proxy module of the second terminal to realize joint debugging of the interface debugging information, so that the second terminal is configured with the communication Proxy module, and the second terminal debugs the interface debugging information after receiving the interface debugging information through the communication Proxy module of the second terminal.
Optionally, the communication Proxy module of the second terminal is MagicBox, magicBox as a docking object of Proxy, which has a relay function, and meanwhile, has a capability of reducing signal interference, and can accurately and effectively obtain the interface debugging information received from the first terminal for the second terminal.
When the first terminal sends out interface debugging information through Proxy of mobile terminal application in the first terminal, the interface debugging information can be subjected to serialization processing, and finally the interface debugging information after the serialization processing is sent out. Similarly, when the second terminal feeds back the debug result to the first terminal, the debug result is also subjected to serialization processing to ensure safety, specifically, the second terminal can call an interface which is self-owned and corresponds to the interface debug information through a GBridge (bridging layer) to obtain the debug result, and then the debug result is subjected to serialization processing through the GBridge and returned to the first terminal.
Therefore, the debugging of the software development kit special for 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 side debugs the game application of the mobile side, the requirement of debugging the mobile side software development kit of the game application of the mobile side is met. At this time, the Proxy module in the game debugging PC (i.e., the first terminal) may intercept interface debugging information of the mobile terminal software development kit of the game application of the mobile terminal at the engine bridge layer of the game debugging PC, 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.
And the MagicBox module of the local/remote mobile terminal performs deserialization processing on the received information to obtain interface debugging information. Further, the local/remote mobile terminal calls a mobile terminal software development kit interface of the local/remote mobile terminal to execute debugging based on the interface debugging information, and a debugging result is obtained. The MagicBox module of the local/remote mobile terminal performs serialization processing on the debugging result and sends the debugging result after 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 through server forwarding. In one possible design, the remote mobile terminal can provide a control path through which an external developer 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, so that the controllability of the mobile terminal software development kit debugging process is increased, the mobile terminal software development kit debugging work of the game debugging PC terminal is facilitated, the overall difficulty of game debugging is reduced, and the overall efficiency of game debugging is improved.
As shown in fig. 5, when the game debugging PC side debugs the game application of the mobile side, the requirement of debugging the mobile side software development kit of the game application of the mobile side is met. At this time, the Proxy module in the game debugging PC (i.e., the first terminal) may intercept interface debugging information of the mobile terminal software development kit of the game application of the mobile terminal at the engine bridge layer of the game debugging PC, and send the interface debugging information to the MagicBox module of the mobile terminal simulator (i.e., the second terminal) after performing serialization processing.
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 mobile terminal software development kit interface of the mobile terminal simulator to execute debugging based on the interface debugging information, and a debugging result is obtained. The MagicBox module of the mobile terminal simulator performs serialization processing on the debugging result, and sends the debugging result after serialization processing to the Proxy module of the game debugging PC terminal.
On the basis of any technical scheme, finally, the Proxy module at the game debugging PC end performs deserialization processing on the received content to obtain a debugging result, and returns the debugging result to the engine bridging layer for intercepting interface debugging information. Thus, for the engine bridging layer, the debugging result of the interface debugging information is automatically obtained based on the interface debugging information.
It should be added that the technical solution of the present application may include: responding to the fact that the software development kit of the first terminal does not have the interface, and suspending the current debugging process while acquiring interface debugging information of the debugging method; after receiving the debug result, further comprising: and continuing the current debugging process based on the debugging result.
Specifically, for the first terminal, when the current debugging process for debugging the mobile terminal application encounters a mobile terminal special software development kit interface which cannot be debugged by the first terminal, the current debugging process is suspended while the debugging work is transferred to an external second terminal. Finally, when the debugging result from the second terminal is received, restarting the current debugging process. Therefore, the current debugging process is equivalent to obtaining the debugging result based on the interface debugging information directly based on the interface debugging information of the mobile terminal software development kit to be debugged, thereby avoiding the negative influence of the application debugging process caused by the incapability of debugging the interface of the mobile terminal software development kit and being beneficial to improving the reliability of the debugging result.
On the basis of any technical scheme, referring to fig. 6, in a game debugging PC end environment, a PC end is connected with 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/universal and the like through a plug-in, and sends the interface debugging information to Proxy at the PC end, the Proxy sequences the interface debugging information and forwards the sequenced information to MagicBox in the mobile end environment through a Server. After the MagicBox calls GBridge to process the information from Proxy, native Module is called to obtain a debugging result, and the debugging result is synchronously returned or asynchronously returned to the PC side.
Specifically, the second terminal may send the debug 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 the above, the synchronization mode refers to sending the interface debugging information of the mobile terminal software development kit to be debugged to the second terminal by the first terminal, and returning the debugging result to the first terminal by the second terminal as a complete process, so that the process integrity can be ensured, and the error probability of the process can be 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, wherein between the two steps, the second terminal needs a certain time to carry out debugging operation, and if the two steps are continuously used as a process, the debugging time can cause the application debugging of the first terminal to be blocked. Therefore, the asynchronous mode 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 two processes, so that the smoothness of application debugging of the first terminal is improved.
Fig. 7 shows a block diagram of an application debugging device according to an embodiment of the invention.
As shown in fig. 7, an application debugging device 700 according to an embodiment of the present invention includes: a first obtaining unit 702, configured to obtain an application debug request sent by a first terminal; a judging unit 704, configured to judge whether an interface called by the debugging method of the application debugging request is provided in the software development kit of the first terminal; a second obtaining unit 706, configured to obtain interface debug information of the debug method in response to the software development kit of the first terminal not having the interface; a sending unit 708, configured to send the interface debug information to a second terminal, so that the second terminal invokes the debug method in the second terminal based on the interface debug information, and determines a debug result; and a receiving unit 710, configured to receive and display the debug result.
In the foregoing 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 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 obtaining 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 obtaining the interface debugging information and obtaining the debugging result after being called.
In the foregoing embodiment of the present invention, optionally, the interface debug information includes: the method comprises a method name related to the software development kit, a parameter name, a parameter number, a parameter type and a parameter value used by the method related to the software development kit.
In the above embodiment of the present invention, optionally, the sending unit 708 is configured to: the interface debugging information is subjected to serialization processing and the interface debugging information after the serialization processing is sent through a communication proxy module applied by 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 proxy module; and sending the anti-serialization debugging result to an engine bridging layer of the mobile terminal application in the first terminal, so that the mobile terminal application obtains and displays the anti-serialization debugging result.
In the above embodiment of the present invention, optionally, the method further includes: a process control unit, configured to suspend a current debugging process while obtaining interface debugging information of the debugging method in response to the software development kit of the first terminal not having the interface, and configured to, after receiving the debugging result, further include: and continuing the current debugging process based on the debugging result.
The application debugging device 700 uses the scheme described in any of the above embodiments, so that all the above technical effects are achieved, and will not be described herein.
Fig. 8 shows a block diagram of an application debugging device according to another embodiment of the present invention.
As shown in fig. 8, an application debugging device 800 according to another embodiment of the present invention includes: an obtaining unit 802, configured to obtain interface debug information, where the interface debug information is interface debug information of a debug method of an application debug request sent by a first terminal; a debugging unit 804, configured to invoke 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 invoked by the debugging method of the application debugging request; a sending unit 806, configured to send the debug result.
In the foregoing 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 unit 802 is configured to: receiving the interface debugging information and performing deserialization processing on the interface debugging information through a communication proxy 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 proxy module.
In the foregoing embodiment of the present invention, optionally, the interface debug information includes: the method comprises a method name related to the software development kit, a parameter name, a parameter number, a parameter type and a parameter value used by the method related to the software development kit.
In the above embodiment of the present invention, optionally, the sending unit 806 is configured to: and transmitting the debugging result to the first terminal based on a transmission mode indicated by the software development kit of the second terminal, wherein the transmission mode indicated by the software development kit of the second terminal comprises a synchronous mode or an asynchronous mode.
The application debugging device 800 uses the solution described in any of the above embodiments, so that all the above technical effects are achieved, and will not be described in detail herein.
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 an 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 arrangements described in any of the embodiments above. Therefore, the electronic device 900 has the same technical effects as those of any of the above embodiments, and will not be described herein.
The electronic device of the 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 functionality and are aimed at providing voice, data communication. Such terminals include smart phones (e.g., iPhone), multimedia phones, functional phones, and low-end phones, among others.
(2) Ultra mobile personal computer equipment, which belongs to the category of personal computers, has the functions of calculation and processing and generally has the characteristic of mobile internet surfing. Such terminals include PDA, MID and UMPC devices, etc., such as iPad.
(3) Portable entertainment devices such devices can display and play multimedia content. Such devices include audio, video players (e.g., iPod), palm game consoles, electronic books, and smart toys and portable car navigation devices.
(4) The server is similar to a general computer architecture in that the server is provided with high-reliability services, and therefore, the server has high requirements on processing capacity, stability, reliability, safety, expandability, manageability and the like.
(5) Other electronic devices with data interaction function.
In addition, an embodiment of the present invention provides a computer readable storage medium storing computer executable instructions for performing the method flow described in any one of the above embodiments.
The technical scheme of the invention is described in detail by combining the drawings, 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 an external debugging main body for debugging when the software development kit is required to be debugged, and then the debugging result provided by the external debugging main body is directly obtained. Therefore, the 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 relationship describing the association of the associated objects, meaning that there may be three relationships, e.g., a and/or B, may represent: a exists alone, A and B exist together, and B exists alone. In addition, the character "/" herein generally indicates that the front and rear associated objects are an "or" relationship.
It should be understood that although the terms first, second, etc. may be used in embodiments of the present invention to describe a terminal, these terminals should not be limited by these terms. These terms are only used to distinguish terminals from one 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.
Depending on the context, the word "if" as used herein may be interpreted as "at … …" or "at … …" or "in response to a determination" or "in response to detection". Similarly, the phrase "if determined" or "if detected (stated condition or event)" may be interpreted as "when determined" or "in response to determination" or "when detected (stated condition or event)" or "in response to detection (stated condition or event), depending on the context.
In the several embodiments provided by the present invention, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the elements is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple elements or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.
In addition, each functional unit in the embodiments of the present invention may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit. The integrated units may be implemented in hardware or in hardware plus software functional units.
The integrated units implemented in the form of software functional units described above 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, etc.) or a Processor (Processor) to perform part of the steps of the methods according to the embodiments of the present invention. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a random access Memory (Random Access Memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.
The foregoing description of the preferred embodiments of the invention is not intended to be limiting, but rather to enable any modification, equivalent replacement, improvement or the like to be made within the spirit and principles of the invention.
Claims (14)
1. An application debugging method, comprising:
acquiring an application debugging request sent by a first terminal; the first terminal is a local terminal;
judging whether an interface called by a debugging method of the application debugging request exists in a software development kit of the first terminal or not;
responding to the fact that the software development kit of the first terminal does not have the interface, and acquiring interface debugging information of the debugging method through an engine bridging layer of a mobile terminal application in the first terminal;
the interface debugging information is sent 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 a debugging result is determined; the second terminal is a remote terminal;
and receiving and displaying the debugging result.
2. The application debugging method of claim 1, wherein the application debugging method comprises the steps of,
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 application debugging method comprises the steps of,
the interface debugging information comprises: the method comprises a method name related to the software development kit, a parameter name, a parameter number, a parameter type and a parameter value used by the method related to the software development kit.
4. An application debugging method according to any one of claims 2 to 3, wherein said sending the interface debugging information to the second terminal comprises:
the interface debugging information is subjected to serialization processing and the interface debugging information after the serialization processing is sent through a communication proxy module applied by a mobile terminal in the first terminal;
the step of receiving and displaying the debugging result comprises the following steps:
receiving the debugging result and performing deserialization processing on the debugging result through the communication proxy module;
and sending the anti-serialization debugging result to an engine bridging layer of the mobile terminal application in the first terminal, so that the mobile terminal application obtains and displays the anti-serialization debugging result.
5. The application debugging method of claim 1, further comprising:
responding to the fact that the software development kit of the first terminal does not have the interface, and suspending the current debugging process while acquiring interface debugging information of the debugging method;
After receiving the debug result, further comprising:
and continuing the current debugging process based on the debugging result.
6. 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; the interface debugging information is obtained through an engine bridging layer of the mobile terminal application in the first terminal; the first terminal is a local 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 is provided with an interface called by the debugging method of the application debugging request; the second terminal is a remote terminal;
and sending the debugging result.
7. The application debugging method of claim 6, wherein the step of executing the application debugging process comprises,
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.
8. The application debugging method of claim 7, wherein the obtaining interface debugging information comprises:
Receiving the interface debugging information and performing deserialization processing on the interface debugging information through a communication proxy module of the second terminal;
the sending the debug result includes:
and carrying out serialization processing on the debugging result and sending the debugging result after the serialization processing through the communication proxy module.
9. The application debugging method of claim 7, wherein the step of executing the application debugging process comprises,
the interface debugging information comprises: the method comprises a method name related to the software development kit, a parameter name, a parameter number, a parameter type and a parameter value used by the method related to the software development kit.
10. The application debugging method according to any one of claims 7 to 9, wherein the sending the debugging result comprises:
transmitting the debug result to the first terminal based on a transmission 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.
11. An application debugging device, comprising:
the first acquisition unit is used for acquiring an application debugging request sent by the first terminal; the first terminal is a local terminal;
The judging unit is used for judging whether the software development kit of the first terminal is provided with an interface called by the debugging method of the application debugging request or not;
the second obtaining unit is used for obtaining interface debugging information of the debugging method through an engine bridging layer of the mobile terminal application in the first terminal in response to the fact that the software development kit of the first terminal does not have the interface;
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; the second terminal is a remote terminal;
and the receiving unit is used for receiving and displaying the debugging result.
12. An application debugging device, comprising:
the system comprises an acquisition unit, a first terminal and a second terminal, wherein the acquisition unit is used for acquiring interface debugging information, wherein the interface debugging information is the interface debugging information of a debugging method of an application debugging request sent by the first terminal; the interface debugging information is obtained through an engine bridging layer of the mobile terminal application in the first terminal; the first terminal is a local terminal;
the debugging unit is used for 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 is provided with an interface called by the debugging method for applying the debugging request; the second terminal is a remote terminal;
And the sending unit is used for sending the debugging result.
13. 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 10.
14. A computer readable storage medium having stored thereon computer executable instructions for performing the method flow of any one of claims 1 to 10.
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 CN112882950A (en) | 2021-06-01 |
| CN112882950B true 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) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115543853B (en) * | 2022-11-23 | 2023-03-17 | 北京蔚领时代科技有限公司 | 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 |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112882950A (en) | 2021-06-01 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110113407B (en) | Applet state synchronization method, apparatus and computer 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 | |
| CN107122224A (en) | A kind of data transmission method, virtual machine and host | |
| CN105468462A (en) | Inter-process communication authentication method and system as well as inter-application communication method and system | |
| CN112882950B (en) | Application debugging method and device, electronic equipment and computer readable storage medium | |
| CN111569417A (en) | Peripheral data transmission method and system for cloud games | |
| CN116701168A (en) | Peripheral interface testing method, device, equipment and storage medium | |
| CN113849356B (en) | Equipment testing method and device, electronic equipment and storage medium | |
| CN103209255B (en) | Mobile terminal network games system | |
| CN110290139B (en) | Message transmission method and device | |
| CN110162389B (en) | Application program starting method and device and intelligent interaction equipment | |
| EP3955645A1 (en) | Message transmission method and related device | |
| CN113407044B (en) | Method, device, equipment and storage medium for simulating terminal handle input | |
| CN115052003B (en) | Data synchronization method, related device and medium | |
| CN114173319B (en) | Method and device for realizing conversation across platforms, cloud platform server and storage medium | |
| CN110737900A (en) | Webpage function testing method and device, server and computer readable storage medium | |
| CN114217927A (en) | Thread calling method and device, computer equipment and storage medium | |
| CN111209086A (en) | Bare metal virtualization implementation method based on autonomous platform | |
| CN106982242A (en) | The method and device of many registration terminal synchronizing informations | |
| CN114168498B (en) | Broken line maintaining method, device, equipment and computer storage medium | |
| CN112891928B (en) | Data processing method, storage medium and electronic device | |
| CN115996410B (en) | Method, device, equipment and storage medium for testing wireless communication protocol stack | |
| CN113521738B (en) | Special effect generation method and device, computer readable storage medium and electronic equipment | |
| CN114385384B (en) | Application programming interface calling method and related 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 | ||
| 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 |