WO2020210994A1

WO2020210994A1 - Quick application installation package debugging method and apparatus, and electronic device and storage medium

Info

Publication number: WO2020210994A1
Application number: PCT/CN2019/082947
Authority: WO
Inventors: 郭子亮
Original assignee: 深圳市欢太科技有限公司; Oppo广东移动通信有限公司
Priority date: 2019-04-16
Filing date: 2019-04-16
Publication date: 2020-10-22
Also published as: CN113330427B; CN113330427A

Abstract

A quick application installation package debugging method and apparatus, and an electronic device and a storage medium. The quick application installation package debugging method, applied to a quick application installation package debugging apparatus, comprises: obtaining a quick application installation package from a specified address (S110); unpacking the quick application installation package to obtain an unpacked resource file (S120); and invoking a quick application development tool hap-toolkit to debug the unpacked resource file (S130). According to the method, any quick application installation package can be debugged, and because before the quick application development tool is dynamically invoked, the quick application installation package to be debugged is unpacked to obtain the unpacked resource file, thus the problem that the quick application development tool hap-toolkit can only directly debug the source code of the quick application installation package is solved.

Description

Quick application installation package debugging method, device, electronic equipment and storage medium

Technical field

This application relates to the field of computer technology, and more specifically, to a fast application installation package debugging method, device, electronic equipment, and storage medium.

Background technique

Quick App (Quick App) is an application that does not need to be downloaded and is search-and-use. Quick application programs usually correspond to a quick application installation package, and there is still a lack of debugging methods for the quick application installation package.

Summary of the invention

In view of the above problems, this application proposes a quick application installation package debugging method, device, electronic equipment, and storage medium to improve the above problems.

In the first aspect, this application provides a quick application installation package debugging method, which is applied to a quick application installation package debugging device, and the method includes: obtaining the quick application installation package from a designated address; Package to obtain the unpacked resource file; call the fast application development tool hap-toolkit to debug the unpacked resource file.

In a second aspect, the present application provides a quick application installation package debugging device, the device includes: an installation package acquisition unit for obtaining the quick application installation package from a designated address; and an unpacking unit for checking the quick application The installation package is unpacked to obtain the unpacked resource file; the debugging unit is used to call the fast application development tool hap-toolkit to debug the unpacked resource file.

In a third aspect, this application provides an electronic device, including one or more processors and a memory; one or more programs are stored in the memory and configured to be executed by the one or more processors Implement the above method.

In a fourth aspect, the present application provides a computer-readable storage medium in which program code is stored, wherein the above-mentioned method is executed when the program code is run by a processor.

The present application provides a quick application installation package debugging method, device, electronic device, and storage medium. After obtaining the quick application installation package from a designated address, the quick application installation package is unpacked to obtain the unpacked resource file , And then call the fast application development tool hap-toolkit to debug the unpacked resource files, so as to realize that any packaged fast application installation package can be debugged, and because the fast application development tool is dynamically invoked before , The quick application installation package to be debugged has been learned about the package, and the resource files after the understanding of the package have been obtained. At the same time, the problem that the quick application development tool can only directly debug the source code of the quick application installation package is improved, and the quick application installation package is improved Versatility of debugging.

Description of the drawings

In order to more clearly describe the technical solutions in the embodiments of the present application, the following will briefly introduce the drawings needed in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

FIG. 1 shows a schematic diagram of the architecture of a fast application proposed in an embodiment of the present application;

FIG. 2 shows a flowchart of a method for debugging a quick application installation package according to an embodiment of the present application;

FIG. 3 shows a schematic diagram of a browser interface for inputting a server address for debugging in a method for debugging a quick application installation package proposed in an embodiment of the present application;

FIG. 4 shows a flowchart of a method for debugging a quick application installation package according to another embodiment of the present application;

FIG. 5 shows a schematic structural diagram of a quick application installation package development project established in a quick application installation package debugging method proposed in another embodiment of the present application;

FIG. 6 shows a flowchart of a method for debugging a quick application installation package according to another embodiment of the present application;

FIG. 7 shows a flowchart of a fast application installation package debugging method proposed by another embodiment of the present application;

FIG. 8 shows a schematic diagram of a result file established in a method for debugging a quick application installation package proposed by another embodiment of the present application;

FIG. 9 shows a structural block diagram of a fast application installation package debugging device proposed by an embodiment of the present application;

FIG. 10 shows a structural block diagram of a device for debugging a quick application installation package according to another embodiment of the present application;

FIG. 11 shows a structural block diagram of a fast application installation package debugging device proposed by another embodiment of the present application;

FIG. 12 shows a structural block diagram of a quick application installation package debugging device proposed by another embodiment of the present application;

