CN110851204B - Application starting method and device and application packaging method and device - Google Patents
Application starting method and device and application packaging method and device Download PDFInfo
- Publication number
- CN110851204B CN110851204B CN201911090243.8A CN201911090243A CN110851204B CN 110851204 B CN110851204 B CN 110851204B CN 201911090243 A CN201911090243 A CN 201911090243A CN 110851204 B CN110851204 B CN 110851204B
- Authority
- CN
- China
- Prior art keywords
- application
- file
- executable file
- resource file
- resource
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Stored Programmes (AREA)
Abstract
The disclosure relates to the technical field of computers, in particular to a method and a device for starting an application and a method and a device for packaging the application. According to the application starting method, the executable file and the resource file of the second application are built in the application program installation package of the first application, and the files are decompressed in the starting process of the first application, so that the executable file and the resource file of the first application are respectively replaced when the first application meets the replacement condition, and the running files loaded after the application is started are all files of the second application.
Description
Technical Field
The disclosure relates to the technical field of computers, in particular to a method and a device for starting an application and a method and a device for packaging the application.
Background
With the rapid development of internet technology, application iteration is more frequent. When an application that has been stably run is upgraded to a new version, various running errors and even Crash (Crash) may occur, which is a problem especially common in the test version application.
Currently, such problems are solved by pushing new updated versions or patches to the user, usually after discovering the bug. However, releasing a new version or patch requires the user to wait for a period of time and also consumes additional traffic, affecting the user experience and even causing user churn.
Disclosure of Invention
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the detailed description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.
In one aspect, the present disclosure provides a method for starting an application, the method including:
after the first application starts to be started, whether a second executable file and a second resource file are stored in the local directory is checked;
if not, decompressing the second executable file and the second resource file from the application program installation package of the first application to the local directory;
if yes, determining whether the first application meets a preset replacement condition;
if the first application meets the replacement condition, replacing the first executable file and the first resource file with the decompressed second executable file and the decompressed second resource file respectively to start a second application;
wherein the second application and the first application are different versions of the same application; the first executable file and the first resource file are files corresponding to the first application; the second executable file and the second resource file are corresponding files of the second application.
In yet another aspect, the present disclosure provides a method of application packaging, the method comprising:
acquiring a second executable file and a second resource file corresponding to a second application;
performing union operation on a first configuration file corresponding to the first application and a second configuration file corresponding to the second application to generate a third configuration file;
packaging the second executable file, the second resource file and the third configuration file into an application installation package corresponding to the first application;
the application program installation package comprises a first executable file corresponding to the first application, and the first executable file comprises a class representing the first application and a self-defined class; the second executable file includes a class representing a second application; the custom class is used for executing the method for starting the application and calling the class representing the first application or the class representing the second application.
In yet another aspect, the present disclosure provides an apparatus for application launching, the apparatus comprising:
the checking unit is used for checking whether the local directory stores a second executable file and a second resource file after the first application starts to be started;
a decompressing unit, configured to decompress, if the second executable file and the second resource file are not stored in the local directory, the second executable file and the second resource file from an application installation package of a first application to the local directory;
a replacement determining unit, configured to determine whether the first application satisfies a preset replacement condition if the second executable file and the second resource file are stored in the local directory;
a second starting unit, configured to replace the first executable file and the first resource file with the decompressed second executable file and the decompressed second resource file, respectively, to start a second application;
wherein the second application and the first application are different versions of the same application; the first executable file and the first resource file are files corresponding to the first application; the second executable file and the second resource file are corresponding files of the second application.
In yet another aspect, the present disclosure provides an apparatus for application packaging, the apparatus comprising:
the acquisition unit is used for acquiring a second executable file and a second resource file corresponding to a second application;
the merging unit is used for performing union operation on a first configuration file corresponding to the first application and a second configuration file corresponding to the second application to generate a third configuration file;
a packing unit, configured to pack the second executable file, the second resource file, and the third configuration file into an application installation package corresponding to the first application;
the application program installation package comprises a first executable file corresponding to the first application, and the first executable file comprises a class representing the first application and a self-defined class; the second executable file includes a class representing a second application; the self-defined class is used for executing the method for starting the application and calling the class representing the first application or the class representing the second application.
In yet another aspect, the present disclosure provides a terminal, including:
at least one memory and at least one processor;
wherein the memory is used for storing program codes, and the processor is used for calling the program codes stored in the memory to execute the method.
In another aspect, the present disclosure provides a non-transitory computer storage medium having stored thereon program code for performing the above-described method.
According to the method and the device, the executable file and the resource file of the second application are built in the first application, and the file is decompressed in the starting process of the first application, so that the executable file and the resource file of the first application are respectively replaced when the first application meets the replacement condition, the running files loaded after the application is started are all files of the second application, and the running performance of the second application is the same as that of the second application.
Drawings
The above and other features, advantages, and aspects of embodiments of the present disclosure will become more apparent by referring to the following detailed description when taken in conjunction with the accompanying drawings. Throughout the drawings, the same or similar reference numbers refer to the same or similar elements. It should be understood that the drawings are schematic and that elements and features are not necessarily drawn to scale.
Fig. 1 is a flowchart of an application startup method provided in an embodiment of the present disclosure;
fig. 2 is a flowchart of an application startup method according to another embodiment of the present disclosure;
fig. 3 is a flowchart of an application startup method according to another embodiment of the present disclosure;
fig. 4 is a flowchart of a method for packaging an application according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of an apparatus for application startup according to an embodiment of the present disclosure;
fig. 6 is a schematic structural diagram of an apparatus for starting an application according to another embodiment of the present disclosure;
fig. 7 is a schematic structural diagram of an apparatus for packaging an application according to an embodiment of the present disclosure;
fig. 8 is a schematic structural diagram of a terminal device for implementing an embodiment of the present disclosure.
Detailed Description
Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While certain embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure may be embodied in various forms and should not be construed as limited to the embodiments set forth herein, but rather are provided for a more complete and thorough understanding of the present disclosure. It should be understood that the drawings and embodiments of the disclosure are for illustration purposes only and are not intended to limit the scope of the disclosure.
It should be understood that the steps recited in the apparatus embodiments of the present disclosure may be performed in a different order and/or performed in parallel. Moreover, apparatus embodiments may include additional steps and/or omit performing the illustrated steps. The scope of the present disclosure is not limited in this respect.
The term "include" and variations thereof as used herein are open-ended, i.e., "including but not limited to". The term "based on" is "based, at least in part, on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". Relevant definitions for other terms will be given in the following description.
It should be noted that the terms "first", "second", and the like in the present disclosure are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
It is noted that references to "a" or "an" in this disclosure are intended to be illustrative rather than limiting, and that those skilled in the art will appreciate that references to "one or more" are intended to be exemplary and not limiting unless the context clearly indicates otherwise.
The names of messages or information exchanged between devices in the embodiments of the present disclosure are for illustrative purposes only, and are not intended to limit the scope of the messages or information.
Fig. 1 shows a flowchart of a method for starting an application according to an embodiment of the present disclosure, where the method 100 includes steps S101 to S105:
step S101: and after the first application starts to be started, checking whether a second executable file and a second resource file are stored in the local directory.
If the second executable file and the second resource file are not stored locally, executing step S102: and decompressing the second executable file and the second resource file from the application installation package of the first application to the local directory.
If the local directory stores the second executable file and the second resource file, step S103 is executed: it is determined whether the first application satisfies a preset replacement condition.
If the first application satisfies the replacement condition, step S104 is executed: and replacing the first executable file and the first resource file by the decompressed second executable file and the decompressed second resource file respectively to start the second application.
The second application and the first application are different versions of the same application, for example, the second application may be a last formal version of the first application; the first executable file and the first resource file are files corresponding to the first application; the second executable file and the second resource file are corresponding files of a second application. The executable file refers to a file including all operating instructions and operating data of the application program, such as a dex file of an android platform; resource files refer to resources in an application that are separate from the source code, such as images, audio files, and any content related to the visual presentation of the application. In the embodiment of the present disclosure, the local directory refers to a directory used for storing files locally at the terminal, and does not include a file directory included in the application installation package of the first application. According to the embodiment of the disclosure, the dex file and the resource file of the second application are pre-built in the application program installation package of the first application for subsequent replacement use.
Therefore, according to the embodiment of the disclosure, the executable file and the resource file of the second application are built in the application program installation package of the first application, and the files are decompressed in the process of starting the first application, so that the executable file and the resource file of the first application are respectively replaced when the first application meets the replacement condition, so that the running files loaded after the application is started are all files of the second application, and the running performance of the second application is the same as that of the second application.
Preferably, the second executable file and the second resource file are pre-compressed and stored in the assets directory of the application installation package of the first application, so as to be decompressed for use when the first application is started. The assets directory is a resource directory of the android platform, and files stored in the assets directory cannot be directly accessed by an application. Therefore, the second executable file and the second resource file are stored in the associations directory, and the influence on the normal operation of the first application can be avoided.
As shown in fig. 2, another embodiment of the present disclosure further provides a method 200, where the method 200 includes steps S201 to S207:
step S201: the first application is started.
Step S202: it is checked whether the local directory holds the second executable file and the second resource file.
If the second executable file and the second resource file are not stored locally, step S203 is executed: decompressing the second executable file and the second resource file under the assets directory of the application program installation package of the first application to the local directory, and executing step S105: the first application continues to be launched.
If the local directory stores the second executable file and the second resource file, step S204 is executed: it is determined whether the first application satisfies a preset replacement condition.
If the first application does not satisfy the replacement condition, step S205 is executed: the first application continues to be launched.
If the first application satisfies the replacement condition, step S206 is executed: and replacing the first executable file and the first resource file by the decompressed second executable file and second resource file respectively to start the second application.
Step S207: and calling the corresponding Applicaton class of the second application to run the code of the second application. The Application represents the class of the Application program, belongs to a system component in the Android system, and is a base class for maintaining the global state of the Application, and when the Application process is started, the Android system can create the Application class and call an onCreate () function of the class.
In the embodiment of the present disclosure, by calling the app class corresponding to the second application to run the code of the second application, the running performance of the code is the same as that of the second application, that is, the starting of the second application is implemented equivalently.
In some embodiments, step S204 further comprises: a1: determining whether the first application receives a replacement instruction sent by the server, or A2: determining whether the abnormal times of the first application exceed a preset threshold. If the first application receives a replacement instruction sent by the server or the abnormal times of the first application exceeds a preset threshold value, the first application can be determined to meet a preset replacement condition. In the embodiment of the disclosure, an application developer can actively send a replacement instruction to a client through a server according to the BUG feedback condition of an application, or the client determines whether to replace an application version according to the actual running condition of the application.
As shown in fig. 3, another embodiment of the present disclosure further provides a method 300, where the method 300 includes steps S301 to S308:
step S301: the first application is started.
Step S302: and checking whether the local directory stores a second dex file and a second resource file.
If the local directory does not store the second dex file and the second resource file, step S303 is executed: decompressing the second dex file and the second resource file under the assets directory of the application program installation package of the first application to the local directory, and executing step S305: the first application continues to be launched.
If the local directory stores the second dex file and the second resource file, step S304 is executed: and determining whether the abnormal times of the first application exceed a threshold value T according to the local cache data.
If the threshold T is not exceeded, step S305 is executed: the first application continues to be launched.
If the threshold value T is exceeded, step S306 is executed.
Step S306: the first executable file is replaced by the decompressed second dex file. Taking the replacement of the dex file under the android platform as an example, a class loader ClassLoader inherited to PathClassLoader can be customized, a path of loading the dex file by default is modified to be a local directory of the embodiment of the present disclosure, then a second dex file is read through the customized ClassLoader and is converted into an Element array, wherein the Element array is an encapsulation of the dex file, the Element array loaded in the first application is obtained through reflection, and then the original Element array is replaced by a new Element array through reflection, so that the replacement of the dex file is completed.
Step S307: and replacing the first resource file with the decompressed second resource file. Taking the Resource file replacement under the android platform as an example, first, a Resource manager ResourceManager is obtained, and then all configuration information (configuration) is obtained through the ResourceManager, where each configuration information has its corresponding Resource object. The Resources object describes the android Resource file, contains the AssetManager objects, adds the Resource of the first application to a new AssetManager by creating the new AssetManager, and finally replaces the original AssetManager in the Resources with the new AssetManager, thereby completing the replacement of the Resource file.
Step S308: and calling the corresponding Applicaton class of the second application to run the code of the second application.
In the step S305, if the first application is started and an exception occurs, the step S3051 is performed: and recording an exception in the local cache data and restarting the first application.
If the first application is started without exception, executing step S3052: the first boot is complete.
The local cache data refers to data cached in a local physical memory of the user terminal. In the embodiment of the present disclosure, when an exception occurs when the first application is started, the exception is recorded to the local cache data in step S3051, so that when the first application is started again, the number of times that the exception has occurred to the first application is determined by reading the local cache data in step S304. In this way, whether the first application meets the replacement condition at the moment can be judged, and if the abnormal times exceed the threshold value T, the first application is considered to meet the replacement condition.
Thus, in the embodiment of the present disclosure, when an exception occurs in the first application, the application is immediately restarted by recording the exception, and the above steps are repeated until the exception satisfies the replacement condition, so that the user is unaware of the start exception and the application version is replaced without being aware of the user.
In some embodiments, step S3051 may further include: and calling an exception capture interface to record exceptions and restarting the application. The abnormal capturing interface is a user-defined UncaudexceptionHandler, and the user-defined UncaudexceptionHandler does not display an abnormal prompt popup window. Where UncaughtExceptionHandler is the interface of the handler that is called when a thread suddenly terminates due to an uncaptured exception. Typically, when an exception occurs, the system will call UncaudexExceptionHandler to kill the application and pop the user, such as "sorry, the application has stopped running". The embodiment of the disclosure replaces the default UncaudexExceptionHandler of the system with the customized UncaudexExceptionHandler to record the exception and restart the application. Therefore, on one hand, the method can realize that the abnormity can be automatically recorded and the application can be restarted when the starting code block is abnormal only by simply modifying the default interface of the system; on the other hand, the user-defined UncaudexExceptionHandler removes the default popup of the system, so that the application can be restarted under the condition that the user does not sense the popup, and the influence of the popup on the user experience is avoided.
Referring to fig. 4, corresponding to the method for starting an application, an embodiment of the present disclosure provides a method 400 for packaging an application, including steps S401 to S403:
step S401: and acquiring a second executable file and a second resource file corresponding to the second application. The execution file (e.g., dex file of Android) and the resource file are main files inside an application installation package (APK). Illustratively, the second executable file and the second resource file corresponding to the second application may be obtained by decompressing an application installation package of the second application.
Step S402: and performing union operation on the first configuration file corresponding to the first application and the second configuration file corresponding to the second application to generate a third configuration file. The configuration file, such as Android manifest file of an Android platform, is a file necessary for each application program, is located in a root directory of the whole project, contains configuration information of the application and code of the application that the system needs to run according to the content of the application, can be used for naming a package of the application, describing various components of the application, including Activity (Activity) constituting the application, a service, a broadcast receiver and a content provider, and can also determine a process for hosting the application components, declare the lowest Android API level required by the application, list libraries to which the application must be linked, and the like. In the embodiment of the disclosure, the configuration files of the first application and the second application are subjected to union operation to cover the difference of the first application and the second application in the configuration of each component due to different versions.
Step S403: and packaging the second executable file, the second resource file and the third configuration file into an application program installation package corresponding to the first application.
The application program installation package corresponding to the first application comprises a first executable file corresponding to the first application, and the first executable file comprises a class representing the first application and a self-defined class; the second executable file includes a class representing the second application; the custom class is used to execute the above-described application-initiated method and to invoke either the class representing the first application or the class representing the second application. Classes representing applications, including classes representing a first Application and classes representing a second Application, such as the Application class of the Android system, are base classes that maintain the global state of the Application. The implementation of classes representing applications of different versions of an application is not identical, and therefore, in embodiments of the present disclosure, an application installation package contains both a class representing a first application and a class representing a second application. In addition, the embodiment of the present disclosure further includes a custom class to implement the method for starting the application, and the custom class calls the class representing the first application when the first application needs to be started, or calls the class representing the second application when the second application needs to be started. For example, the customized class in the embodiment of the present disclosure may be customized on the basis of an Application class of the first Application or the second Application, specifically, the relevant service code may be deleted in an OnCreate () function of the Application class, only a code for executing the Application start method is reserved, and when the Application process starts, the Android system may call the customized class and call an OnCreate () function therein to execute the Application start method, and call the Application class of the first Application or the Application class of the second Application according to a corresponding determination, so as to execute the code of the first Application or the code of the second Application. Therefore, the user-defined class is used as an entrance or a bridge after the application is started, so that the relevant codes of the first application or the second application can be selected to be executed after the application is started.
In this way, according to the embodiment of the present disclosure, the executable file and the resource file of the second application are additionally packaged into the application program installation package of the first application together, so that the first application starts the application based on the executable file and the resource file of the second application as needed, and the running files loaded after the application is started are all files of the second application, and the running performance of the second application is the same as that of the second application, thereby realizing automatic replacement of the version of the application.
In some embodiments, step S401 may further include: and saving the second executable file and the second resource file to the assets directory corresponding to the first application. The assets directory is a resource directory of the android platform, and files stored in the assets directory cannot be directly accessed by the application. Therefore, the second executable file and the second resource file are stored in the first application assets directory, and the influence on the normal operation of the first application can be avoided.
In some embodiments, the first application is a testboard application and the second application is a previous formal version of the first application. Generally speaking, a large number of bugs often exist in the test version application and are not repaired, in the embodiment of the disclosure, after the application is abnormal and reported, a developer obtains corresponding abnormal information, and the application can be rolled back to the last formal version, so that the user experience is prevented from being continuously influenced by the abnormal application.
Referring to fig. 5, an embodiment of the present disclosure provides an apparatus 500 for application startup, to implement the method for application startup provided by the foregoing embodiment, where the apparatus 500 includes a checking unit 501, a decompressing unit 502, a replacement determining unit 503, and a second starting unit 504, where:
a checking unit 501, configured to check whether a second executable file and a second resource file are stored in the local directory after the first application starts to be started;
a decompressing unit 502, configured to decompress the second executable file and the second resource file from the application installation package of the first application to the local directory if the local directory does not store the second executable file and the second resource file;
a replacement determining unit 503, configured to determine whether the first application satisfies a preset replacement condition if the local directory stores the second executable file and the second resource file;
a second starting unit 504, configured to, if the first application meets the replacement condition, replace the first executable file and the first resource file with the decompressed second executable file and second resource file, respectively, to start the second application;
the second application and the first application are different versions of the same application, for example, the second application is a last formal version application of the first application; the first executable file and the first resource file are files corresponding to the first application; the second executable file and the second resource file are corresponding files of a second application. An executable file refers to a file including all operation instructions and operation data of an application program, such as a dex file of an android platform; resource files refer to resources in an application that are separate from the source code, such as images, audio files, and any content related to the visual presentation of the application; the local directory is a directory used for storing files locally at the terminal, and does not include a file directory included in the application program installation package of the first application. The dex file and the resource file of the second application are pre-built in the application program installation package of the first application for subsequent replacement use.
In this way, according to the embodiment of the present disclosure, the executable file and the resource file of the second application are built in the application program installation package of the first application, and the files are decompressed in the process of starting the first application, so that the executable file and the resource file of the first application are replaced respectively when the first application meets the replacement condition, so that the running files loaded after the application is started are all files of the second application, and the running performance of the second application is the same as that of the second application.
For the embodiments of the apparatus, since they correspond substantially to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described apparatus embodiments are merely illustrative, wherein the modules described as separate modules may or may not be separate. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of the present embodiment. One of ordinary skill in the art can understand and implement without inventive effort.
In some embodiments, the replacement determination unit 503 is further configured to: and determining whether the first application receives a replacement instruction sent by the server or determining whether the abnormal times of the first application exceed a preset threshold. If the first application receives a replacement instruction sent by the server or the number of times that the first application has occurred exceeds a preset threshold, the replacement determining unit 503 may determine that the first application satisfies a preset replacement condition. In the embodiment of the disclosure, an application developer can actively send a replacement instruction to a client through a server according to the BUG feedback condition of an application, or the client determines whether to replace an application version according to the actual running condition of the application.
Referring to fig. 6, in some embodiments, the apparatus 500 for application startup further includes an exception capture unit 505, configured to record an exception in local cache data and restart the first application if the first application has an exception during a startup process.
The local cache data refers to data cached in a local physical memory of the user terminal. In the embodiment of the present disclosure, when an exception occurs when the first application is started, the exception capturing unit 505 records the exception to the local cache data, so that the replacement determining unit 503 determines the number of times that the exception has occurred in the first application by reading the local cache data when the first application is started again. In this way, the replacement determining unit 503 may determine whether the first application satisfies the replacement condition at this time, and if the number of times that the abnormality has occurred exceeds the threshold T, the first application is considered to satisfy the replacement condition.
Thus, in the embodiment of the present disclosure, when an abnormality occurs in the first application, the abnormality is recorded by the abnormality capturing unit 505 and the application is restarted immediately, so that the above process is repeated until it meets the replacement condition, and it is possible to make the user unaware of the start abnormality and implement the user unaware version replacement of the application.
In some embodiments, the exception capture unit 505 may be further configured to: and calling an exception capture interface to record exceptions and restarting the application. The abnormal capturing interface is a user-defined UncaudexceptionHandler, and the user-defined UncaudexceptionHandler does not display an abnormal prompt popup window. Where UncoauthExceptionHandler is the interface of the handler that is called when a thread suddenly terminates due to an uncaptured exception. Typically, when an exception occurs, the system will call UncaughtExceptionHandler to kill the application and pop-window the user, such as "sorry, that the application has stopped running". The embodiment of the disclosure replaces the default UncaudexceptionHandler of the system with the customized UncaudexceptionHandler to record the exception and restart the application. Therefore, on one hand, when the starting code block is abnormal, the abnormal condition can be automatically recorded and the application can be restarted only by simply modifying the default interface of the system; on the other hand, the user-defined UncaudexceptionHandler removes the default popup of the system, so that the application can be restarted under the condition that the user does not sense the popup, and the influence of the popup on the user experience is avoided.
Referring to fig. 7, an apparatus 700 for packaging an application is provided in the present disclosure, to implement the method for packaging an application provided in the foregoing embodiment, where the apparatus 700 includes an obtaining unit 701, a merging unit 702, and a packaging unit 703, where:
an obtaining unit 701, configured to obtain a second executable file and a second resource file corresponding to a second application;
a merging unit 702, configured to perform union operation on a first configuration file corresponding to a first application and a second configuration file corresponding to a second application to generate a third configuration file;
a packaging unit 703 is configured to package the second executable file, the second resource file, and the third configuration file into an application installation package corresponding to the first application.
The application program installation package corresponding to the first application comprises a first executable file corresponding to the first application, and the first executable file comprises a class representing the first application and a self-defined class; the second executable file includes a class representing a second application; the custom class is used to execute the above-described application-initiated method and to invoke either the class representing the first application or the class representing the second application. The classes representing the applications, including the class representing the first Application and the class representing the second Application, such as the Application class of the Android system, are base classes that maintain the global state of the Application. The implementation of classes representing applications of different versions of an application is not identical, and therefore, in embodiments of the present disclosure, an application installation package contains both a class representing a first application and a class representing a second application. In addition, the embodiment of the present disclosure further includes a custom class to implement the method for starting the application, and the custom class calls the class representing the first application when the first application needs to be started, or calls the class representing the second application when the second application needs to be started. For example, the customized class of the embodiment of the present disclosure may be customized on the basis of an Application class of the first Application or the second Application, and specifically, the relevant service code may be deleted in an OnCreate () function of the Application class, and only a code for executing the Application start method is reserved, and when the Application process is started, the Android system may call the customized class and call an OnCreate () function therein to execute the Application start method, and call the Application class of the first Application or the Application class of the second Application according to a corresponding judgment to execute the code of the first Application or the code of the second Application. Therefore, the user-defined class is used as an entrance or a bridge after the application is started, so that the relevant codes of the first application or the second application can be selected to be executed after the application is started.
Correspondingly, the present disclosure also provides a terminal, including: at least one memory and at least one processor; the memory is used for storing program codes, and the processor is used for calling the program codes stored in the memory to execute the application starting method.
Accordingly, the present disclosure also provides a non-transitory computer storage medium storing program code for executing the above application startup method. The non-transitory computer storage medium may be a ROM, random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.
Referring now to fig. 8, a block diagram of a terminal device 600 suitable for use in implementing embodiments of the present disclosure is shown. The terminal devices in the embodiments of the present disclosure may include, but are not limited to, mobile terminals such as mobile phones, notebook computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), and the like, and fixed terminals such as digital TVs, desktop computers, and the like. The terminal device shown in fig. 8 is only an example, and should not bring any limitation to the functions and the use range of the embodiment of the present disclosure.
As shown in fig. 8, the terminal device 600 may include a processing means (e.g., a central processing unit, a graphic processor, etc.) 601 that may perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM) 602 or a program loaded from a storage means 608 into a Random Access Memory (RAM) 603. In the RAM 603, various programs and data necessary for the operation of the terminal apparatus 600 are also stored. The processing device 601, the ROM 602, and the RAM 603 are connected to each other via a bus 604. An input/output (I/O) interface 605 is also connected to bus 604.
Generally, the following devices may be connected to the I/O interface 605: input devices 606 including, for example, a touch screen, touch pad, keyboard, mouse, camera, microphone, accelerometer, gyroscope, etc.; output devices 607 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, and the like; storage 608 including, for example, tape, hard disk, etc.; and a communication device 609. The communication means 609 may allow the terminal device 600 to communicate with other devices wirelessly or by wire to exchange data. While fig. 8 illustrates a terminal apparatus 600 having various means, it is to be understood that not all illustrated means are required to be implemented or provided. More or fewer devices may alternatively be implemented or provided.
In particular, according to an embodiment of the present disclosure, the processes described above with reference to the flowcharts may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a non-transitory computer readable medium, the computer program comprising program code for executing an apparatus illustrated by the flow chart. In such an embodiment, the computer program may be downloaded and installed from a network via the communication means 609, or may be installed from the storage means 608, or may be installed from the ROM 602. The computer program, when executed by the processing device 601, performs the above-described functions defined in the device of the embodiments of the present disclosure.
It should be noted that the computer readable medium in the present disclosure can be a computer readable signal medium or a computer readable storage medium or any combination of the two. A computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the foregoing. More specific examples of the computer readable storage medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. In contrast, in the present disclosure, a computer readable signal medium may comprise a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take many forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to: electrical wires, optical cables, RF (radio frequency), etc., or any suitable combination of the foregoing.
In some embodiments, the clients, servers may communicate using any currently known or future developed network Protocol, such as HTTP (HyperText Transfer Protocol), and may interconnect with any form or medium of digital data communication (e.g., a communications network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), the Internet (e.g., the Internet), and peer-to-peer networks (e.g., ad hoc peer-to-peer networks), as well as any currently known or future developed network.
The computer readable medium may be included in the terminal device; or may exist separately without being assembled into the terminal device.
The computer readable medium carries one or more programs which, when executed by the terminal device, cause the terminal device to: after the first application starts to be started, whether a second executable file and a second resource file are stored in the local directory is checked; if not, decompressing the second executable file and the second resource file from the application program installation package of the first application to the local directory; if so, determining whether the first application meets a preset replacement condition; if the first application meets the replacement condition, replacing the first executable file and the first resource file with the decompressed second executable file and the decompressed second resource file respectively to start a second application; wherein the second application and the first application are different versions of the same application; the first executable file and the first resource file are files corresponding to the first application; the second executable file and the second resource file are corresponding files of the second application.
Alternatively, the computer readable medium carries one or more programs which, when executed by the terminal device, cause the terminal device to: after the first application starts to be started, whether a second executable file and a second resource file are stored in a local directory or not is checked; if not, decompressing the second executable file and the second resource file from the application program installation package of the first application to the local directory; if yes, determining whether the first application meets a preset replacement condition; if the first application meets the replacement condition, replacing the first executable file and the first resource file with the decompressed second executable file and the decompressed second resource file respectively to start a second application; wherein the second application and the first application are different versions of the same application; the first executable file and the first resource file are files corresponding to the first application; the second executable file and the second resource file are corresponding files of the second application.
Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages, including but not limited to an object oriented programming language such as Java, smalltalk, C + +, including conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet service provider).
The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, apparatuses, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.
The units described in the embodiments of the present disclosure may be implemented by software or hardware. The name of the unit does not in some cases constitute a limitation on the unit itself, and for example, the checking unit may be further described as "a unit for checking whether the local directory holds the second executable file and the second resource file after the first application starts to be started".
The functions described herein above may be performed, at least in part, by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field Programmable Gate Arrays (FPGAs), application Specific Integrated Circuits (ASICs), application Specific Standard Products (ASSPs), systems on a chip (SOCs), complex Programmable Logic Devices (CPLDs), and the like.
In the context of this disclosure, a machine-readable medium may be a tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.
According to one or more embodiments provided by the present disclosure, there is provided a method of application launching, the method including: after the first application starts to be started, whether a second executable file and a second resource file are stored in the local directory is checked; if not, decompressing the second executable file and the second resource file from the application program installation package of the first application to the local directory; if so, determining whether the first application meets a preset replacement condition; if the first application meets the replacement condition, replacing the first executable file and the first resource file with the decompressed second executable file and second resource file respectively to start the second application; the second application and the first application are different versions of the same application; the first executable file and the first resource file are files corresponding to the first application; the second executable file and the second resource file are corresponding files of a second application.
According to one or more embodiments provided by the disclosure, the second executable file and the second resource file are pre-compressed and stored in the assets directory of the application installation package of the first application.
According to one or more embodiments provided by the present disclosure, determining whether the first application satisfies a preset replacement condition includes: and determining whether the first application receives a replacement instruction sent by the server or determining whether the abnormal times of the first application exceed a preset threshold.
According to the method for starting the application provided by one or more embodiments of the disclosure, the method further comprises the following steps: and if the first application is abnormal in the starting process, recording the abnormality in the local cache data and restarting the first application.
According to one or more embodiments provided by the present disclosure, determining whether the number of exceptions that have occurred to the first application exceeds a preset threshold includes: and determining whether the abnormal times of the first application exceed a preset threshold value according to the local cache data.
According to one or more embodiments provided by the present disclosure, recording an exception in local cache data and restarting a first application includes: calling an exception capture interface to record exceptions and restarting the application; the abnormal capturing interface is a user-defined UncaudexceptionHandler, and the user-defined UncaudexceptionHandler does not display an abnormal prompt popup window.
According to one or more embodiments provided by the present disclosure, the first application is a testboard application, and the second application is a previous formal version application of the first application.
According to one or more embodiments provided by the present disclosure, there is provided a method of application packaging, the method including: acquiring a second executable file and a second resource file corresponding to a second application; performing union operation on a first configuration file corresponding to the first application and a second configuration file corresponding to the second application to generate a third configuration file; packaging the second executable file, the second resource file and the third configuration file into an application program installation package corresponding to the first application; the application program installation package comprises a first executable file corresponding to a first application, and the first executable file comprises a class representing the first application and a self-defined class; the second executable file includes a class representing a second application; the custom class is used to execute the method of application launching described in the claims above and to invoke either the class representing the first application or the class representing the second application.
According to one or more embodiments provided by the present disclosure, acquiring a second executable file and a second resource file corresponding to a second application includes: and saving the second executable file and the second resource file to the assets directory corresponding to the first application.
According to one or more embodiments provided by the present disclosure, the first application is a testboard application, and the second application is a previous formal version application of the first application.
According to one or more embodiments provided by the present disclosure, there is provided an apparatus for application startup, the apparatus including: the checking unit is used for checking whether the local directory stores a second executable file and a second resource file after the first application starts to be started; the decompression unit is used for decompressing the second executable file and the second resource file from the application program installation package of the first application to the local directory if the second executable file and the second resource file are not stored in the local directory; a replacement determining unit, configured to determine whether the first application satisfies a preset replacement condition if the local directory stores the second executable file and the second resource file; the second starting unit is used for replacing the first executable file and the first resource file by the decompressed second executable file and the decompressed second resource file respectively to start the second application; the second application and the first application are different versions of the same application; the first executable file and the first resource file are files corresponding to the first application; the second executable file and the second resource file are corresponding files of a second application.
According to one or more embodiments provided by the present disclosure, there is provided an apparatus for application packaging, the apparatus including: the acquisition unit is used for acquiring a second executable file and a second resource file corresponding to a second application; the merging unit is used for performing union operation on a first configuration file corresponding to the first application and a second configuration file corresponding to the second application to generate a third configuration file; the packaging unit is used for packaging the second executable file, the second resource file and the third configuration file into an application program installation package corresponding to the first application; the application program installation package comprises a first executable file corresponding to a first application, and the first executable file comprises a class representing the first application and a self-defined class; the second executable file includes a class representing a second application; the custom class is used to execute the above-described application-initiated method and to invoke either the class representing the first application or the class representing the second application.
According to one or more embodiments provided by the present disclosure, there is provided a terminal including: at least one memory and at least one processor; the memory is used for storing program codes, and the processor is used for calling the program codes stored in the memory to execute the method for starting the application.
According to one or more embodiments provided by the present disclosure, a non-transitory computer storage medium storing program code for performing the above-described method of application startup is provided.
Further, while operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Likewise, while several specific implementation details are included in the above discussion, these should not be construed as limitations on the scope of the disclosure. Certain features that are described in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination.
Although the subject matter has been described in language specific to structural features and/or logical acts of devices, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.
Claims (14)
1. A method for application launching, the method comprising:
after the first application starts to be started, whether a second executable file and a second resource file are stored in the local directory is checked;
if not, decompressing the second executable file and the second resource file from the application program installation package of the first application to the local directory;
if yes, determining whether the first application meets a preset replacement condition;
if the first application meets the replacement condition, replacing the first executable file and the first resource file with the decompressed second executable file and the decompressed second resource file respectively to start a second application;
wherein the second application and the first application are different versions of the same application; the first executable file and the first resource file are files corresponding to the first application; the second executable file and the second resource file are corresponding files of the second application.
2. The method for starting an application according to claim 1, wherein the second executable file and the second resource file are pre-compressed and stored in an assets directory of an application installation package of the first application.
3. The method of application launching as described in claim 1, wherein said determining whether said first application satisfies a preset replacement condition comprises:
determining whether the first application receives a replacement instruction sent by a server, or
And determining whether the abnormal times of the first application exceed a preset threshold.
4. The method of application launching of claim 3, the method further comprising:
and if the first application is abnormal in the starting process, recording the abnormality in local cache data and restarting the first application.
5. The method for application launching as described in claim 4, wherein said determining whether the number of exceptions that have occurred to the first application exceeds a preset threshold comprises:
and determining whether the abnormal times of the first application exceed a preset threshold value according to the local cache data.
6. The method of application launching of claim 4, wherein the logging the exception in local cache data and the restarting the first application comprises:
calling an exception capture interface to record the exception and restart the application;
the abnormal capturing interface is a self-defined UncaudexexceptinonHandler, and the self-defined UncaudexExceptionHandler does not display an abnormal prompt popup window.
7. The method of application launching as described in claim 1, wherein the first application is a testboard application and the second application is a previous formal application of the first application.
8. A method of application packaging, the method comprising:
acquiring a second executable file and a second resource file corresponding to a second application;
performing union operation on a first configuration file corresponding to the first application and a second configuration file corresponding to the second application to generate a third configuration file;
packaging the second executable file, the second resource file and the third configuration file into an application installation package corresponding to the first application;
the application program installation package comprises a first executable file corresponding to the first application, and the first executable file comprises a class representing the first application and a self-defined class; the second executable file includes a class representing a second application; the custom class is for performing the method of any of claims 1 to 7 and for invoking the class representing the first application or the class representing the second application.
9. The method for packaging an application of claim 8, wherein the obtaining a second executable file and a second resource file corresponding to a second application comprises:
and saving the second executable file and the second resource file to the assets directory corresponding to the first application.
10. The method of application packaging of claim 8, wherein the first application is a testboard application and the second application is a previous formal application of the first application.
11. An apparatus for application launching, the apparatus comprising:
the checking unit is used for checking whether the local directory stores a second executable file and a second resource file after the first application starts to be started;
a decompressing unit, configured to decompress the second executable file and the second resource file from the application installation package of the first application to the local directory if the second executable file and the second resource file are not stored in the local directory;
a replacement determining unit, configured to determine whether the first application satisfies a preset replacement condition if the second executable file and the second resource file are stored in the local directory;
a second starting unit, configured to replace the first executable file and the first resource file with the decompressed second executable file and the decompressed second resource file, respectively, to start a second application;
wherein the second application and the first application are different versions of the same application; the first executable file and the first resource file are files corresponding to the first application; the second executable file and the second resource file are corresponding files of the second application.
12. An apparatus for application packaging, the apparatus comprising:
the acquisition unit is used for acquiring a second executable file and a second resource file corresponding to a second application;
the merging unit is used for performing union operation on a first configuration file corresponding to the first application and a second configuration file corresponding to the second application to generate a third configuration file;
a packing unit, configured to pack the second executable file, the second resource file, and the third configuration file into an application installation package corresponding to the first application;
the application program installation package comprises a first executable file corresponding to the first application, and the first executable file comprises a class representing the first application and a self-defined class; the second executable file includes a class representing a second application; the custom class is for performing the method of any of claims 1 to 7 and for invoking the class representing the first application or the class representing the second application.
13. A terminal, characterized in that the terminal comprises:
at least one memory and at least one processor;
wherein the memory is configured to store program code and the processor is configured to call the program code stored in the memory to perform the method of any of claims 1 to 10.
14. A non-transitory computer storage medium, characterized in that it stores a program code for executing the method of any of claims 1 to 10.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911090243.8A CN110851204B (en) | 2019-11-08 | 2019-11-08 | Application starting method and device and application packaging method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911090243.8A CN110851204B (en) | 2019-11-08 | 2019-11-08 | Application starting method and device and application packaging method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN110851204A CN110851204A (en) | 2020-02-28 |
| CN110851204B true CN110851204B (en) | 2023-04-18 |
Family
ID=69600157
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911090243.8A Active CN110851204B (en) | 2019-11-08 | 2019-11-08 | Application starting method and device and application packaging method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN110851204B (en) |
Families Citing this family (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113760338B (en) * | 2020-06-05 | 2023-07-18 | 北京字跳网络技术有限公司 | Method and device for switching application binary interface ABI and electronic equipment |
| CN112416418A (en) * | 2020-08-13 | 2021-02-26 | 上海哔哩哔哩科技有限公司 | Application component generation method and device, computer equipment and readable storage medium |
| CN112083928A (en) * | 2020-08-31 | 2020-12-15 | 广州新视展投资咨询有限公司 | Construction method of application program installation package, application program running method and device |
| CN114564369B (en) * | 2022-04-28 | 2022-08-02 | 云账户技术(天津)有限公司 | Application program abnormity monitoring method and device, electronic equipment and storage medium |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106126290A (en) * | 2016-06-27 | 2016-11-16 | 微梦创科网络科技（中国）有限公司 | Application program optimization method, Apparatus and system |
| CN107357613A (en) * | 2017-06-28 | 2017-11-17 | 广州酷狗计算机科技有限公司 | Using update method, device and computer-readable recording medium |
| CN107506221A (en) * | 2017-09-28 | 2017-12-22 | 阿里巴巴集团控股有限公司 | Application program updating method, apparatus and equipment |
| CN108491216A (en) * | 2018-03-05 | 2018-09-04 | 北京指掌易科技有限公司 | A kind of method of android system unaware application installation upgrading |
| CN109445829A (en) * | 2018-12-19 | 2019-03-08 | 四川虹美智能科技有限公司 | A kind of product software programme upgrade method, apparatus and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8191060B2 (en) * | 2006-08-29 | 2012-05-29 | Adobe Systems Incorporated | Software installation using template executables |
-
2019
- 2019-11-08 CN CN201911090243.8A patent/CN110851204B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106126290A (en) * | 2016-06-27 | 2016-11-16 | 微梦创科网络科技（中国）有限公司 | Application program optimization method, Apparatus and system |
| CN107357613A (en) * | 2017-06-28 | 2017-11-17 | 广州酷狗计算机科技有限公司 | Using update method, device and computer-readable recording medium |
| CN107506221A (en) * | 2017-09-28 | 2017-12-22 | 阿里巴巴集团控股有限公司 | Application program updating method, apparatus and equipment |
| CN108491216A (en) * | 2018-03-05 | 2018-09-04 | 北京指掌易科技有限公司 | A kind of method of android system unaware application installation upgrading |
| CN109445829A (en) * | 2018-12-19 | 2019-03-08 | 四川虹美智能科技有限公司 | A kind of product software programme upgrade method, apparatus and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN110851204A (en) | 2020-02-28 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110851204B (en) | Application starting method and device and application packaging method and device | |
| CN111090536B (en) | Method, device, medium and electronic equipment for acquiring memory leakage information | |
| CN109918166B (en) | Applet processing method and device and electronic equipment | |
| CN107291481B (en) | Component updating method, device and system | |
| CN111240766B (en) | Application starting method and device, electronic equipment and computer readable storage medium | |
| CN112965761B (en) | Data processing method, system, electronic equipment and storage medium | |
| CN111309391A (en) | Application program starting method, device, equipment and medium | |
| CN107644075B (en) | Method and device for collecting page information | |
| CN112596720A (en) | Service operation method and device, electronic equipment and computer storage medium | |
| CN113900721A (en) | Operating system starting method and device and electronic equipment | |
| CN111079125A (en) | Method and device for calling third-party library dynamic lifting authority by application program | |
| CN113886264A (en) | Embedded method, device, equipment and storage medium of distributed database | |
| CN114328097A (en) | File monitoring method and device, electronic equipment and storage medium | |
| CN111782231B (en) | Service deployment method and device | |
| CN112905220A (en) | Thermal restoration method, device, equipment and storage medium | |
| CN114090090B (en) | Starting method and device of terminal firmware, electronic equipment and storage medium | |
| CN113934437B (en) | Method and system for installing application on cloud mobile phone and client cloud mobile phone | |
| CN110502251B (en) | Application installation method and device | |
| CN116360802A (en) | Middleware processing method, middleware processing device, electronic equipment and storage medium | |
| CN111324386A (en) | Method and device for starting personal application program, electronic equipment and storage medium | |
| CN111324888B (en) | Verification method and device for application program starting, electronic equipment and storage medium | |
| CN111625326A (en) | Task pipeline execution method and device and electronic equipment | |
| CN111382076A (en) | Application program testing method and device, electronic equipment and computer storage medium | |
| CN116382796B (en) | Plug-in management method and device of H5 applet runner and electronic equipment | |
| CN115033139B (en) | Method and related device for starting application program interface |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |