CN108762771B - Plug-in unloading method and electronic terminal - Google Patents

Abstract

The invention discloses a plug-in unloading method and an electronic terminal, wherein the current state of a plug-in is inquired based on an unloading request of a user for unloading the plug-in an application program; and if the current state of the plug-in is the running state, adding uninstalling field information in the plug-in. The unloading field information is used for indicating that the plug-in is in the state of waiting to be unloaded, so that if the unloading field information is read, the plug-in needs to be unloaded. The plug-in unit is initialized at the next starting, namely all data of the plug-in unit is read for loading. Therefore, in the process of starting the plug-in next time, when the uninstalling field information is read, the plug-in and the related files thereof are deleted based on the uninstalling field information. Therefore, the plug-in can be unloaded when the plug-in is started next time due to the addition of the unloading field information, the implementation of the method does not influence the current use of the plug-in, the problem that the plug-in can be unloaded only when the plug-in needs to be closed is avoided, and the plug-in can be conveniently unloaded.

Description

Plug-in uninstall method and electronic terminal

technical field

The invention relates to the field of communication technologies, and in particular, to a plug-in uninstallation method and an electronic terminal.

Background technique

A plug-in (Plug-in, also known as addin, add-in, addon or add-on, also translated as plug-in) is a program written in accordance with a certain standard application program interface. A plug-in refers to a program that is automatically executed with the startup of the IE browser. It can only run under the system platform specified by the program, and may support multiple platforms at the same time, but cannot run independently of the specified platform. That is, the plug-in must be attached to the application's startup to be able to run. There are countless types of plug-ins. For example, some plug-in programs can help users browse the Internet more conveniently or call online auxiliary functions, and some plug-ins can help users pay online and so on. For example, after installing the relevant plug-in, the browser can directly call the plug-in program for processing certain types of files.

Due to the particularity of plug-ins, each module in the Replugin plug-in framework exists and runs as a plug-in. To remove a plug-in module in the Replugin plug-in framework, the plug-in needs to be uninstalled.

At present, the uninstallation of the plug-in is generally done when the plug-in is not working, and when the plug-in is working normally, the user will be prompted to "close the plug-in" to uninstall, which affects the use of the currently running plug-in and causes the currently running plug-in to appear. There is a problem that it is not easy to uninstall.

SUMMARY OF THE INVENTION

In view of the above problems, the present invention is proposed to provide a plug-in uninstallation method and an electronic terminal that overcome the above problems or at least partially solve the above problems.

One aspect of the present invention provides a method for uninstalling a plug-in, the method comprising:

querying the current state of the plug-in based on a user's uninstall request for uninstalling a plug-in in an application;

If it is found that the current state of the plug-in is the running state, add an uninstall field information to the plug-in, and the uninstall field information is used to identify that the plug-in is in a state to be uninstalled;

During the next startup of the plug-in, the plug-in and its related files are deleted based on the uninstall field information.

Preferably, the querying the current state of the plug-in specifically includes:

Call the isPluginRunning interface to query the current status of the plug-in.

Preferably, before the querying the current state of the plug-in, the method further includes:

Get the plugin name of the plugin;

obtaining plug-in information based on the plug-in name of the plug-in;

Determine whether the plug-in information is empty;

If so, it means that the plug-in is not installed;

If not, it means that the plug-in information is an installed plug-in whose current running state is unknown.

Preferably, after querying the current state of the plug-in, the method further includes:

If it is found that the current state of the plug-in is not running, the plug-in and its related files are deleted.

Preferably, the adding an uninstall field information in the plug-in specifically includes:

The unloading field information delinfo is added to the p.l file of the application in Json format.

Preferably, during the next startup of the plug-in, deleting the plug-in and its related files based on the uninstall field information specifically includes:

During the next startup of the plug-in, load the relevant files of the plug-in;

Determine whether the relevant file of the plug-in has the uninstall field information;

If there is the uninstall field information, delete the plug-in and its related files based on the uninstall field information;

If there is no unload field information, the plug-in is loaded and started based on the relevant file of the plug-in.

Preferably, the deletion of the plug-in and its related files based on the uninstall field information specifically includes:

Based on the system version number where the plug-in is located, the configuration file corresponding to the system version in the plug-in is deleted.