FIG. 13 shows a structural block diagram of an electronic device for executing the method for debugging a quick application installation package according to an embodiment of the present application in real time of the present application;

FIG. 14 shows a storage unit used to store or carry the program code for implementing the method for debugging a quick application installation package according to an embodiment of the present application in real time.

detailed description

The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, not all the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative work fall within the protection scope of this application.

With the development of mobile Internet technology, mobile terminal developers expect to implement the same functions as the aforementioned clients through fast applications, so as to improve the development efficiency of smart home functions and at the same time save the storage space of the mobile terminal.

Among them, the fast application is a new application form based on the hardware platform of the terminal device. It does not need to be installed, it is click-to-use, and it has the original application experience (performance, system integration, interaction, etc.). As shown in Figure 4, the structure diagram of the fast application engine, the front-end design of fast application draws on and integrates the design ideas of mainstream front-end frameworks (Vue, React, etc.): build applications in a componentized way, with data binding as the core The MVVM design mode uses V-DOM to improve performance, while choosing a concise and clear Vue-like template.

In the development process of Quick App, related development methods are all based on hap-toolkit. Hap-toolkit is a developer tool for Quick App. It helps developers to complete the development work through command line tools, mainly including Create template projects, upgrade projects, compile and debug functions.

However, the inventor found in the research that hap-toolkit, as a quick application development tool, can smoothly complete the development and debugging process of the source code of the quick application, but hap-toolkit does not have the packaged quick application installation package (rpk) The unpacking function, which can only directly debug the source code of the fast application, but the debugging work of the current fast application installation package is more complicated and diverse, so the developer or later operation and maintenance personnel need to perform the packaged fast application In the case of debugging or code modification of the installation package, it is necessary to retrieve or search the original source code again, which will cause great inconvenience to the code for developers or later operation and maintenance personnel.

Therefore, the inventor proposes that the implementation in the application can be debugged for any packaged quick application installation package, and because before calling the quick application development tool, the quick application installation package to be debugged has been checked to obtain the understanding package The latter resource files, and at the same time, improve the problem that the quick application development tool can only directly debug the source code of the quick application installation package, and improve the versatility of the quick application installation package debugging method, device, and electronic equipment And storage media.

The embodiments of the present application will be described in detail below in conjunction with the drawings.

Please refer to FIG. 2, a quick application installation package debugging method provided by an embodiment of the present application is applied to a quick application installation package debugging device, and the method includes:

Step S110: Obtain the quick application installation package from the specified address.

It is understandable that the quick application installation package to be debugged later will be stored in a certain device first, where the quick application installation package can be stored locally or on other devices in the network. Regardless of where the quick application installation package is stored, there will be a corresponding storage address. Among them, the corresponding storage address of the quick application installation package stored locally may include the storage path, and the corresponding storage address of the quick application installation package stored on other devices in the network will include the network address and storage path of the storage device . For example, for the quick app installation package stored locally, the corresponding storage address may be D:\quickapp\a.rpk. The corresponding storage address of the quick app installation package stored on other devices in the network can be 192.168.1.3\quickapp\a.rpk.

Then in this way, the debugger can input the address and the name of the quick application installation package in the designated address input area, and then when the quick application installation package debugging device obtains the address input by the user and the name of the quick application installation package, Take the obtained address as the designated address, and then obtain the quick application installation package corresponding to the name entered by the user from the designated address. For example, if the user input information obtained by the quick app installation package debugging device is D:\quickapp\b.rpk, then the quick app installation package debugging device will use D:\quickapp\ as the specified address, and then go to the D drive Find the quick app installation package b.rpk in the quickapp folder.

Step S120: Unpack the quick application installation package to obtain the unpacked resource file.

Step S130: Call the quick application development tool hap-toolkit to debug the unpacked resource file.

Among them, it should be noted that, in this embodiment, the quick application development tool hap-toolkit exists as a component of the quick application installation package debugging device, so the quick application installation package debugging device is calling the quick application development tool hap-toolkit In the process, it can be called based on how the components call each other. It is understandable that if the development language of the quick application installation package debugging device itself is not available, the way it performs component calls will be adaptable differently.

For example, if the quick application installation package debugging device is developed based on Python, as a way, the quick application installation package debugging device can call the quick application development tool hap-toolkit based on the os.system() function during operation, as In another way, the quick application installation package debugging device can also call the quick application development tool hap-toolkit based on the ShellExecute function.

As a way, in this embodiment, the unpacked resource file can be loaded into the quick application installation package debugging device, and then the quick application development tool hap-toolkit can be called to load the quick application installation package debugging device. Debug the unpacked resource file. As another way, you can also load the unpacked resource file into the quick application development tool hap-toolkit, and then trigger the quick application development tool hap-toolkit to perform the unpacked resource file loading into itself debugging.

Among them, for the way of loading the unpacked resource file into the quick application installation package debugging device in this embodiment, it should be noted that the quick application development tool hap-toolkit runs in the form of a functional module, and In this mode, the quick application development tool hap-toolkit is a functional module in the quick application installation package debugging device in this embodiment, so that the resource files loaded into the quick application installation package in this embodiment can be performed debugging.

For the method of loading the unpacked resource file into the quick application development tool hap-toolkit, it should be noted that in this way, the quick application development tool hap-toolkit can be used for the quick application installation package debugging device A functional module can also be a stand-alone application. When the fast application development tool hap-toolkit is an independently running application, the fast application installation package debugging device can send the storage location of the unpacked resource file to the fast application development tool hap- based on inter-process communication. toolkit, so that the fast application development tool hap-toolkit can load the unpacked resource files for subsequent debugging.

It should be noted that during the debugging process shown in Figure 3, the quick application installation package debugging device opens the debugging port locally, at this time, use the local browser to open http://localhost:8000, and simultaneously debug with the quick application installation package The electronic device where the device is connected is connected to the Android mobile phone under the same WiFi to start the quick application debugger. Then you can start debugging based on the method suggested in the quick application debugger. For example, if you choose scan code debugging, you can start debugging by scanning the QR code in the local browser page.

This application provides a quick application installation package debugging method. After obtaining the quick application installation package from a designated address, unpack the quick application installation package to obtain the unpacked resource file, and then call the quick application development tool hap -toolkit, to debug the unpacked resource files, so as to realize that any packaged quick app installation package can be debugged, and because the quick app installation package to be debugged has been debugged before calling the quick app development tool Understand the package, get the resource files after the package, and at the same time improve the problem that the quick application development tool can only directly debug the source code of the quick application installation package, and improve the generality of the quick application installation package debugging.

Referring to FIG. 4, a quick application installation package debugging method provided by an embodiment of the present application is applied to a quick application installation package debugging device, and the method includes:

Step S210: Obtain the quick application installation package from the specified address.

Step S220: Unpack the quick application installation package to obtain the unpacked resource file.

Step S230: Create a new quick application installation package development project, in which the resource files of the initial quick application installation package are configured.

As a way, the quick application installation package debugging device executes the hap init<ProjectName> command to create a new quick application installation package development project. Among them, "ProjectName" represents the name of the new project. The development project for the new quick application installation package includes the resource files shown in Figure 5, which mainly include the two resource folders sign and src, and the package.json file, where sign mainly stores the resource files required for signature , Src mainly includes index.ux file for recording source code and manifest.json file for recording configuration information. It is understandable that the new quick application installation package development project includes the various resource files shown in FIG. 5, but the content of the resource files included in the new quick application installation package development project is the default initial content. For example, the initial content in the index.ux file that records the source code can be "hello quickapp", or the content in the resource files of some initial quick app installation packages is empty.

Step S240: Replace the resource file of the initial quick application installation package with the unpacked resource file.

It is understandable that the aforementioned unpacked resource file will also include the various files shown in the figure, but the content in the unpacked resource file is the content edited by the developer. Then, after the unpacked resource file is obtained, the unpacked resource file can be used to replace the resource file of the initial quick application installation package. For example, in this step, the index.ux file in the unpacked resource file will be used to replace the index.ux file in the new quick application installation package development project, and the manifest.json file in the unpacked resource file will be used. Replace the manifest.json file in the new quick application installation package development project.

Step S250: Call the quick application development tool hap-toolkit to debug the new quick application installation package development project, so as to realize the debugging of the unpacked resource file.

Step S260: Invoke the quick application development tool hap-toolkit to sign the debugged resource file based on the specified signature and package it into a quick application installation package, wherein the specified signature and the quick application obtained from the specified address The original signature of the installation package is different.

It should be noted that the signature of the quick application installation package is used to protect the integrity of the file. The principle of use of the signature is: When compiling and packaging, first perform SHA256 operation on each file in the rpk package, and then use the signed private key and certificate The result of SHA256 is signed, and the final result is packaged in the quick application installation package in a file named /META-INF/CERT. When the quick application installation package is running, it will check the value of the signed SHA256 to see if it is equal to the SHA256 value of the current file. If it is not equal, the verification will fail, which proves that the file in the quick application installation package has been modified. In turn, the quick application installation package that fails the verification cannot be run normally.

So if in the process of debugging the unpacked resource file, if the code of the resource file is modified, in order to avoid the above problem, the quick application installation package debugging device will perform the debugging based on the specified signature. The resource file is re-signed. Among them, the quick application installation package debugging device can find the /META-INF/CERT file with the signature result stored in the unpacking folder, and delete it, and then use other legal signature private keys and certificates in the packaging process ( As a way, this embodiment can directly use the debug signature provided by the official, eliminating the need to generate another signature) Invoke the fast application development tool hap-toolkit to sign and package the unpacked file directory, and generate a new /CERT file.

It should be noted that the aforementioned file names are only exemplary, and as long as the correspondingly stored contents are the same, they fall within the protection scope of this application.

In the packaging process, as a way, call the quick application development tool hap-toolkit to create an empty packaging project, update the packaging configuration information of the packaging project to the information of the resource file after debugging, and obtain the updated packaging The configuration information is used to sign the debugged resource file based on the updated packaging configuration information and the designated signature and package it into a quick application installation package.

Among them, the optional packaging project is webpack packaging project. Among them, webpack can be regarded as a module packaging machine: what it does is to analyze the project structure, find JavaScript modules and other extended languages (Scss, TypeScript, etc.) that cannot be directly run by browsers, and convert and package them into suitable ones The format is for browser use.

As a way, after the debugged resource file is signed and packaged as a quick application installation package, the debugged resource file in the new quick application installation package development project can be replaced with all The resource files of the initial quick application installation package are described.

It should be noted that, in addition to directly establishing a new quick application installation package development project in the quick application installation package debugging device, you can also obtain the quick application installation package from the designated address, unpack the quick application installation package, and obtain After unpacking the resource files, directly call the quick application development tool hap-toolkit, and create a new quick application installation package development project in the called quick application development tool hap-toolkit, and for the new quick application development tool hap-toolkit The quick application installation package development project is the same as the aforementioned initial resource file included in the establishment of the new quick application installation package development project in the quick application installation package debugging device.

In this embodiment, the content of step S210 to step S250 in this embodiment can be executed again for the quick application installation package packaged after debugging, so as to realize the code modification in the debugging process, you can immediately Verify whether the modified code can be executed successfully. Among them, as a way, the quick application installation package debugging device may provide a command line input interface so that the user can input corresponding instructions therein to trigger the quick application installation package debugging device to perform corresponding steps in this embodiment. .

For example, when the "-d" command is used to indicate the start of debugging, when it is detected that the command "-d" is input on the command line input interface, the step S210 to the step S260 will be executed. It is also possible to execute only step S210 to step S250 when the command "-d" input is detected, and then when the command “-f” input is further detected in the command line input interface, execute the steps for the debugged resource file The content of S260. In addition, the user can also input two or more commands at the same time in the command line input interface. For example, after the quick application installation package debugging device has executed step S250 in response to the command "-d", the user can input the command "-d" at the same time. And "-f", so that after the quick application installation package debugging device is packaged, it can start to execute the content of step 210 to step S250 on the newly packaged quick application installation package.

This application provides a quick application installation package debugging method. After obtaining the quick application installation package from a specified address, unpack the quick application installation package to obtain the unpacked resource file, and then create a new one including the initial quick application installation package. The quick application installation package development project of the resource file of the application installation package, replace the resource file of the initial quick application installation package with the unpacked resource file, and then call the quick application development tool hap-toolkit to debug the new project , So as to realize that any packaged quick application installation package can be debugged, and because before calling the quick application development tool, the quick application installation package to be debugged has been learned about the package, and the resource file after understanding the package is obtained, and at the same time The problem that the quick application development tool can only directly debug the source code of the quick application installation package is improved, and the generality of the quick application installation package debugging is improved. Furthermore, because the debugging of the quick application installation package development project is still carried out, there is no need to modify the debugging process of hap-toolkit, thereby improving the generality of the debugging process. In addition, it also implements dynamic configuration and invocation of the called hap-toolkit during the debugging process.

Please refer to FIG. 6, a quick application installation package debugging method provided by an embodiment of the present application is applied to a quick application installation package debugging device, and the method includes:

Step S310: If the file input instruction is recognized, the type of the input file is recognized.

In the embodiment of the present application, after the file input instruction is recognized, the type of the file can be recognized by recognizing the suffix of the input file. For example, if the suffix of the file is recognized as rpk, then the input file can be recognized as a file of the quick application installation package type. If the suffix of the file is recognized as js, then the type of the input file can be recognized For the js file type.

Step S320: If it is recognized that the type of the input file is a quick application installation package, obtain the quick application installation package from the designated address.

Step S330: Unpack the quick application installation package to obtain the unpacked resource file.

Step S340: Call the quick application development tool hap-toolkit to debug the unpacked resource file.

Step S350: If it is recognized that the type of the input file is a JavaScript file, typeset the code included in the JavaScript file according to a specified format for easy viewing.

As a method, the code deleted during the packaging process of the JavaScript file is restored; the code in the restored JavaScript file is typeset according to a specified format.

It should be noted that, if a JavaScript file is detected in the unpacked resource file, the code included in the JavaScript file in the unpacked resource file can also be typeset according to a specified format. In order to facilitate the quick application installation package debugging device to distinguish the format adjusted JavaScript files, the quick application installation package debugging device will re-create a JavaScript file to store the content of the format adjusted JavaScript file, and the included content has been A JavaScript file that has been formatted will be named a different name from a JavaScript file whose content has not been formatted for distinction.

This application provides a quick application installation package debugging method, which realizes that any packaged quick application installation package can be debugged, and because the quick application installation package to be debugged has been checked before calling the quick application development tool , Get the resource files after understanding the package, and at the same time improve the problem that the quick application development tool can only directly debug the source code of the quick application installation package, and improve the generality of the quick application installation package debugging. Furthermore, in this embodiment, after recognizing that the read file is a JavaScript file, the JavaScript file can also be formatted to improve the user's reading experience.

Please refer to FIG. 7, a quick application installation package debugging method provided by an embodiment of the present application is applied to a quick application installation package debugging device, and the method includes:

Step S410: Obtain the quick application installation package from the specified address.

Step S420: Unpack the quick application installation package to obtain the unpacked resource file.

Step S430: Invoke the fast application development tool hap-toolkit to debug the unpacked resource file.

Step S440: Obtain the configuration file in the unpacked resource file, where the code in the configuration file includes the function interface called by the quick application installation package obtained from the specified address.

It should be noted that, in order to make the developed fast application have certain functions, certain pre-configured functional interfaces will be called during the development process. However, in the process of calling the functional interfaces, it may be caused by errors in the calling code. The entire quick application installation package has a debugging error, so in order to facilitate the debugging personnel to find the source of the error in time, the unpacked resource can be obtained when an error occurs in the debugging process of the unpacked resource file is identified The configuration file in the file. In the embodiment of the present application, there are multiple ways to detect whether an error occurs during the debugging process.

As a way, whether errors occur during debugging can be detected based on image recognition. Specifically, when an exception occurs when the code is running, the interface of the fast application development tool hap-toolkit will pop up a dialog box, and the Dangkuai application installation package debugging device and the fast application development tool hap-toolkit are two independent operations. In the case of applications, the quick application installation package debugging device cannot directly obtain specific error information, then the quick application installation package debugging device can detect the quick application in real time based on image recognition after the quick application development tool hap-toolkit starts debugging On the interface of the development tool hap-toolkit, when a dialog box pops up is detected, an error can be determined during the debugging process. In this way, even if the quick application installation package debugging device cannot obtain the debugging information output by the quick application development tool hap-toolkit, it can also detect whether an error occurs during the debugging process.

In addition, as another way, in the way that the quick application installation package debugging device and the quick application development tool hap-toolkit are called based on the component method, the quick application installation package debugging device can be directly used in the quick application development tool hap-toolkit. After the toolkit starts debugging, the interface of the debugging output information is detected. When the specified text output is detected, it can be determined that an error occurred during the debugging process.

Step S450: Read the function interface scanning requirement information.

Step S460: Scan the configuration file based on the function interface scanning requirement information to obtain the function interface invoked by the quick application installation package obtained from the specified address.

The configuration file is a manifest.json file.

Step S470: Output the obtained functional interface to the result file.

As a way, the scanning requirement information includes the target type and output style to be scanned; the step of scanning the configuration file based on the function interface scanning requirement information includes: scanning the functions included in the configuration file The type in the interface that matches the target type;

The step of outputting the obtained functional interface to the result file includes: outputting the obtained functional interface to the result file according to the output style.

For example, as shown in Figure 8, it is a style of output content of a result file. In the result file shown in FIG. 8, the description of the interface function is correspondingly configured for each function interface found. For example, "<vendor account service>", "<Alipay payment>" and "<network request>" etc.

It should be noted that the quick application installation package debugging device in this embodiment can also identify how it calls the quick application development tool hap-toolkit, and determine the display position of the final result file according to the identified calling method. In order to facilitate debugging personnel to view. Optionally, if the quick application installation package debugging device recognizes that the quick application development tool hap-toolkit is called based on inter-process communication, the result file can be displayed in the quick application development tool hap-toolkit in the form of a pop-up box. toolkit. It is understandable that the pop-up box displaying the result file here is popped up by the quick application installation package debugging device, but the display position coincides with the quick application development tool hap-toolkit. In this way, even if the quick application installation package debugging device cannot obtain the debugging information output by the quick application development tool hap-toolkit, it can display the function interface file in time for the user to refer to when debugging.

