CN108762771A - A kind of plug-in unit discharging method and electric terminal - Google Patents

Abstract

The invention discloses a plug-in unloading method and an electronic terminal. Based on a user's unloading request of 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 running, a plug-in is added Unload field information. The uninstallation field information is used to indicate that the plug-in is in a state to be uninstalled, so if the uninstallation field information is read, it means that the plug-in needs to be uninstalled. Since the plug-in will be initialized at the next startup, that is, it will read all its own data for loading. Therefore, when the plug-in reads the uninstallation field information during the next startup process, it will delete the plug-in and its related files based on the uninstallation field information. Thus, the plug-in in the present invention can be uninstalled when the plug-in is started next time due to the addition of the uninstallation field information. The implementation of this method will not only affect the current use of the plug-in, but also avoid the problem that the plug-in must be closed to uninstall the plug-in. Plugins can be easily uninstalled.

Description

Plug-in uninstallation method and electronic terminal

technical field

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

Background technique

Plug-in (Plug-in, also known as addin, add-in, addon or add-on, also translated as plug-in) is a program written by an application program interface that follows certain specifications. A plug-in refers to a program that is automatically executed with the startup of the IE browser. It can only run on the system platform specified by the program, and may support multiple platforms at the same time, but it cannot run independently of the specified platform. In other words, the plug-in must be dependent on the startup of the application to be able to run. There are countless types of plug-ins. For example, some plug-ins can help users browse the Internet more conveniently or call auxiliary functions online, and some plug-ins can help users pay online and so on. For example, after installing a related plug-in, the browser can directly call the plug-in program to process a specific type of file.

In view of 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, you need to uninstall the plug-in.

At present, plug-in uninstallation is generally performed when the plug-in is not working, and when the plug-in is uninstalled during normal operation, the user will be prompted to "whether to close the plug-in" to uninstall, thus affecting the use of the currently running plug-in, resulting in the current running plug-in There is a problem that it is not easy to uninstall.

Contents 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 plug-in uninstallation method, the method comprising:

Querying the current state of the plug-in based on a user's uninstall request to uninstall the plug-in in the application program;

If it is found that the current state of the plug-in is running, 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 process of the plug-in, the plug-in and its related files are deleted based on the information in the uninstallation field.

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

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

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

Get the plugin name of said plugin;

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

Determine whether the plug-in information is empty;

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

If not, it means that the plug-in information is a plug-in that has been installed but 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, then delete the plug-in and its related files.

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

Add the uninstall field information delinfo 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 uninstallation field information specifically includes:

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

Judging whether the relevant file of the plug-in has the uninstallation field information;

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

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

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

Based on the system version number of the plug-in, delete the configuration file corresponding to the system version in the plug-in.

Preferably, 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 includes: deleting the Native file.

Preferably, after the plug-in and its related files are deleted based on the uninstallation field information, the method further includes:

Recording the unloading field information;

Delete the uninstallation field information.

Preferably, after the plug-in and its related files are deleted based on the uninstallation field information, the method further includes:

Send a broadcast notification to each process, and synchronize the latest state of the plug-in to each process.

Preferably, after the plug-in and its related files are deleted based on the uninstallation field information, the method further includes:

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

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

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

Adding a module, configured to add an uninstall field information to the plug-in if it is found that the current state of the plug-in is running, and 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 uninstallation 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 state of the plug-in.

Preferably, the electronic terminal also 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 judging module is used to judge whether the plug-in information is empty; if yes, it means that the plug-in is not installed; if not, it means that the plug-in information is a plug-in that has been installed but the current running state is unknown.

Preferably, the electronic terminal also includes:

A deletion module, configured to delete the plug-in and its related files if it is found that the current state of the plug-in is not running.

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

Preferably, the uninstallation module specifically includes:

The first loading module is used to load related files of the plug-in during the next startup of the plug-in;

The second judging module is used to judge whether the relevant file of the plug-in has the uninstallation 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 related file of the plug-in if there is no information in the uninstallation field.

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 of the plug-in.