Preferably, after the configuration file corresponding to the system version in the plug-in is deleted based on the system version number where the plug-in is located, the method further includes: deleting the Native file.

Preferably, after the plugin and its related files are deleted based on the uninstall field information, the method further includes:

recording the unloading field information;

Delete the uninstall field information.

Preferably, after the plugin and its related files are deleted based on the uninstall field information, the method further includes:

A broadcast notification is sent to each process, and the latest state of the plug-in is synchronized to each process.

Preferably, after the plugin and its related files are deleted based on the uninstall field information, the method further includes:

Update the memory table information of the process where the plug-in is located.

Another aspect of the present invention discloses an electronic terminal, comprising:

a query module, configured to query the current state of the plug-in based on a user's uninstall request for uninstalling a plug-in in an application;

The adding module is configured to add an uninstall field information to the plug-in if the current state of the plug-in is found to be the running state, where the uninstall field information is used to identify that the plug-in is in a state to be uninstalled;

An uninstall module, configured to delete the plug-in and its related files based on the uninstall field information during the next startup of the plug-in.

Preferably, the querying the current state of the plug-in specifically includes:

Call the isPluginRunning interface to query the current status of the plug-in.

Preferably, the electronic terminal further includes:

The first obtaining module is used to obtain the plug-in name of the plug-in;

The second obtaining module is used to obtain plug-in information based on the plug-in name of the plug-in;

The first judgment module is used for judging whether the plug-in information is empty; if so, it means that the plug-in is not installed; if not, it means that the plug-in information is a plug-in whose current running state is unknown.

Preferably, the electronic terminal further includes:

A deletion module, configured to delete the plug-in and its related files if the current state of the plug-in is found to be a non-running state.

Preferably, the adding module is specifically configured to add the unloading field information delinfo to the p.l file of the application in Json format.

Preferably, the unloading module specifically includes:

a first loading module, used for loading the relevant files of the plug-in during the next startup of the plug-in;

The second judgment module is used for judging whether the relevant file of the plug-in has the uninstall field information;

a first deletion module, configured to delete the plug-in and its related files based on the uninstallation field information if there is the uninstallation field information;

The second loading module is configured to load and start the plug-in based on the relevant file of the plug-in if there is no unload field information.

Preferably, the uninstallation module is specifically configured to delete the configuration file corresponding to the system version in the plug-in based on the system version number where the plug-in is located.

Preferably, the uninstallation module is also used to delete the Native file.

Preferably, the electronic terminal further includes:

a recording module for recording the unloading field information;

The second deletion module is used to delete the uninstall field information.

Preferably, the electronic terminal further includes: a synchronization module, configured to send a broadcast notification to each process, and synchronize the latest state of the plug-in to each process.

Preferably, the electronic terminal further comprises: an update module for updating the memory table information of the process where the plug-in is located.

In another aspect of the present invention, a computer program is stored thereon, and the program implements the steps of the above method when executed by a processor.

Another aspect of the present invention provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, the processor implementing the steps of the above method when executing the program.

The technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages:

The invention discloses a plug-in uninstalling method and an electronic terminal. Based on a user's uninstall request for uninstalling a plug-in in an application program, the current state of the plug-in is queried; if the current state of the plug-in is found to be the running state, the An uninstall field information is added to the plug-in. The uninstall field information is used to indicate that the plug-in is in a state to be uninstalled, so if the uninstall field information is read, it means that the plug-in needs to be uninstalled. Because the plugin will be initialized the next time it starts, that is, read all its own data for loading. Therefore, during the next startup of the plug-in, when the uninstall field information is read, the plug-in and its related files will be deleted based on the uninstall field information. Therefore, the plugin in the present invention can be uninstalled when the plugin is started next time due to the addition of uninstall field information. The implementation of this method not only does not affect the current use of the plugin, but also avoids the problem that the plugin must be closed to uninstall the plugin. Plugins can be easily uninstalled.

Further, the existing method of uninstalling a plug-in actually uses the method of "disabled" plug-in function to uninstall, resulting in a large number of "disabled plug-ins" occupying the system memory, which is easy to slow down the system running speed and cause a freeze phenomenon. In the present invention, the method of deleting the plug-in and its related files is directly adopted, and all relevant information of the plug-in is deleted, so that the memory occupies less and the system operation is not affected.