This application provides a quick application installation package debugging method, which realizes that any packaged quick application installation package can be debugged, and because the quick application installation package to be debugged has been checked before calling the quick application development tool , Get the resource files after understanding the package, and at the same time improve the problem that the quick application development tool can only directly debug the source code of the quick application installation package, and improve the generality of the quick application installation package debugging. Furthermore, in this embodiment, the configuration file in the resource file can be scanned, and then the function interface called in the decompressed quick application installation package can be output for the user to view.

Please refer to FIG. 9, a quick application installation package debugging device 500 provided by an embodiment of the present application, the device 500 includes:

The installation package obtaining unit 510 is configured to obtain a quick application installation package from a designated address.

The unpacking unit 520 is used to unpack the quick application installation package to obtain the unpacked resource file.

The debugging unit 530 is used to call the fast application development tool hap-toolkit to debug the unpacked resource file.

As shown in FIG. 10, the debugging unit 530 specifically includes:

The development project establishment subunit 531 is used to create a new quick application installation package development project, and the new quick application installation package development project is configured with resource files of the initial quick application installation package.

The information replacement subunit 532 is configured to replace the resource file of the initial quick application installation package with the unpacked resource file.

The debugging execution subunit 533 is used to call the quick application development tool hap-toolkit to debug the new quick application installation package development project, so as to realize the debugging of the unpacked resource file.

In addition, as a manner, the device 500 further includes:

The packaging unit 540 is configured to call the quick application development tool hap-toolkit to sign the debugged resource file based on the specified signature and package it into a quick application installation package, wherein the specified signature is the same as the address specified by the slave The original signature of the quick app installation package is different.

Optionally, the packaging unit 540 is specifically used to call the fast application development tool hap-toolkit to create an empty packaging project; update the packaging configuration information of the packaging project to the information of the resource file after debugging, to obtain The updated packaging configuration information; based on the updated packaging configuration information and the designated signature, the debugged resource file is signed and packaged into a quick application installation package. Wherein, the packaging project is a webpack packaging project.

In this manner, the information replacement subunit 532 is also used to replace the debugged resource file in the new quick application installation package development project with the resource file of the initial quick application installation package.

As shown in FIG. 11, the device 500 further includes:

The file format identification unit 550 is used for identifying the type of the input file if the file input instruction is recognized. In this manner, if the file format recognition unit 550 recognizes that the type of the input file is a quick application installation package, the installation package acquisition unit 510 executes the acquisition of the quick application installation package from the specified address.

The file layout processing unit 560 is configured to, if the file format recognition unit 550 recognizes that the type of the input file is a JavaScript file, typeset the code included in the JavaScript file according to a specified format for easy viewing.

As a way, the file typesetting processing unit 560 is specifically configured to restore the code deleted during the packaging of the JavaScript file; and typeset the code in the restored JavaScript file according to a specified format.

In addition, as shown in FIG. 12, the device 500 further includes:

The interface processing unit 570 is configured to read the function interface scanning requirement information; scan the configuration file based on the function interface scanning requirement information to obtain the function interface called by the quick application installation package obtained from the specified address; The obtained function interface is output to the result file.

As a way, the scanning requirement information includes the target type and output style to be scanned. In this manner, the interface processing unit 570 is specifically configured to scan the configuration file based on the function interface scanning requirement information, including: scanning the function interface included in the configuration file and the target type Matching type; the step of outputting the obtained functional interface to the result file includes: outputting the obtained functional interface to the result file according to the output style.

As a way, the interface processing unit 570 is configured to obtain the configuration file in the unpacked resource file when an error occurs in the debugging process of the unpacked resource file.

Optionally, the interface processing unit 570 is specifically configured to determine that an error has occurred during debugging of the unpacked resource file when it recognizes that the designated error image prompt information appears in the debugging interface based on the image recognition method.

It should be noted that the device embodiment in this application and the foregoing method embodiment correspond to each other, and the specific principles in the device embodiment can be referred to the content in the foregoing method embodiment, which is not repeated here.

Hereinafter, an electronic device provided by the present application will be described with reference to FIG. 13.

Referring to FIG. 13, based on the foregoing quick application installation package debugging method and device, an embodiment of the present application also provides another electronic device 100 that can execute the foregoing quick application installation package debugging method. The electronic device 100 includes one or more (only one is shown in the figure) a processor 102, a memory 104, and a network module 106 coupled to each other. Wherein, the memory 104 stores a program that can execute the content in the foregoing embodiment, and the processor 102 can execute the program stored in the memory 104.