Preferably, the uninstall module is also used to delete Native files.

Preferably, the electronic terminal also includes:

A recording module, configured to record the unloading field information;

The second deletion module is configured to delete the uninstallation 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 includes: an update module, configured to update 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 when the program is executed by a processor, the steps of the above method are realized.

Another aspect of the present invention provides a computer device, including a memory, a processor, and a computer program stored in the memory and operable on the processor, and the processor implements 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 unloading method and an electronic terminal. Based on a user's unloading request of a plug-in in an application program, the current state of the plug-in is queried; An uninstallation field information is added to the plug-in. The uninstallation field information is used to indicate that the plug-in is in a state to be uninstalled, so if the uninstallation field information is read, it means that the plug-in needs to be uninstalled. Since the plug-in will be initialized at the next startup, that is, it will read all its own data for loading. Therefore, during the next startup process of the plug-in, when the uninstallation field information is read, the plug-in and its related files will be deleted based on the uninstallation field information. Thus, the plug-in in the present invention can be uninstalled when the plug-in is started next time due to the addition of the uninstallation field information. The implementation of this method will not only affect the current use of the plug-in, but also avoid the problem that the plug-in must be closed to uninstall the plug-in. Plugins can be easily uninstalled.

Furthermore, the existing way of uninstalling plug-ins is actually to use the "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 and cause a freeze phenomenon. However, the present invention directly adopts the method of deleting the plug-in and its related files, and all relevant information of the plug-in will be deleted, so the memory occupation is less and the system operation will not be affected.

The above description is only an overview of the technical solution of the present invention. In order to better understand the technical means of the present invention, it can be implemented according to the contents of the description, and in order to make the above and other purposes, features and advantages of the present invention more obvious and understandable , the specific embodiments of the present invention are enumerated below.

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 embodiment. The drawings are only for the purpose of illustrating a preferred embodiment and are not to be considered as limiting the invention. Also throughout the drawings, the same reference numerals are used to designate the same components. In the attached picture:

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. Although 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 for more thorough understanding of the present disclosure and to fully convey the scope of the present disclosure to those skilled in the art.

An embodiment of the present invention provides a method for uninstalling a plug-in, which is used to solve the problem of difficult uninstallation of currently running plug-ins in the prior art.

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

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

In the embodiment of the present invention, each functional module in the related application program exists in the Replugin plug-in framework. Therefore, if a function in the application is removed, it 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 unloading request of a plug-in in an application program, the plug-in name of the plug-in will be 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 it can be returned without processing. If not, it means that the plug-in information indicates a plug-in that has been installed but whose current running state is unknown.

In the specific implementation process, 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 operation of the plug-in in the embodiment of the present invention can all be placed in the resident process, specifically through the plug-in manager (PluginManagerServer class). The uninstallation of the installed plug-in can be roughly divided into two states: the state of the plug-in running and the state of the plug-in not running.

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

Step 12: If the current state of the plug-in is found to be running, 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.

In the specific implementation process, when the plug-in has been installed and is running, in this case, because 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 Information, used to identify that the plug-in is in a state to be uninstalled, so that the plug-in can be uninstalled when it is started next time.

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

As an optional embodiment, if it is found that the current state of the plug-in is not running, then delete the plug-in and its related files. 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 uninstallation field information at the next startup. The deletion process, so the present invention does not repeat the deletion process when the plug-in is not running.

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

In the specific implementation process of deleting the plug-in and its related files based on the uninstallation field information, in the process of starting the plug-in next time, load the related files of the plug-in; determine whether the related files of the plug-in have 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 uninstall field information, load and start the plug-in based on the related files of the plug-in plugin.

Specifically, since the initialization operation of the plug-in will be executed every time the resident process performs a restart operation, which involves the management logic of the plug-in, the p.l file mentioned in the above steps not only records the uninstallation field information, 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. The meaning of management includes plug-in version upgrade and plug-in uninstallation, etc. Therefore, if the current plug-in contains the uninstallation field information delinfo, the uninstallation field information delinfo will be obtained by calling the getPendingDelete interface. Since the plug-in uninstallation 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 directly delete the plug-in and its related files, and no longer update it.