The above description is only an overview of the technical solutions of the present invention. In order to understand the technical means of the present invention more clearly, it can be implemented according to the content of the description, and in order to make the above and other objects, features and advantages of the present invention more obvious and easy to understand , the following specific embodiments of the present invention are given.

Description of drawings

Various other advantages and benefits will become apparent to those of ordinary skill in the art upon reading the following detailed description of the preferred embodiments. The drawings are for the purpose of illustrating preferred embodiments only and are not to be considered limiting of the invention. Also, the same components are denoted by the same reference numerals throughout the drawings. In the attached image:

Fig. 1 shows a plug-in uninstallation method according to an embodiment of the present invention;

FIG. 2 shows a schematic diagram of an electronic terminal according to an embodiment of the present invention.

Detailed ways

Exemplary embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. While exemplary 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 limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present disclosure will be more thoroughly understood, and will fully convey the scope of the present disclosure to those skilled in the art.

The embodiment of the present invention provides a method for uninstalling a plug-in, so as to solve the problem that the current running plug-in is not easy to uninstall in the prior art.

For details, please refer to FIG. 1 , which is an implementation process diagram of a plug-in uninstallation method in an embodiment of the present invention.

Step 11, based on a user's uninstall request for uninstalling a plug-in in an application, query the current state of the plug-in.

In the embodiment of the present invention, each functional module in the involved application program exists in the Replugin plug-in framework. Therefore, removing a function in an application is equivalent to uninstalling the corresponding plug-in. And each plug-in has its own current state, the current state is: running state or not running state and so on.

Before querying the current state of the plug-in, based on the user's uninstall request to uninstall the plug-in in an application, the plug-in name of the plug-in is obtained first, and the plug-in name cannot be empty. Plug-in information is then obtained based on the plug-in name of the plug-in. It is judged whether the plug-in information is empty; if it is, it means that the plug-in is not installed, and can be returned directly without processing. If not, it means that the plug-in information represents a plug-in that has been installed but whose current running state is unknown.

In the specific implementation process, because the Replugin framework adopts a dual-process architecture by default. The dual-process architecture is to run two processes at the same time. When the resident process is interrupted unexpectedly, a backup process can be started to ensure the normal operation of the plug-in, and the operation will not be interrupted due to the unexpected interruption of the resident process, and vice versa.

The unloading operations of the plug-ins in the embodiments of the present invention can all be placed in the resident process, and are specifically completed by a plug-in manager (PluginManagerServer class). For the uninstallation of installed plug-ins, there are roughly two states: the plug-in is running and the plug-in is not running.

In the process of querying the current state of the plug-in, the isPluginRunning interface can be called to query the current state of the plug-in.

Step 12: If it is found that the current state of the plug-in is the running state, add uninstall field information to the plug-in, where the uninstall field information is used to identify that the plug-in is in a state to be uninstalled.

In the specific implementation process, when the plug-in has been installed and is running, in this case, since the plug-in is being used (may be used by the user or other plug-ins), the uninstall operation cannot be performed immediately, so an uninstall field is added to the plug-in The information is used to identify that the plug-in is in a state to be uninstalled, so that the plug-in can be uninstalled at the next startup.

Further, by calling the setPendingDelete interface, an object of the plug-in information to be uninstalled (that is, the uninstall field information) is maintained inside the plug-in information object (PluginInfo), and the uninstall field information delinfo is added as a key value to the Json format. In the p.l file in the application's own directory, the pending uninstallation status of the plug-in is recorded, and the plug-in uninstall operation is postponed until the resident process restarts.

As an optional embodiment, if it is found that the current state of the plug-in is not running, the plug-in and its related files are deleted. In the specific implementation process, the processing process of the plug-in when it is not running is actually similar to the processing process when the plug-in is added to the uninstall field information at the next startup. Therefore, the present invention will not repeat the deletion process when the plug-in is not running.

Step 13, during the next startup of the plug-in, delete the plug-in and its related files based on the uninstall field information.

In the specific implementation process of deleting the plug-in and its related files based on the uninstall field information, during the next startup of the plug-in, load the related files of the plug-in; determine whether the related files of the plug-in have the uninstallation field information; if there is the uninstallation field information, delete the plug-in and its related files based on the uninstallation field information; if there is no uninstallation field information, start the plugin based on the relevant file loading of the plug-in plugin.

Specifically, since each time the resident process performs the restart operation, the initialization operation of the plug-in will be performed, which involves the management logic of the plug-in. In the p.l file mentioned in the above steps, the file not only records the uninstall field information, but also It also records the plug-in information generated by the plug-in when it is installed. Therefore, each plug-in will be read and managed according to the plug-in information in the p.l file, and the meaning of management includes plug-in version upgrade and plug-in uninstallation. Therefore, if the current plug-in contains the uninstall field information delinfo, the uninstall field information delinfo will be obtained by calling the getPendingDelete interface. Since the plug-in uninstall condition is better than the plug-in upgrade condition, it will first determine whether the plug-in needs to be uninstalled. If it needs to be uninstalled, Then, the plug-in and its related files are directly deleted, and no update operation is performed.

Of course, if the plugin is not running, the plugin and its associated files will be deleted directly.

The following is a detailed description of the plug-in deletion process.

In the specific deletion process, the configuration file corresponding to the system version in the plug-in will be deleted based on the system version number where the plug-in is located. For example, delete the APK file of the plug-in in turn, and delete the odex file released after the plug-in is installed. When deleting the relevant files of the plugin, the corresponding system version number will be queried, and then the corresponding configuration file will be deleted based on the system version number.

In the specific implementation process, determine whether the system version where the plug-in is located is higher than the first preset level version;

If the system version where the plug-in is located is higher than the first preset level version, delete the configuration file corresponding to the system version in the plug-in;

If the system version where the plug-in is located is lower than the first preset level version, further determine whether the system version where the plug-in is located is lower than the second preset level version, and if so, delete the plug-in and the system The configuration file corresponding to the version.

For example, if the system is Android 8.0 and above, you also need to delete the vdex file and **.jar.prof file released after the plugin is installed.

If it is an Android 4.0 system and below, you need to delete the directory where the dex optimization is released. If there is a so library, the Native file will be deleted. In addition, it is also necessary to delete the process lock file corresponding to the plug-in, which is created when the plug-in is installed. At this point, the files released and generated when the plugin is installed have been deleted.

Further, after the plugin and its related files are deleted based on the uninstallation field information, the uninstallation field information is also recorded; the uninstallation field information is deleted. For example, delete the delinfo field in the p.l file and save.

Further, since the state of the plug-in has changed, it is necessary to notify each process of the latest state of the plug-in in time. That is, after the plug-in and its related files are deleted based on the uninstall field information, a broadcast notification will be sent to each process to synchronize the latest status of the plug-in to each process, so as to inform each process that the plug-in has been uninstalled and removed.

In a specific implementation process, after the plug-in and its related files are deleted based on the uninstall field information, the memory table information of the process where the plug-in is located will also be updated. For example, update the memory table information of the resident process (the resident process maintains a buffer table of various information of all plug-ins, including buffer objects such as plug-in information, PackageInfo, Resources, ComponentList, and DexClassLoader): remove the uninstalled plug-in and save it Buffer data in HashMap with all plugin information, remove plugin table snapshot, remove PackageInfo, Resources, ComponentList and DexClassLoader cache object data of unloaded plugins in memory.

Based on the unified inventive concept, the following embodiments introduce an electronic terminal.

Referring to Figure 2, the electronic terminal includes:

a query module 21, configured to query the current state of the plug-in based on a user's uninstall request for uninstalling a plug-in in an application;

The adding module 22 is configured to add an uninstall field information to the plug-in if the current state of the plug-in is found to be the running state, where the uninstall field information is used to identify that the plug-in is in a state to be uninstalled;

The uninstall module 23 is configured to delete the plug-in and its related files based on the uninstall field information during the next startup of the plug-in.

As an optional embodiment, the querying the current state of the plug-in specifically includes:

Call the isPluginRunning interface to query the current status of the plug-in.

As an optional embodiment, the electronic terminal further includes:

The first obtaining module is used to obtain the plug-in name of the plug-in;

The second obtaining module is used to obtain plug-in information based on the plug-in name of the plug-in;

The first judgment module is used for judging whether the plug-in information is empty; if so, it means that the plug-in is not installed; if not, it means that the plug-in information is a plug-in whose current running state is unknown.

As an optional embodiment, the electronic terminal further includes:

A deletion module, configured to delete the plug-in and its related files if the current state of the plug-in is found to be a non-running state.

As an optional embodiment, the adding module 22 is specifically configured to add the unloading field information delinfo to the p.1 file of the application in Json format.

As an optional embodiment, the unloading module 23 specifically includes:

a first loading module, used for loading the relevant files of the plug-in during the next startup of the plug-in;

The second judgment module is used for judging whether the relevant file of the plug-in has the uninstall field information;

a first deletion module, configured to delete the plug-in and its related files based on the uninstallation field information if there is the uninstallation field information;

The second loading module is configured to load and start the plug-in based on the relevant file of the plug-in if there is no unload field information.

As an optional embodiment, the uninstallation module 23 is specifically configured to delete the configuration file corresponding to the system version in the plug-in based on the system version number where the plug-in is located.

As an optional embodiment, the uninstallation module 23 is further configured to delete the Native file.

As an optional embodiment, the electronic terminal further includes:

a recording module for recording the unloading field information;

The second deletion module is used to delete the uninstall field information.

As an optional embodiment, the electronic terminal further includes: a synchronization module, configured to send a broadcast notification to each process, and synchronize the latest state of the plug-in to each process.

As an optional embodiment, the electronic terminal further includes:

The update module is used to update the memory table information of the process where the plug-in is located.

Based on the same inventive concept as in the foregoing embodiments, the present invention further provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, implements the steps of any of the foregoing methods.

Based on the same inventive concept as in the foregoing embodiments, the present invention also provides a computer device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, when the processor executes the program Implement the steps of any of the methods described above.

The technical solutions provided in the embodiments of the present application have at least the following technical effects or advantages:

The invention discloses a plug-in uninstalling method and an electronic terminal. Based on a user's uninstall request for uninstalling a plug-in in an application program, the current state of the plug-in is queried; if the current state of the plug-in is found to be the running state, the An uninstall field information is added to the plug-in. The uninstall field information is used to indicate that the plug-in is in a state to be uninstalled, so if the uninstall field information is read, it means that the plug-in needs to be uninstalled. Because the plugin will be initialized the next time it starts, that is, read all its own data for loading. Therefore, during the next startup of the plug-in, when the uninstall field information is read, the plug-in and its related files will be deleted based on the uninstall field information. Therefore, the plugin in the present invention can be uninstalled when the plugin is started next time due to the addition of uninstall field information. The implementation of this method not only does not affect the current use of the plugin, but also avoids the problem that the plugin must be closed to uninstall the plugin. Plugins can be easily uninstalled.

Further, the existing method of uninstalling a plug-in actually uses the method of "disabling" the function of the plug-in, which results in a large number of "disabled plug-ins" occupying the system memory, which is easy to slow down the system running speed and cause a freeze phenomenon. In the present invention, the method of deleting the plug-in and its related files is directly adopted, and all relevant information of the plug-in is deleted, so that the memory occupies less and the system operation is not affected.

The algorithms and displays provided herein are not inherently related to any particular computer, virtual system, or other device. Various general-purpose systems can also be used with teaching based on this. The structure required to construct such a system is apparent from the above description. Furthermore, the present invention is not directed to any particular programming language. It is to be understood that various programming languages may be used to implement the inventions described herein, and that the descriptions of specific languages above are intended to disclose the best mode for carrying out the invention.

In the description provided herein, numerous specific details are set forth. It will be understood, however, that embodiments of the invention may be practiced without these specific details. In some instances, well-known methods, structures and techniques have not been shown in detail in order not to obscure an understanding of this description.

Similarly, it is to be understood that in the above description of exemplary embodiments of the invention, various features of the invention are sometimes grouped together into a single embodiment, figure, or its description. This disclosure, however, should not be construed as reflecting an intention that the invention as claimed requires more features than are expressly recited in each claim. Rather, as the following claims reflect, inventive aspects lie in less than all features of a single foregoing disclosed embodiment. Thus, the claims following the Detailed Description are hereby expressly incorporated into this Detailed Description, with each claim standing on its own as a separate embodiment of this invention.

Those skilled in the art will understand that the modules in the device in the embodiment can be adaptively changed and arranged in one or more devices different from the embodiment. The modules or units or components in the embodiments may be combined into one module or unit or component, and further they may be divided into multiple sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings) and any method so disclosed may be employed in any combination unless at least some of such features and/or procedures or elements are mutually exclusive. All processes or units of equipment are combined. Each feature disclosed in this specification (including accompanying claims, abstract and drawings) may be replaced by alternative features serving the same, equivalent or similar purpose, unless expressly stated otherwise.

Furthermore, it will be understood by those skilled in the art that although some of the embodiments herein include certain features, but not others, included in other embodiments, that combinations of features of the different embodiments are intended to be within the scope of the invention And form different embodiments. For example, in the following claims, any of the claimed embodiments may be used in any combination.

Various component embodiments of the present invention may be implemented in hardware, or in software modules running on one or more processors, or in a combination thereof. Those skilled in the art should understand that a microprocessor or a digital signal processor (DSP) may be used in practice to implement some or all functions of some or all of the gateways, proxy servers, and systems according to embodiments of the present invention. The present invention can also be implemented as apparatus or apparatus programs (eg, computer programs and computer program products) for performing part or all of the methods described herein. Such a program implementing the present invention may be stored on a computer-readable medium, or may be in the form of one or more signals. Such signals may be downloaded from Internet sites, or provided on carrier signals, or in any other form.

It should be noted that the above-described embodiments illustrate rather than limit the invention, and that alternative embodiments may be devised by those skilled in the art without departing from the scope of the appended claims. In the claims, any reference signs placed between parentheses shall not be construed as limiting the claim. The word "comprising" does not exclude the presence of elements or steps not listed in a claim. The word "a" or "an" preceding an element does not exclude the presence of a plurality of such elements. The invention can be implemented by means of hardware comprising several different elements and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means may be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. do not denote any order. These words can be interpreted as names.

The present invention discloses, A1, a method for uninstalling a plug-in, characterized in that the method includes:

querying the current state of the plug-in based on a user's uninstall request for uninstalling a plug-in in an application;

If it is found that the current state of the plug-in is the running state, add an uninstall field information to the plug-in, and the uninstall field information is used to identify that the plug-in is in a state to be uninstalled;

During the next startup of the plug-in, the plug-in and its related files are deleted based on the uninstall field information.

A2. The method according to A1, wherein the querying the current state of the plug-in specifically includes:

Call the isPluginRunning interface to query the current status of the plug-in.

A3. The method according to A1, wherein before the querying the current state of the plug-in, the method further comprises:

Get the plugin name of the plugin;

obtaining plug-in information based on the plug-in name of the plug-in;

Determine whether the plug-in information is empty;

If so, it means that the plug-in is not installed;

If not, it means that the plug-in information is an installed plug-in whose current running state is unknown.

A4. The method according to A1, wherein after querying the current state of the plug-in, the method further includes:

If it is found that the current state of the plug-in is not running, the plug-in and its related files are deleted.

A5. The method according to A1, wherein the adding an uninstall field information to the plug-in specifically includes:

The unloading field information delinfo is added to the p.l file of the application in Json format.

A6. The method according to A1, characterized in that, in the process of next startup of the plug-in, deleting the plug-in and its related files based on the uninstall field information specifically includes:

During the next startup of the plug-in, load the relevant files of the plug-in;

Determine whether the relevant file of the plug-in has the uninstall field information;

If there is the uninstall field information, delete the plug-in and its related files based on the uninstall field information;

If there is no unload field information, the plug-in is loaded and started based on the relevant file of the plug-in.

A7. The method according to A1, wherein the deleting the plug-in and its related files based on the uninstall field information specifically includes:

Based on the system version number where the plug-in is located, the configuration file corresponding to the system version in the plug-in is deleted.

A8. The method according to A7, wherein after deleting the configuration file corresponding to the system version in the plug-in based on the system version number where the plug-in is located, the method further comprises: deleting the Native file .

A9. The method according to A1, wherein after the plugin and its related files are deleted based on the uninstall field information, the method further includes:

recording the unloading field information;

Delete the uninstall field information.

A10. The method according to A1, wherein after the plugin and its related files are deleted based on the uninstall field information, the method further includes:

A broadcast notification is sent to each process, and the latest state of the plug-in is synchronized to each process.