The processor 102 may include one or more processing cores. The processor 102 uses various interfaces and lines to connect various parts of the entire electronic device 100, and executes by running or executing instructions, programs, code sets, or instruction sets stored in the memory 104, and calling data stored in the memory 104. Various functions and processing data of the electronic device 100. Optionally, the processor 102 may use at least one of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). A kind of hardware form to realize. The processor 102 may integrate one or a combination of a central processing unit (CPU), a graphics processing unit (GPU), a modem, and the like. Among them, the CPU mainly processes the operating system, user interface, and application programs; the GPU is used for rendering and drawing of display content; the modem is used for processing wireless communication. It can be understood that the above-mentioned modem may not be integrated into the processor 102, but may be implemented by a communication chip alone.

The memory 104 may include random access memory (RAM) or read-only memory (Read-Only Memory). The memory 104 may be used to store instructions, programs, codes, code sets or instruction sets. The memory 104 may include a storage program area and a storage data area, where the storage program area may store instructions for implementing the operating system and instructions for implementing at least one function (such as touch function, sound playback function, image playback function, etc.) , Instructions for implementing the following method embodiments, etc. The data storage area can also store data (such as phone book, audio and video data, chat record data) created by the terminal 100 during use.

The network module 106 may include a radio frequency unit for receiving and transmitting electromagnetic waves, and realizes mutual conversion between electromagnetic waves and electrical signals, so as to communicate with a communication network or other equipment, such as communicating with an audio playback device. Furthermore, the network module 106 may also include a network adapter (network card), so as to directly connect to the router or the gateway Ethernet through a wired manner, and then perform data interaction with the network.

Wherein, the network module 106 may include various existing circuit elements for performing these functions, such as antennas, radio frequency transceivers, digital signal processors, encryption/decryption chips, subscriber identity module (SIM) cards, memory and many more. The network module 106 can communicate with various networks such as the Internet, an intranet, and a wireless network, or communicate with other devices through a wireless network. The aforementioned wireless network may include a cellular telephone network, a wireless local area network, or a metropolitan area network. For example, the network module 106 can exchange information with the base station.

Please refer to FIG. 14, which shows a structural block diagram of a computer-readable storage medium provided by an embodiment of the present application. The computer-readable medium 800 stores program code, and the program code can be invoked by a processor to execute the method described in the foregoing method embodiment.

The computer-readable storage medium 800 may be an electronic memory such as flash memory, EEPROM (Electrically Erasable Programmable Read Only Memory), EPROM, hard disk, or ROM. Optionally, the computer-readable storage medium 800 includes a non-transitory computer-readable storage medium. The computer-readable storage medium 800 has a storage space for the program code 810 for executing any method steps in the above-mentioned methods. These program codes can be read out from or written into one or more computer program products. The program code 810 may be compressed in a suitable form, for example.

In summary, the present application provides a quick application installation package debugging method, device, electronic equipment, and storage medium. After obtaining the quick application installation package from a designated address, the quick application installation package is unpacked to obtain the solution. After the packaged resource file, then call the fast application development tool hap-toolkit to debug the unpacked resource file, so as to realize that any packaged fast application installation package can be debugged, and because the fast application installation package is called Before applying the development tools, the quick application installation package to be debugged has been learned about the package, and the resource files after understanding the package have been obtained. At the same time, the problem that the quick application development tool can only directly debug the source code of the quick application installation package has been improved. The versatility of fast application installation package debugging.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the application, not to limit them; although the application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that: The technical solutions recorded in the foregoing embodiments are modified, or some of the technical features are equivalently replaced; these modifications or replacements do not drive the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present application.

Claims

A quick application installation package debugging method, characterized in that it is applied to a quick application installation package debugging device, and the method includes:

Obtain the quick application installation package from the specified address;

Unpack the quick application installation package to obtain the unpacked resource file;

Call the fast application development tool hap-toolkit to debug the unpacked resource file.
The method according to claim 1, wherein the step of invoking the fast application development tool hap-toolkit to debug the unpacked resource file comprises:

A new quick application installation package development project, where the resource files of the initial quick application installation package are configured in the new quick application installation package development project;

Replacing the resource file of the initial quick application installation package with the unpacked resource file;

Call the quick application development tool hap-toolkit to debug the new quick application installation package development project, so as to realize the debugging of the unpacked resource file.
The method according to claim 2, wherein before the step of creating a new quick application installation package development project, the method further comprises:

Check whether there is an empty quick application installation package development project;

If it is detected that there is no empty quick application installation package development project, execute the new quick application installation package development project;