Of course, if the plug-in is not running, the plug-in and its related files will be deleted directly.

The following is a detailed introduction to the removal process of the plug-in.

During 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 of the plug-in. For example, delete the APK file of the plug-in in sequence, and delete the odex file released after the plug-in is installed. When deleting the relevant files of the plug-in, the corresponding system version number will be queried, and then the corresponding configuration file will be deleted based on the system version number.

In a specific implementation process, it is judged whether the system version of the plug-in 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, then 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 default level version, and if so, delete the plug-in and the system The configuration file corresponding to the version.

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

If it is Android 4.0 system and below, you need to delete the directory where the dex optimization is released. If there is an so library, the Native file will be deleted. In addition, you also need 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 by the plugin installation have been deleted.

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

Furthermore, 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 a timely manner. That is, after the plug-in and its related files are deleted based on the uninstallation field information, a broadcast notification will be sent to each process to synchronize the latest status of the plug-in to each process to inform 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 uninstallation 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 with various information of all plug-ins, including buffer objects such as plug-in information, PackageInfo, Resources, ComponentList, and DexClassLoader): remove uninstalled plug-ins in the save Buffer data in HashMap with all plugin information, remove plugin table snapshot, remove PackageInfo, Resources, ComponentList and DexClassLoader cache object data of unloaded plugin in memory.

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

Referring to Figure 2, the electronic terminal includes:

The query module 21 is configured to query the current state of the plug-in based on the user's uninstall request of the plug-in in an application program;

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

The uninstallation module 23 is configured to delete the plug-in and its related files based on the uninstallation field information during the next start-up 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 state 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 judging module is used to judge whether the plug-in information is empty; if yes, it means that the plug-in is not installed; if not, it means that the plug-in information is a plug-in that has been installed but the 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 it is found that the current state of the plug-in is not running.

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

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

The first loading module is used to load related files of the plug-in during the next startup of the plug-in;

The second judging module is used to judge whether the relevant file of the plug-in has the uninstallation 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 related file of the plug-in if there is no information in the uninstallation field.

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 of the plug-in.

As an optional embodiment, the uninstallation module 23 is also used to delete Native files.

As an optional embodiment, the electronic terminal further includes:

A recording module, configured to record the unloading field information;

The second deletion module is configured to delete the uninstallation 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 aforementioned embodiments, the present invention also provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the steps of any one of the aforementioned methods are implemented.

Based on the same inventive concept as in the foregoing embodiments, the present invention also provides a computer device, including a memory, a processor, and a computer program stored on the memory and operable on the processor, when the processor executes the program Implement the steps of any one 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 unloading method and an electronic terminal. Based on a user's unloading request of a plug-in in an application program, the current state of the plug-in is queried; An uninstallation field information is added to the plug-in. The uninstallation field information is used to indicate that the plug-in is in a state to be uninstalled, so if the uninstallation field information is read, it means that the plug-in needs to be uninstalled. Since the plug-in will be initialized at the next startup, that is, it will read all its own data for loading. Therefore, during the next startup process of the plug-in, when the uninstallation field information is read, the plug-in and its related files will be deleted based on the uninstallation field information. Thus, the plug-in in the present invention can be uninstalled when the plug-in is started next time due to the addition of the uninstallation field information. The implementation of this method will not only affect the current use of the plug-in, but also avoid the problem that the plug-in must be closed to uninstall the plug-in. Plugins can be easily uninstalled.

Furthermore, the existing way of uninstalling plug-ins is actually to use the "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 and cause a freeze phenomenon. However, the present invention directly adopts the method of deleting the plug-in and its related files, and all relevant information of the plug-in will be deleted, so the memory occupation is less and the system operation will not be affected.