A11. The method according to A1, wherein after the plugin and its related files are deleted based on the uninstall field information, the method further includes:

Update the memory table information of the process where the plug-in is located.

B12. An electronic terminal, characterized in that it includes:

a query module, configured to query the current state of the plug-in based on a user's uninstall request for uninstalling a plug-in in an application;

The adding module is configured to add an uninstall field information to the plug-in if the current state of the plug-in is found to be the running state, where the uninstall field information is used to identify that the plug-in is in a state to be uninstalled;

An uninstall module, configured to delete the plug-in and its related files based on the uninstall field information during the next startup of the plug-in.

B13. The electronic terminal according to B12, wherein the querying the current state of the plug-in specifically includes:

Call the isPluginRunning interface to query the current status of the plug-in.

B14. The electronic terminal according to B12, wherein the electronic terminal further comprises:

The first obtaining module is used to obtain the plug-in name of the plug-in;

The second obtaining module is used to obtain plug-in information based on the plug-in name of the plug-in;

The first judgment module is used for judging whether the plug-in information is empty; if so, it means that the plug-in is not installed; if not, it means that the plug-in information is a plug-in whose current running state is unknown.

B15. The electronic terminal according to B12, wherein the electronic terminal further comprises:

A deletion module, configured to delete the plug-in and its related files if the current state of the plug-in is found to be a non-running state.

B16. The electronic terminal according to B12, wherein the adding module is specifically configured to add the unloading field information delinfo to the p.1 file of the application in Json format.

B17. The electronic terminal according to B12, wherein the unloading module specifically includes:

a first loading module, used for loading the relevant files of the plug-in during the next startup of the plug-in;

The second judgment module is used for judging whether the relevant file of the plug-in has the uninstall field information;

a first deletion module, configured to delete the plug-in and its related files based on the uninstallation field information if there is the uninstallation field information;

The second loading module is configured to load and start the plug-in based on the relevant file of the plug-in if there is no unload field information.

B18. The electronic terminal according to B12, wherein the uninstallation module is specifically configured to delete the configuration file corresponding to the system version in the plug-in based on the system version number where the plug-in is located.

B19. The electronic terminal according to B18, wherein the uninstallation module is further configured to delete the Native file.

B20. The electronic terminal according to B12, wherein the electronic terminal further comprises:

a recording module for recording the unloading field information;

The second deletion module is used to delete the uninstall field information.

B21. The electronic terminal according to B12, wherein the electronic terminal further comprises: a synchronization module, configured to send a broadcast notification to each process, and synchronize the latest state of the plug-in to each process.

B22. The electronic terminal according to B12, wherein the electronic terminal further comprises:

The update module is used to update the memory table information of the process where the plug-in is located.

C23. A computer-readable storage medium on which a computer program is stored, characterized in that, when the program is executed by a processor, the steps of the method according to any one of claims A1-A12 are implemented.

D24. A computer device, comprising a memory, a processor, and a computer program stored in the memory and running on the processor, characterized in that, when the processor executes the program, any one of claims A1-A12 is implemented the steps of the method.

Claims (24)