If it is detected that there is an empty quick application installation package development project, the empty quick application installation package development project is regarded as a new quick application installation package development project.
The method according to any one of claims 1 to 3, wherein after the step of invoking the quick application development tool hap-toolkit to debug the unpacked resource file, the method further comprises:

Call the quick application development tool hap-toolkit to sign the debugged resource file based on the specified signature and package it into a quick application installation package, wherein the specified signature is the same as the one obtained from the specified address of the quick application installation package The original signature is different.
The method according to claim 4, wherein the step of invoking the quick application development tool hap-toolkit to sign the debugged resource file based on a specified signature and packaging it into a quick application installation package comprises:

Call the quick application development tool hap-toolkit to create an empty packaging project;

Updating the packaging configuration information of the packaging project to the information of the resource file after debugging to obtain the updated packaging configuration information;

Sign the debugged resource file based on the updated packaging configuration information and the designated signature and package it into a quick application installation package.
The method according to claim 5, wherein the packaging project is a webpack packaging project.
The method according to claim 5 or 6, characterized in that after the step of signing the debugged resource file based on the updated packaging configuration information and the specified signature and packaging it as a quick application installation package Also includes:

Replace the debugged resource file in the new quick application installation package development project with the resource file of the initial quick application installation package.
The method according to any one of claims 1-7, wherein before the step of obtaining the quick application installation package from the specified address, the method further comprises:

If the file input command is recognized, recognize the type of the input file;

If it is recognized that the type of the input file is a quick application installation package, execute the acquisition of the quick application installation package from the specified address.
The method according to claim 8, wherein the method further comprises:

If it is recognized that the type of the input file is a JavaScript file, the code included in the JavaScript file is typeset according to a specified format for easy viewing.
The method according to claim 9, wherein the step of typesetting the code included in the JavaScript file according to a specified format comprises:

Restore the code deleted during the packaging of the JavaScript file;

The code in the JavaScript file after the restoration is typeset according to the specified format.
The method according to any one of claims 1-10, wherein the method further comprises:

Obtaining a configuration file in the unpacked resource file, where the code in the configuration file includes the functional interface called by the quick application installation package obtained from the specified address;

Read function interface scanning demand information;

Scan the configuration file based on the function interface scanning requirement information to obtain the function interface called by the quick application installation package obtained from the specified address;

Output the obtained functional interface to the result file.
The method according to claim 11, wherein the scanning requirement information includes the target type and output style to be scanned;

The step of scanning the configuration file based on the function interface scanning requirement information includes:

Scanning the type of the functional interface included in the configuration file that matches the target type;

The step of outputting the obtained functional interface to the result file includes:

Output the obtained functional interface to the result file according to the output style.
The method according to claim 12, wherein the configuration file is a manifest.json file.
The method according to any one of claims 11-13, wherein the step of obtaining the configuration file in the unpacked resource file comprises:

When it is recognized that an error occurs in the debugging process of the unpacked resource file, acquiring the configuration file in the unpacked resource file.
The method according to claim 14, wherein when it is recognized that an error has occurred during the debugging of the unpacked resource file, the step of obtaining the configuration file in the unpacked resource file comprises :

Based on the image recognition method, when the designated error message appears in the debugging interface, it is determined that an error occurred during the debugging of the unpacked resource file, and the configuration file in the unpacked resource file is obtained .
A quick application installation package debugging device, characterized in that the device includes:

The installation package obtaining unit is used to obtain the quick application installation package from the specified address;

The unpacking unit is used to unpack the quick application installation package to obtain the unpacked resource file;

The debugging unit is used to call the fast application development tool hap-toolkit to debug the unpacked resource file.
The device according to claim 16, wherein the debugging unit specifically comprises:

The development project establishment subunit is used to create a new quick application installation package development project, where the resource files of the initial quick application installation package are configured in the new quick application installation package development project;

An information replacement subunit for replacing the resource file of the initial quick application installation package with the unpacked resource file;

The debugging execution subunit is used to call the quick application development tool hap-toolkit to debug the new quick application installation package development project, so as to realize the debugging of the unpacked resource file.
The device according to claim 16 or 17, wherein the device further comprises:

The packaging unit is used to call the quick application development tool hap-toolkit to sign the debugged resource file based on the specified signature and package it into a quick application installation package, wherein the specified signature is the same as the one obtained from the specified address The original signature of the quick app installation package is different.
An electronic device, characterized in that it includes one or more processors and a memory;

One or more programs are stored in the memory and configured to be executed by the one or more processors to implement the method of any one of claims 1-15.
A computer-readable storage medium, wherein a program code is stored in the computer-readable storage medium, wherein the method according to any one of claims 1-15 is executed when the program code is run by a processor.