The algorithms and displays presented herein are not inherently related to any particular computer, virtual system, or other device. Various generic systems can also be used with the teachings based on this. The structure required to construct such a system is apparent from the above description. Furthermore, the present invention is not specific to any particular programming language. It should be understood that various programming languages can be used to implement the content of the present invention described herein, and the above description of specific languages is for disclosing the best mode of the present invention.

In the description provided herein, numerous specific details are set forth. However, it is understood 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 the understanding of this description.

Similarly, it should be appreciated that in the foregoing description of exemplary embodiments of the invention, in order to streamline this disclosure and to facilitate an understanding of one or more of the various inventive aspects, various features of the invention are sometimes grouped together in a single embodiment, figure, or its description. This method of disclosure, however, is not to be interpreted as reflecting an intention that the claimed invention 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 can 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. Modules or units or components in the embodiments may be combined into one module or unit or component, and furthermore may be divided into a plurality of sub-modules or sub-units or sub-assemblies. All features disclosed in this specification (including accompanying claims, abstract and drawings) and any method or method so disclosed may be used in any combination, except that at least some of such features and/or processes or units 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, those skilled in the art will understand that although some embodiments herein include some features included in other embodiments but not others, combinations of features from different embodiments are meant 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.

The 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) can be used in practice to implement some or all functions of some or all components in the gateway, proxy server, and system according to the embodiments of the present invention. The present invention can also be implemented as an apparatus or an apparatus program (for example, a computer program and a computer program product) for performing a part or all of the methods described herein. Such a program for realizing the present invention may be stored on a computer-readable medium, or may be in the form of one or more signals. Such a signal may be downloaded from an Internet site, or provided on a carrier signal, or provided in any other form.

It should be noted that the above-mentioned embodiments illustrate rather than limit the invention, and that those skilled in the art will be able to design alternative embodiments 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 distinct elements, and by means of a suitably programmed computer. In a unit claim enumerating several means, several of these means can be embodied by one and the same item of hardware. The use of the words first, second, and third, etc. does not indicate any order. These words can be interpreted as names.

The invention discloses, A1, a plug-in unloading method, characterized in that the method includes:

Querying the current state of the plug-in based on a user's uninstall request to uninstall the plug-in in the application program;

If it is found that the current state of the plug-in is running, 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 process of the plug-in, the plug-in and its related files are deleted based on the information in the uninstallation field.

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

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

A3. The method as described in A1, wherein before the querying the current state of the plug-in, the method also includes:

Get the plugin name of said plugin;

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

Determine whether the plug-in information is empty;

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

If not, it means that the plug-in information is a plug-in that has been installed but whose current running state is unknown.

A4, the method as described in A1, is characterized in that, after the current status of the plug-in is inquired, the method also includes:

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

A5, the method as described in A1, is characterized in that, adding an uninstallation field information in the plug-in specifically includes:

Add the uninstall field information delinfo to the p.l file of the application in Json format.

A6. The method as described in A1, wherein, during the next startup of the plug-in, the plug-in and its related files are deleted based on the uninstallation field information, specifically including:

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

Judging whether the relevant file of the plug-in has the uninstallation field information;

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

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

A7. The method as described in A1, wherein the deletion of the plug-in and its related files based on the uninstallation field information specifically includes:

Based on the system version number of the plug-in, delete the configuration file corresponding to the system version in the plug-in.

A8, the method as described in A7, is characterized in that, 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 also includes: deleting the Native file .

A9. The method as described in A1, characterized in that, after the plug-in and its related files are deleted based on the uninstallation field information, the method further includes:

Recording the unloading field information;

Delete the uninstallation field information.

A10, the method as described in A1, characterized in that, after the plug-in and its related files are deleted based on the uninstallation field information, the method further includes:

Send a broadcast notification to each process, and synchronize the latest state of the plug-in to each process.

A11. The method as described in A1, wherein after deleting the plug-in and its related files based on the uninstallation field information, the method further includes:

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

B12, an electronic terminal, is characterized in that, comprises:

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

Adding a module, configured to add an uninstall field information to the plug-in if it is found that the current state of the plug-in is running, and 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 uninstallation field information during the next startup of the plug-in.