1. a plug-in unloading method, is characterized in that, described method comprises: querying the current state of the plug-in based on a user's uninstall request for uninstalling a plug-in in an application; If it is found that the current state of the plug-in is the running state, add an uninstall field information to the plug-in, and the uninstall field information is used to identify that the plug-in is in a state to be uninstalled; During the next startup of the plug-in, the plug-in and its related files are deleted based on the uninstall field information. 2. The method of claim 1, wherein the querying the current state of the plug-in specifically comprises: Call the isPluginRunning interface to query the current status of the plug-in. 3. The method of claim 1, wherein before the querying the current state of the plug-in, the method further comprises: Get the plugin name of the plugin; obtaining plug-in information based on the plug-in name of the plug-in; Determine whether the plug-in information is empty; If so, it means that the plug-in is not installed; If not, it means that the plug-in information is an installed plug-in whose current running state is unknown. 4. The method of claim 1, wherein after the querying the current state of the plug-in, the method further comprises: If it is found that the current state of the plug-in is not running, the plug-in and its related files are deleted. 5. The method of claim 1, wherein the adding an uninstall field information in the plug-in specifically comprises: The unloading field information delinfo is added to the p.l file of the application in Json format. 6. The method according to claim 1, wherein, during the next startup of the plug-in, deleting the plug-in and its related files based on the uninstall field information, specifically comprising: During the next startup of the plug-in, load the relevant files of the plug-in; Determine whether the relevant file of the plug-in has the uninstall field information; If there is the uninstall field information, delete the plug-in and its related files based on the uninstall field information; If there is no unload field information, the plug-in is loaded and started based on the relevant file of the plug-in. 7. The method of claim 1, wherein the deleting the plug-in and its related files based on the uninstall field information specifically comprises: Based on the system version number where the plug-in is located, the configuration file corresponding to the system version in the plug-in is deleted. 8. The method according to claim 7, wherein after deleting the configuration file corresponding to the system version in the plug-in based on the system version number where the plug-in is located, the method further comprises: deleting Native file. 9. The method according to claim 1, wherein after the plugin and its related files are deleted based on the uninstall field information, the method further comprises: recording the unloading field information; Delete the uninstall field information. 10. The method of claim 1, wherein after deleting the plug-in and its related files based on the uninstall field information, the method further comprises: A broadcast notification is sent to each process, and the latest state of the plug-in is synchronized to each process. 11. The method of claim 1, wherein after deleting the plug-in and its related files based on the uninstall field information, the method further comprises: Update the memory table information of the process where the plug-in is located. 12. An electronic terminal, characterized in that, comprising: a query module, configured to query the current state of the plug-in based on a user's uninstall request for uninstalling a plug-in in an application; An adding module, configured to add an uninstall field information to the plug-in if the current state of the plug-in is found to be the running state, where the uninstall field information is used to identify that the plug-in is in a state to be uninstalled; An uninstall module, configured to delete the plug-in and its related files based on the uninstall field information during the next startup of the plug-in. 13. The electronic terminal according to claim 12, wherein the querying the current state of the plug-in specifically comprises: Call the isPluginRunning interface to query the current state of the plug-in. 14. The electronic terminal of claim 12, wherein the electronic terminal further comprises: The first obtaining module is used to obtain the plug-in name of the plug-in; The second obtaining module is used to obtain plug-in information based on the plug-in name of the plug-in; The first judgment module is used for judging whether the plug-in information is empty; if so, it means that the plug-in is not installed; if not, it means that the plug-in information is a plug-in whose current running state is unknown. 15. The electronic terminal of claim 12, wherein the electronic terminal further comprises: A deletion module, configured to delete the plug-in and its related files if the current state of the plug-in is found to be a non-running state. 16. The electronic terminal according to claim 12, wherein the adding module is specifically configured to add the unloading field information delinfo to the p.l file of the application in Json format. 17. The electronic terminal according to claim 12, wherein the unloading module specifically comprises: a first loading module, used for loading the relevant files of the plug-in during the next startup of the plug-in; The second judgment module is used for judging whether the relevant file of the plug-in has the uninstall field information; a first deletion module, configured to delete the plug-in and its related files based on the uninstallation field information if there is the uninstallation field information; The second loading module is configured to load and start the plug-in based on the relevant file of the plug-in if there is no unload field information. 18 . The electronic terminal according to claim 12 , wherein the uninstallation module is specifically configured to delete a configuration file corresponding to the system version in the plug-in based on the system version number where the plug-in is located. 19 . 19. The electronic terminal according to claim 18, wherein the uninstallation module is further configured to delete Native files. 20. The electronic terminal of claim 12, wherein the electronic terminal further comprises: a recording module for recording the unloading field information; The second deletion module is configured to delete the uninstall field information. 21. The electronic terminal according to claim 12, wherein the electronic terminal further comprises: a synchronization module, configured to send a broadcast notification to each process, and synchronize the latest state of the plug-in to each process. 22. The electronic terminal of claim 12, wherein the electronic terminal further comprises: An update module, configured to update the memory table information of the process where the plug-in is located. 23. A computer-readable storage medium on which a computer program is stored, characterized in that, when the program is executed by a processor, the steps of the method according to any one of claims 1-11 are implemented. 24. A computer device comprising a memory, a processor and a computer program stored in the memory and running on the processor, wherein the processor implements any one of claims 1-11 when executing the program the steps of the method described in item.

Images