B13, the electronic terminal as described in B12, is characterized in that, the current state of described inquiry described plug-in, specifically comprises:

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

B14, the electronic terminal as described in B12, is characterized in that, described electronic terminal also 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 judging module is used to judge whether the plug-in information is empty; if yes, it means that the plug-in is not installed; if not, it means that the plug-in information is a plug-in that has been installed but the current running state is unknown.

B15, the electronic terminal as described in B12, is characterized in that, described electronic terminal also comprises:

A deletion module, configured to delete the plug-in and its related files if it is found that the current state of the plug-in is not running.

B16. The electronic terminal as described in B12, wherein the adding module is specifically configured to add the uninstallation field information delinfo to the p.l file of the application program in Json format.

B17, the electronic terminal as described in B12, is characterized in that, described unloading module specifically comprises:

The first loading module is used to load related files of the plug-in during the next startup of the plug-in;

The second judging module is used to judge whether the relevant file of the plug-in has the uninstallation 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 related file of the plug-in if there is no information in the uninstallation field.

B18. The electronic terminal as described in 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 as described in B18, is characterized in that, described unloading module is also used for deleting Native file.

B20, the electronic terminal as described in B12, is characterized in that, described electronic terminal also comprises:

A recording module, configured to record the unloading field information;

The second deletion module is configured to delete the uninstallation field information.

B21. The electronic terminal as described in B12, characterized in that the electronic terminal further includes: a synchronization module, configured to send a broadcast notification to each process, and synchronize the latest status of the plug-in to each process.

B22, the electronic terminal as described in B12, is characterized in that, described electronic terminal also 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 described in 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 operable on the processor, characterized in that, when the processor executes the program, any one of claims A1-A12 is realized The steps of the method.

Claims (10)

1. A plug-in uninstallation method, characterized in that the method comprises: Querying the current state of the plug-in based on a user's uninstall request to uninstall the plug-in in the application program; If it is found that the current state of the plug-in is running, 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 process of the plug-in, the plug-in and its related files are deleted based on the information in the uninstallation field. 2. The method according to claim 1, 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. 3. The method according to claim 1, wherein before the querying the current state of the plug-in, the method further comprises: Get the plugin name of said plugin; obtaining plug-in information based on the plug-in name of the plug-in; Determine whether the plug-in information is empty; If yes, it means that the plug-in is not installed; If not, it means that the plug-in information is a plug-in that has been installed but whose current running state is unknown. 4. The method according to claim 1, wherein after said querying the current state of said plug-in, said method further comprises: If it is found that the current state of the plug-in is not running, then delete the plug-in and its related files. 5. The method according to claim 1, wherein adding an uninstallation field information in the plug-in specifically includes: Add the uninstall field information delinfo 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 uninstallation field information specifically includes: During the next startup process of the plug-in, load the related files of the plug-in; Judging whether the relevant file of the plug-in has the uninstallation field information; If there is the uninstall field information, then delete the plug-in and its related files based on the uninstall field information; If there is no information in the uninstallation field, the plug-in is loaded and started based on the related files of the plug-in. 7. The method according to claim 1, wherein the deleting the plug-in and its related files based on the uninstallation field information specifically comprises: Based on the system version number of the plug-in, delete the configuration file corresponding to the system version in the plug-in. 8. An electronic terminal, characterized in that it comprises: A query module, configured to query the current state of the plug-in based on a user's request to uninstall the plug-in in an application program; Adding a module, configured to add an uninstall field information to the plug-in if the current state of the plug-in is found to be running, and 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 uninstallation field information during the next startup of the plug-in. 9. A computer-readable storage medium, on which a computer program is stored, wherein, when the program is executed by a processor, the steps of the method according to any one of claims 1-7 are implemented. 10. A computer device, comprising a memory, a processor, and a computer program stored on the memory and operable on the processor, characterized in that, when the processor executes the program, any one of claims 1-7 is realized. steps of the method described in the item.