CN106406956B - Application program installation method and device - Google Patents
Application program installation method and device Download PDFInfo
- Publication number
- CN106406956B CN106406956B CN201610848611.0A CN201610848611A CN106406956B CN 106406956 B CN106406956 B CN 106406956B CN 201610848611 A CN201610848611 A CN 201610848611A CN 106406956 B CN106406956 B CN 106406956B
- Authority
- CN
- China
- Prior art keywords
- installation
- application program
- application
- reason
- signature
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/60—Software deployment
- G06F8/61—Installation
Abstract
The disclosure relates to an application program installation method, an application program installation device and a terminal. The method may include: when the application program is failed to be installed, reading an installation failure log on the terminal, wherein the installation failure log records the reason of the installation failure; and installing the application program according to the installation failure reason. According to the technical scheme, the installation failure log can be read when the App is failed to be installed, and the App is processed according to the installation failure reason of the installation failure log, so that the problem of installation failure is solved according to the installation failure reason, the installation power is improved, and the user experience is optimized.
Description
Technical Field
The present disclosure relates to the field of terminal technologies, and in particular, to an installation method and an installation device for an application program.
Background
With the development of intelligent terminals, various apps (Application programs) are also developed, but the matching degree of the Application programs and the hardware of the terminals is relatively low, so that some exceptions often occur in the process of installing the Application programs into the terminals, and the Application programs are failed to install.
In the related art, if the terminal has the condition of application program installation failure, the user is usually prompted in a simple dialog box form, in this way, the user can only know the installation failure, the problem cannot be solved, the time of the user is wasted, and the user experience is poor; similarly, the developer of the application program can only know the installation failure, but cannot further solve the problem of the installation failure.
Disclosure of Invention
In order to overcome the problems in the related art, embodiments of the present disclosure provide an installation method and an installation device for an application program, so as to provide a solution after an installation failure of the application program, improve installation power of the application program, and optimize user experience.
According to a first aspect of the embodiments of the present disclosure, there is provided an installation method of an application program, the method including:
when the application program is failed to be installed, reading an installation failure log on the terminal, wherein the installation failure log records the reason of the installation failure;
and installing the application program according to the installation failure reason.
In one embodiment, the installing the application program according to the reason for the installation failure includes:
determining the reason of the installation failure according to the installation failure log;
when the installation failure reason is that the current installation environment information does not meet the requirement, generating first feedback information carrying system operation data of the terminal;
and returning the first feedback information to an application providing end providing the application program.
In an embodiment, the method further comprises:
after the first feedback information is returned to an application providing end providing the application program, downloading an installation file of the application program, which is returned by the application providing end and is suitable for the current installation environment information;
and installing the application program based on the downloaded installation file.
In one embodiment, the installing the application program according to the reason for the installation failure includes:
determining the reason of the installation failure according to the installation failure log;
when the reason of the installation failure is that the application signature of the application program is inconsistent with the system signature of the terminal, detecting whether the terminal has the authority of modifying the application signature;
when detecting that the terminal has the authority of modifying the application signature, modifying the application signature to be consistent with the system signature;
reinstalling the application program based on the modified application signature.
In one embodiment, the installing the application program according to the reason for the installation failure includes:
determining the reason of the installation failure according to the installation failure log;
when the reason of the installation failure is that the first application signature of the application program is inconsistent with the second application signature of the application program of other installed versions, outputting confirmation information of inconsistent signature and uninstalling the application program of other versions or inconsistent signature and uninstalling the currently installed application program;
and unloading the corresponding application program according to the detected confirmation operation of the confirmation information.
In one embodiment, the installing the application program according to the reason for the installation failure includes:
determining the reason of the installation failure according to the installation failure log;
when the failure reason of installation is that functional conflict exists between the failure reason and the installed application program, determining the system function required to be called for running the application program based on the installation file;
reading an installed application program, and determining a first application program needing to call the system function;
outputting confirmation information for shielding a first function of a currently installed application program or shielding a second function of the first application program, wherein the first function and the second function are used for calling the system function;
masking the first function of the currently installed application or masking the second function of the installed application according to the detected operation.
In an embodiment, the method further comprises:
before the application program fails to be installed, downloading an installation file of the application program;
determining whether the installation file carries a virus or not;
deleting the installation file carrying the virus when the installation file is determined to carry the virus;
and when the installation file is determined not to carry the virus, installing the application program according to the installation file.
According to a second aspect of the embodiments of the present disclosure, there is provided an installation apparatus of an application, the method including:
the reading module is configured to read an installation failure log on the terminal when the application program is failed to be installed, wherein the installation failure log records the reason of the installation failure;
a first installation module configured to install the application program according to the installation failure log read by the reading module.
In one embodiment, the first mounting module comprises:
a first determining submodule configured to determine an installation failure reason according to the installation failure log;
the generating submodule is configured to generate first feedback information carrying system operation data of a terminal when the installation failure reason determined by the first determining submodule is not met by the current installation environment information;
and the return submodule is configured to return the first feedback information generated by the generation submodule to an application providing end providing the application program.
In one embodiment, the first mounting module further comprises:
the downloading submodule is configured to download the installation file of the application program, which is returned by the application providing terminal and is suitable for the current installation environment information, after the returning submodule returns the first feedback information to the application providing terminal providing the application program;
a first installation sub-module configured to install the application program based on the installation file downloaded by the download sub-module.
In one embodiment, the first mounting module comprises:
a second determining submodule configured to determine an installation failure reason from the installation failure log;
a first detection sub-module configured to detect whether the terminal has an authority to modify the application signature when the reason of the installation failure determined by the second determination sub-module is that the application signature of the application program is inconsistent with the system signature of the terminal;
a modification sub-module configured to modify the application signature to be consistent with the system signature when the first detection sub-module detects that the terminal has the authority to modify the application signature;
a second installation submodule configured to re-install the application program based on the application signature modified by the modification submodule.
In one embodiment, the first mounting module comprises:
a third determining submodule configured to determine an installation failure reason according to the installation failure log;
a first output sub-module, configured to output, when the reason for the installation failure is that the first application signature of the application program is inconsistent with the second application signature of the application program of the other installed version, a confirmation message that the signature is inconsistent, the application program of the other version is uninstalled, or the signature is inconsistent, the currently installed application program is uninstalled;
and the uninstalling submodule is configured to uninstall the corresponding application program according to the detected confirmation operation of the confirmation information.
In one embodiment, the first mounting module comprises:
a fourth determining submodule configured to determine an installation failure reason from the installation failure log;
a fifth determining submodule configured to determine, based on the installation file, a system function that needs to be called for running the application program when the installation failure reason determined by the fourth determining submodule is that there is a functional conflict with the installed application program;
the sixth determining submodule is configured to read the installed application program and determine the first application program which needs to call the system function;
a second output submodule configured to output confirmation information for masking a first function of a currently installed application program or masking a second function of the first application program, wherein the first function and the second function are used to call the system function;
a masking submodule configured to mask the first function of the currently installed application or to mask the second function of the installed application according to the detected operation.
In one embodiment, the apparatus further comprises:
a download module configured to download an installation file of an application program;
a determining module configured to determine whether the installation file carries a virus;
a deleting module configured to delete the installation file carrying the virus when it is determined that the installation file carries the virus;
and the second installation module is configured to install the application program according to the installation file when the fact that the installation file does not carry viruses is determined.
The technical scheme provided by the embodiment of the disclosure can have the following beneficial effects:
the terminal can read the installation failure log when the installation of the App fails, and the App is processed according to the installation failure reason of the installation failure log, so that the problem of installation failure is solved conveniently according to the installation failure reason, the installation power is improved, and the user experience is optimized.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
FIG. 1A is a flow chart illustrating a method of installation of an application in accordance with an exemplary embodiment.
FIG. 1B is a diagram illustrating a scenario of a method for installing an application, according to an example embodiment.
FIG. 2 is a flow diagram illustrating another method of installation of an application in accordance with an illustrative embodiment.
FIG. 3 is a flow chart illustrating yet another method of installation of an application in accordance with an illustrative embodiment.
Fig. 4 is a flowchart illustrating a further method of installing an application according to an example embodiment.
FIG. 5 is a flowchart illustrating yet another method of installing an application according to an example embodiment.
Fig. 6 is a block diagram illustrating an installation apparatus of an application according to an example embodiment.
Fig. 7 is a block diagram illustrating another application installation apparatus according to an example embodiment.
Fig. 8 is a block diagram illustrating an installation apparatus of still another application according to an exemplary embodiment.
Fig. 9 is a block diagram illustrating an installation apparatus of yet another application according to an example embodiment.
Fig. 10 is a block diagram illustrating an installation apparatus of yet another application according to an exemplary embodiment.
Fig. 11 is a block diagram illustrating an installation apparatus of yet another application according to an example embodiment.
Fig. 12 is a block diagram illustrating an installation apparatus of yet another application according to an example embodiment.
Fig. 13 is a block diagram illustrating an installation apparatus adapted for an application according to an example embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the invention, as detailed in the appended claims.
FIG. 1A is a flow diagram illustrating a method of installing an application in accordance with an illustrative embodiment, and FIG. 1B is a diagram illustrating a scenario of a method of installing an application in accordance with an illustrative embodiment; the installation method of the application program can be applied to a terminal, and the terminal in the disclosure can be any intelligent terminal with an internet access function, for example, a mobile phone, a tablet computer, a PDA (Personal Digital Assistant), and the like can be embodied. The terminal can access the router through the wireless local area network and access the server on the public network through the router. As shown in fig. 1A, the installation method of the application program includes the following steps 101-102:
in step 101, when the application program fails to be installed, an installation failure log on the terminal is read, wherein the installation failure log records the reason of the installation failure.
In one embodiment, the App may be any program installed on the terminal. When the App fails to be installed, an installation failure log is generated on the terminal, and the reason of the App installation failure is recorded in the installation failure log. In the step of the present disclosure, the system log, such as a failure report (bug report) and a log cat (log cat), may be read first, and then the installation failure log in the system log may be read.
In one embodiment, the installation failure reasons recorded in the installation failure log may include: the current installation environment of the terminal does not meet the requirements, the application signature of the App is inconsistent with the system signature of the terminal, the application signature of the currently installed App is inconsistent with the application signatures of the same App of other installed versions, and the like.
In an embodiment, prior to the step of the present disclosure, the method may further comprise:
and downloading an installation file of the App.
In the step of the disclosure, the terminal may download the installation file of the App through, for example, an application market.
It is determined whether the installation file carries a virus.
In an embodiment, the terminal may scan the installation file through an interface program provided by the server for killing viruses to determine whether the installation file carries viruses.
And when the installation file is determined to carry the virus, deleting the installation file carrying the virus.
Generating feedback information that the installation file carries viruses;
and feeding back the feedback information to an application providing end providing the application program.
In the case where it is determined that the installation file carries a virus, the terminal does not install the installation file and immediately deletes the installation file carrying the virus.
In an embodiment, the terminal further generates first feedback information that the installation file carries a virus, and returns the first feedback information to the application providing terminal to indicate the application providing terminal to off-shelf the installation file of the App, so as to prevent the installation file from infringing the terminal downloading the installation file.
And when the installation file is determined not to carry the virus, installing the App based on the installation file.
In one embodiment, when the terminal installs the App, the installation file is decompressed, and the manifest file in the decompressed file is scanned to determine whether the App needs to be given system permissions for running, for example, location information of the terminal needs to be used, information of other installed applications needs to be read, and the like.
In step 102, the application program is installed according to the reason of the installation failure.
In an embodiment, according to the installation failure reason recorded in the installation failure log, the application program is processed, for example, the failure reason is fed back to the application providing terminal providing the App, and the App is downloaded and installed again, so that the problem of installation failure can be solved, and the App is installed successfully.
In an exemplary scenario, as shown in fig. 1B, a smartphone 11 is included as a terminal, the smartphone 11 downloads an installation file of a microblog App through an application market, and the installation file of the microblog App is scanned and killed by an interface provided by a server for killing viruses, in the case where no virus is found as a result of the scan, the smartphone 11 reads the manifest file in the installation file, to determine whether the system authority needs to be granted, and output a reminder message whether the system authority is allowed to be used, when receiving the confirmation operation of the user to the reminding information, the smart phone 11 installs the installation file, and if the installation result is that the installation fails, the smart phone 11 reads the installation failure log, and processing the microblog App according to the installation failure reason recorded in the installation failure log so as to solve the problem of installation failure and realize successful installation.
Please refer to the following embodiments for how to install App.
Therefore, according to the method provided by the embodiment of the disclosure, the installation failure log can be read when the installation of the App fails, and the App is processed according to the installation failure reason of the installation failure log, so that the problem of installation failure can be solved conveniently according to the installation failure reason, the installation power is improved, and the user experience is optimized.
The technical solutions provided by the embodiments of the present disclosure are described below with specific embodiments.
FIG. 2 is a flow diagram illustrating another method of installation of an application in accordance with an illustrative embodiment; in this embodiment, by using the method provided by the embodiment of the present disclosure, an example is given by taking the reason of the failed installation as the reason that the current installation environment information does not meet the requirement, and referring to fig. 1B, as shown in fig. 2, the method includes the following steps:
in step 201, an installation failure reason is determined from the installation failure log.
In one embodiment, the terminal can determine the reason for the installation failure by reading the installation failure log.
In step 202, when the reason of the installation failure is that the current installation environment information does not meet the requirement, first feedback information carrying system operation data is generated.
In one embodiment, the current installation environment information is not satisfactory, and may include:
1) and the memory of the terminal is insufficient. When the memory of the terminal is not enough to install the App, the installation fails.
2) The terminal version required by App is higher than the current version of the terminal. In this case, the terminal cannot recognize or be compatible with the App version, and the installation fails.
3) The read-write function of the terminal is abnormal. Because the storage is mounted on the terminal, when mounting is in a problem, the read-write function of the terminal is abnormal, and data of the App cannot be normally written in when the App is installed, so that the installation fails.
In an embodiment, the system operation data includes hardware data and software data, and specifically may include:
any one or more of central processing unit operational data, memory data, thread data, cache data, peripheral operational data (e.g., sensor data, etc.).
In step 203, the first feedback information is returned to the application provider providing the application program.
In an embodiment, the first feedback information is returned to the application providing terminal, so that the application providing terminal can analyze and judge the reason and the solution of the installation failure based on the system operation data, and return the installation file matching the current installation environment information of the terminal.
In step 204, the installation file of the application program suitable for the current installation environment information returned by the application provider is downloaded.
In one embodiment, the installation file returned by the application provider is downloaded.
In step 205, the application is installed based on the downloaded installation file.
When the installation fails due to insufficient memory of the terminal, the application providing end can return an installation file with the file size matched with the memory of the terminal.
When installation fails due to the fact that the version of the terminal required by the App is higher than the current version of the terminal, the application providing end can return the required version of the terminal, namely the App installation file of the current version of the terminal.
When the installation fails due to the abnormal read-write function of the terminal, the application providing end does not return the installation file any more.
In an exemplary scenario, as shown in fig. 1B, an application providing terminal (not shown in the figure) connected to the smart phone 11 is further included, and if the installation fails due to insufficient memory of the smart phone 11, the smart phone 11 reads system operation data, including CPU operation data, memory data, and the like, carries the system operation data in the generated first feedback information, and returns the system operation data to the application providing terminal. And the application providing end receives the first feedback information, determines that the reason of the installation failure is insufficient memory according to the system operation data, reselects the microblog App installation file matched with the terminal memory, returns the installation file to the smart phone 11, and downloads and installs the installation file by the smart phone 11. And simultaneously the smart phone 11 unloads the installation files with failed installation.
In this embodiment, under the condition that the reason of the installation failure is that the current installation environment information does not meet the requirement, the system operation data is carried in the first feedback information and fed back to the application providing terminal, so that the application providing terminal can provide an installation file matched with the current installation environment information of the terminal for the terminal, and the problem of the installation failure is solved.
FIG. 3 is a flow diagram illustrating another method of installation of an application in accordance with an illustrative embodiment; in this embodiment, by using the method provided by the embodiment of the present disclosure, taking an example that an application signature of an application program is inconsistent with a system signature of a terminal due to a failure in installation, and performing an exemplary description with reference to fig. 1B, as shown in fig. 3, the method includes the following steps:
in step 301, an installation failure reason is determined from the installation failure log.
In step 302, when the reason of the installation failure is that the application signature of the application program is not consistent with the system signature of the terminal, whether the terminal has the authority to modify the application signature is detected, if so, step 303 is executed, and if it is determined that step 305 is not executed.
In an embodiment, an installation failure reason is recorded in an installation failure log, and when the installation failure reason is that an application signature of an installed App is inconsistent with a system signature of a terminal, the terminal reads a system file to detect whether the terminal and an application providing terminal providing the App sign a protocol capable of modifying the application signature, that is, whether the terminal has an authority to modify the application signature of the App.
In step 303, when the detection terminal has the right to modify the application signature, the application signature is modified to be consistent with the system signature.
In one embodiment, if the terminal determines that there is a right to modify the application signature, the application provider provides an interface for modifying the application signature through which the terminal can modify the application signature.
In step 304, the application is reinstalled based on the modified application signature.
In one embodiment, after the terminal modifies the application signature of the App to be consistent with the system signature, the problem of installation failure is solved, and therefore the App can be installed again.
In step 305, third feedback information is generated that the application signature does not coincide with the system signature.
In case the terminal does not have a modification application signature, the application provider is required to modify the application signature. Therefore, the terminal can generate third feedback information with the application signature inconsistent with the system signature, and the third feedback information carries the system signature.
In step 306, the third feedback information is returned to the application provider.
And after receiving the third feedback information, the application provider modifies the application signature to be consistent with the system signature, and returns the installation file with the modified application signature to the terminal.
In step 307, the installation file of the application program with the application signature consistent with the system signature returned by the application provider is downloaded.
And the terminal downloads the installation file of the App after the application signature is modified.
In step 308, the application is installed based on the downloaded installation file.
In one embodiment, the terminal re-installs the downloaded installation file.
In an exemplary embodiment, as shown in fig. 1B, the smart phone 11 reads the installation failure log, and determines that the reason for the installation failure is that the application signature of the installed microblog App is inconsistent with the system signature of the terminal, then the smart phone 11 reads the system file to detect whether the permission to modify the application signature exists, and if the permission exists, the smart phone 11 directly modifies the application signature of the microblog App into the system signature, so that the microblog App can be continuously installed and successfully installed. In another case, the smart phone 11 does not have the authority to modify the application signature, and then the smart phone 11 feeds back third feedback information carrying the system signature and the reason of the installation failure to the application providing terminal, so that the application providing terminal modifies the application signature, the application signature is consistent with the system signature, the microblog App installation file after the application signature is modified is returned to the smart phone 11, and the smart phone 11 downloads the installation file with the modified application signature and installs the installation file.
In the embodiment, under the condition that the reason of the installation failure is that the application signature is inconsistent with the system signature, if the terminal has the authority of modifying the application signature, the application signature is directly modified into the system signature; if the terminal does not have the authority of modifying the application signature, the system signature and the reason of the installation failure are carried in the feedback information and fed back to the application providing terminal, so that the application providing terminal can modify the system signature conveniently, and the problem of the installation failure is solved.
FIG. 4 is a flow diagram illustrating another method of installation of an application in accordance with an illustrative embodiment; in this embodiment, by using the above method provided by the embodiment of the present disclosure, taking an example that the reason for the failed installation is that the first application signature of the application is inconsistent with the second application signature of the application of the other installed version, and referring to fig. 1B for exemplary explanation, as shown in fig. 4, the method includes the following steps:
in step 401, the reason for the installation failure is determined from the installation failure log.
In an embodiment, the installation failure reason of the App is recorded in the installation failure log of the terminal.
In step 402, when the reason for the installation failure is that the first application signature of the application program is inconsistent with the second application signature of the application program of the other version already installed, the verification information of the inconsistent signature, the application program of the other version uninstalled, or the inconsistent signature, the application program currently installed is output.
In an embodiment, for an installed App, other versions of the App are already installed in a terminal, and the reason for this installation failure is that application signatures of apps are not consistent, in which case, one version of the App needs to be uninstalled, for example, the installed App needs to be uninstalled, so that the currently installed App can be installed successfully.
In step 403, the corresponding application program is uninstalled according to the detected confirmation operation for the confirmation information.
In an embodiment, for the confirmation information output by the terminal, the user may select to uninstall the currently installed App or select to uninstall the installed App, and the terminal uninstalls the corresponding App according to the selection operation of the user. If the installed App is selected to be uninstalled, the currently installed App continues to be installed after the uninstallation is completed.
In this embodiment, when the reason for the installation failure is that the first application signature of the application program is inconsistent with the second application signature of the application program of another installed version, the user is prompted to uninstall any one of the apps, so that the problem of the installation failure can be solved.
In an exemplary embodiment, as shown in fig. 1B, when the smart phone 11 reads the installation failure log, and determines that the reason of the installation failure is that the first application signature of the microblog App is inconsistent with the second application signature of the installed microblog apps of other versions, the smart phone outputs the signature that is inconsistent, unloads the microblog apps of other versions, or the signature that is inconsistent, unloads the confirmation information of the currently installed microblog App, that is, the microblog App of other versions has been previously installed on the smart phone 11, and the signature of the installed microblog App is inconsistent with the signature of the currently installed microblog App. Then, the smart phone 11 detects a confirmation operation of the user to uninstall the installed microblog App, uninstalls the corresponding installed microblog App, and continues to install the current microblog App.
FIG. 5 is a flow diagram illustrating another method of installation of an application in accordance with an illustrative embodiment; in this embodiment, by using the above method provided by the embodiment of the present disclosure, taking an example that the reason of the installation failure is a functional conflict with the installed application program and taking an example with reference to fig. 1B, as shown in fig. 5, the method includes the following steps:
in step 501, an installation failure reason is determined from the installation failure log.
In step 502, when the reason of the installation failure is that there is a function conflict with the installed application program, the system function to be called for the operation of the application program is determined based on the installation file.
In one embodiment, some apps have a function to call a system function, and when at least two apps have the function, a conflict occurs when the system function is called, thus resulting in a failure in App installation.
In step 503, the installed application is read and the installed application that needs to call the system function is determined.
In one embodiment, the terminal reads the installed App to determine the App having the function of calling the system function as the currently installed App.
In step 504, confirmation information for masking a first function of the currently installed application or masking a second function of the installed application is output, wherein the first function is a function for the currently installed application to call a system function, and the second function is a function for the installed application to call the system function.
In an embodiment, the terminal may prompt the user to shield the function of the App calling the system function from conflict.
In step 505, a first function of a currently installed application is masked or a second function of an installed application is masked according to the detected operation.
In one embodiment, the terminal masks the function of the currently installed App or the function of the installed App according to the selection operation of the user. So that the App with the current installation failure can continue to be successfully installed.
In an exemplary embodiment, as shown in fig. 1B, a smart phone 11 reads an installation failure log, determines a system function required to be called for operation of a microblog App based on an installation file when it is determined that an installation failure reason is that the microblog App has a function conflict with an installed App, then reads the installed application program, and determines a first application program required to call the system function; the smart phone 11 outputs confirmation information for shielding a first function of the microblog App or shielding a second function of the first application program, wherein the first function and the second function are both used for calling a system function; the smart phone 11 shields a first function of the microblog App according to the detected operation of the user.
In the present embodiment, when the cause of the installation failure is a functional conflict with an installed application program, the problem of the installation failure can be solved by masking the function of any App that conflicts.
Fig. 6 is a block diagram illustrating an installation apparatus of an application according to an exemplary embodiment, and as shown in fig. 6, the installation apparatus of the application includes: a reading module 610 and a first installation module 620.
The reading module 610 is configured to read an installation failure log on the terminal when the application program fails to be installed, wherein the installation failure log records the reason of the installation failure;
a first installation module 620 configured to install the application program according to the installation failure log read by the reading module 610.
Fig. 7 is a block diagram illustrating an installation apparatus of an application according to an exemplary embodiment, where as shown in fig. 7, on the basis of the embodiment shown in fig. 6, the first installation module 620 may include: a first determination submodule 621, a generation submodule 622 and a return submodule 623.
A first determining submodule 621 configured to determine an installation failure cause from the installation failure log;
the generating submodule 622 configured to generate first feedback information carrying system operation data of the terminal when the installation failure factor determined by the first determining submodule 621 is not satisfactory because of the current installation environment information;
and a returning sub-module 623 configured to return the first feedback information generated by the generating sub-module 622 to the application provider providing the application program.
Fig. 8 is a block diagram illustrating an installation apparatus of an application according to an exemplary embodiment, where, as shown in fig. 8, on the basis of the embodiment shown in fig. 7, the first installation module 620 further includes: a download sub-module 624 and a first installation sub-module 625.
The downloading submodule 624 is configured to, after the returning submodule 623 returns the first feedback information to the application provider providing the application program, download the installation file of the application program suitable for the current installation environment information, which is returned by the application provider;
a first installation sub-module 625 configured to install the application program based on the installation file downloaded by the download sub-module 624.
Fig. 9 is a block diagram illustrating an installation apparatus of an application according to an exemplary embodiment, where as shown in fig. 9, on the basis of the embodiment shown in fig. 6, the first installation module 620 may include: a second determination sub-module 626, a first detection sub-module 627, a modification sub-module 628, and a second installation sub-module 629.
A second determining submodule 626 configured to determine an installation failure reason from the installation failure log;
a first detecting sub-module 627 configured to detect whether the terminal has a right to modify the application signature when the reason for the installation failure determined by the second determining sub-module 626 is that the application signature of the application program is inconsistent with the system signature of the terminal;
a modification sub-module 628 configured to modify the application signature to be consistent with the system signature when the first detection sub-module 627 detects that the terminal has the right to modify the application signature;
a second installation sub-module 629 configured to reinstall the application based on the application signature modified by the modification sub-module 628.
Fig. 10 is a block diagram illustrating an installation apparatus of an application according to an exemplary embodiment, where as shown in fig. 10, on the basis of the embodiment shown in fig. 6, the first installation module 620 may include: a third determination submodule 6210, a first output submodule 6211 and an unloading submodule 6212.
A third determining sub-module 6210 configured to determine an installation failure cause from the installation failure log;
a first output sub-module 6211 configured to output, when the reason of the installation failure is that the first application signature of the application program is inconsistent with the second application signature of the application program of the other version already installed, the verification information that the signature is inconsistent, the application program of the other version is uninstalled, or the signature is inconsistent, the currently installed application program is uninstalled;
the uninstalling submodule 6212 is configured to uninstall the corresponding application program according to the detected confirmation operation on the confirmation information.
Fig. 11 is a block diagram illustrating an installation apparatus of an application according to an exemplary embodiment, where as shown in fig. 11, on the basis of the embodiment shown in fig. 6, the first installation module 620 may include: a fourth determination submodule 6213, a fifth determination submodule 6214, a sixth determination submodule 6215, a second output submodule 6216 and a masking submodule 6217.
A fourth determining submodule 6213 configured to determine an installation failure cause from the installation failure log;
a fifth determining sub-module 6214 configured to determine, based on the installation file, a system function that needs to be called for the operation of the application program when the reason of the installation failure determined by the fourth determining sub-module 6213 is that there is a functional conflict with the installed application program;
a sixth determining sub-module 6215 configured to read the installed application program and determine the first application program that needs to call the system function;
a second output sub-module 6216 configured to output confirmation information for masking the first function of the currently installed application or masking the second function of the first application, wherein the first function and the second function are used to call the system function;
a masking submodule 6217 configured to mask a first function of the currently installed application program or mask a second function of the installed application program according to the detected operation.
Fig. 12 is a block diagram illustrating an installation apparatus of an application according to an exemplary embodiment, where, as shown in fig. 12, the apparatus further includes, on the basis of the embodiment shown in fig. 6: a download module 630, a determination module 640, a deletion module 650, and a second installation module 660.
A download module 630 configured to download an installation file of the application program;
a determining module 640 configured to determine whether the installation file downloaded by the downloading module 630 carries a virus;
a deleting module 650 configured to delete the installation file carrying the virus when the determining module 640 determines that the installation file carries the virus;
a second installation module 660 configured to install the application according to the installation file when the determination module 640 determines that the installation file does not carry a virus.
With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.
Fig. 13 is a block diagram illustrating an installation apparatus adapted for an application according to an example embodiment. For example, apparatus 1300 may be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, an exercise device, a personal digital assistant, and the like, user device.
Referring to fig. 13, the apparatus 1300 may include one or more of the following components: a processing component 1302, a memory 1304, a power component 1306, a multimedia component 1308, an audio interface 1310, an input/output (I/O) interface 1312, a sensor component 1314, and a communication component 1316.
The processing component 1302 generally controls overall operation of the device 1300, such as operations associated with display, telephone calls, data communications, camera operations, and recording operations. The processing element 1302 may include one or more processors 1320 to execute instructions to perform all or part of the steps of the method described above. Further, the processing component 1302 can include one or more modules that facilitate interaction between the processing component 1302 and other components. For example, the processing component 1302 may include a multimedia module to facilitate interaction between the multimedia component 1308 and the processing component 1302.
The memory 1304 is configured to store various types of data to support operation at the device 1300. Examples of such data include instructions for any application or method operating on device 1300, contact data, phonebook data, messages, pictures, videos, and so forth. The memory 1304 may be implemented by any type or combination of volatile or non-volatile memory devices such as Static Random Access Memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic or optical disks.
The multimedia component 1308 includes a screen between the device 1300 and the user that provides an output interface. In some embodiments, the screen may include a Liquid Crystal Display (LCD) and a Touch Panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from a user. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundary of a touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 1308 includes a front facing camera and/or a rear facing camera. The front-facing camera and/or the back-facing camera may receive external multimedia data when the device 1300 is in an operational mode, such as a capture mode or a video mode. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
The audio interface 1310 is configured to output and/or input an audio signal. For example, the audio interface 1310 includes a Microphone (MIC) configured to receive external audio signals when the apparatus 1300 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals may further be stored in the memory 1304 or transmitted via the communication component 1316. In some embodiments, the audio interface 1310 also includes a speaker for outputting audio signals.
The I/O interface 1312 provides an interface between the processing component 1302 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to: a home button, a volume button, a start button, and a lock button.
The sensor assembly 1314 includes one or more sensors for providing various aspects of state assessment for the device 1300. For example, the sensor assembly 1314 may detect an open/closed state of the device 1300, the relative positioning of components, such as a display and keypad of the apparatus 1300, the sensor assembly 1314 may also detect a change in position of the apparatus 1300 or a component of the apparatus 1300, the presence or absence of user contact with the apparatus 1300, orientation or acceleration/deceleration of the apparatus 1300, and a change in temperature of the apparatus 1300. The sensor assembly 1314 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The sensor assembly 1314 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor assembly 1314 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
The communication component 1316 is configured to facilitate communications between the apparatus 1300 and other devices in a wired or wireless manner. The apparatus 1300 may access a wireless network based on a communication standard, such as WiFi, 2G or 3G, or a combination thereof. In an exemplary embodiment, the communication component 1316 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communications component 1316 also includes a Near Field Communications (NFC) module to facilitate short-range communications. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, infrared data association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
In an exemplary embodiment, the apparatus 1300 may be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, micro-controllers, microprocessors or other electronic components for performing the above-described methods.
In an exemplary embodiment, a non-transitory computer readable storage medium comprising instructions, such as the memory 1304 comprising instructions, executable by the processor 1320 of the apparatus 1300 to perform the method described above is also provided. For example, the non-transitory computer readable storage medium may be a ROM, a Random Access Memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, and the like.
Wherein the processor 1020 is configured to:
when the application program is failed to be installed, reading an installation failure log on the terminal, wherein the installation failure log records the reason of the installation failure;
and installing the application program according to the installation failure log.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This application is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (12)
1. A method for installing an application program, the method comprising:
reading a system log on a terminal when the application program fails to be installed; reading an installation failure log in the system log, wherein the installation failure log records the reason of the installation failure;
installing the application program according to the reason of the installation failure;
the installing the application program according to the reason of the installation failure comprises the following steps:
determining the reason of the installation failure according to the installation failure log;
when the failure reason of installation is that functional conflict exists between the failure reason and the installed application program, determining the system function required to be called for running the application program based on an installation file;
reading an installed application program, and determining a first application program needing to call the system function;
outputting confirmation information for shielding a first function of a currently installed application program or shielding a second function of the first application program, wherein the first function and the second function are used for calling the system function;
masking the first function of the currently installed application or masking the second function of the installed application according to the detected operation.
2. The method of claim 1, wherein installing the application according to the reason for the installation failure comprises:
determining the reason of the installation failure according to the installation failure log;
when the installation failure reason is that the current installation environment information does not meet the requirement, generating first feedback information carrying system operation data of the terminal;
and returning the first feedback information to an application providing end providing the application program.
3. The method of claim 2, further comprising:
after the first feedback information is returned to an application providing end providing the application program, downloading an installation file of the application program, which is returned by the application providing end and is suitable for the current installation environment information;
and installing the application program based on the downloaded installation file.
4. The method of claim 1, wherein installing the application according to the reason for the installation failure comprises:
determining the reason of the installation failure according to the installation failure log;
when the reason of the installation failure is that the application signature of the application program is inconsistent with the system signature of the terminal, detecting whether the terminal has the authority of modifying the application signature;
when detecting that the terminal has the authority of modifying the application signature, modifying the application signature to be consistent with the system signature;
reinstalling the application program based on the modified application signature.
5. The method of claim 1, wherein installing the application according to the reason for the installation failure comprises:
determining the reason of the installation failure according to the installation failure log;
when the reason of the installation failure is that the first application signature of the application program is inconsistent with the second application signature of the application program of other installed versions, outputting confirmation information of inconsistent signature and uninstalling the application program of other versions or inconsistent signature and uninstalling the currently installed application program;
and unloading the corresponding application program according to the detected confirmation operation of the confirmation information.
6. The method of claim 1, further comprising:
before the application program fails to be installed, downloading an installation file of the application program;
determining whether the installation file carries a virus or not;
deleting the installation file carrying the virus when the installation file is determined to carry the virus;
and when the installation file is determined not to carry viruses, installing the application program according to the installation file.
7. An apparatus for installing an application, the apparatus comprising:
the reading module is configured to read a system log on the terminal when the application program fails to be installed; reading an installation failure log in the system log, wherein the installation failure log records the reason of the installation failure;
a first installation module configured to install the application program according to the installation failure log read by the reading module;
the first mounting module includes:
a fourth determining submodule configured to determine an installation failure reason from the installation failure log;
a fifth determining submodule configured to determine, based on the installation file, a system function that needs to be called for running the application program when the installation failure reason determined by the fourth determining submodule is that there is a functional conflict with the installed application program;
the sixth determining submodule is configured to read the installed application program and determine the first application program which needs to call the system function;
a second output submodule configured to output confirmation information for masking a first function of a currently installed application program or masking a second function of the first application program, wherein the first function and the second function are used to call the system function;
a masking submodule configured to mask the first function of the currently installed application or to mask the second function of the installed application according to the detected operation.
8. The apparatus of claim 7, wherein the first mounting module comprises:
a first determining submodule configured to determine an installation failure reason according to the installation failure log;
the generating submodule is configured to generate first feedback information carrying system operation data of a terminal when the installation failure reason determined by the first determining submodule is not met by the current installation environment information;
and the return submodule is configured to return the first feedback information generated by the generation submodule to an application providing end providing the application program.
9. The apparatus of claim 8, wherein the first mounting module further comprises:
the downloading submodule is configured to download the installation file of the application program, which is returned by the application providing terminal and is suitable for the current installation environment information, after the returning submodule returns the first feedback information to the application providing terminal providing the application program;
a first installation sub-module configured to install the application program based on the installation file downloaded by the download sub-module.
10. The apparatus of claim 7, wherein the first mounting module comprises:
a second determining submodule configured to determine an installation failure reason from the installation failure log;
a first detection sub-module configured to detect whether the terminal has an authority to modify the application signature when the reason of the installation failure determined by the second determination sub-module is that the application signature of the application program is inconsistent with the system signature of the terminal;
a modification sub-module configured to modify the application signature to be consistent with the system signature when the first detection sub-module detects that the terminal has the authority to modify the application signature;
a second installation submodule configured to re-install the application program based on the application signature modified by the modification submodule.
11. The apparatus of claim 7, wherein the first mounting module comprises:
a third determining submodule configured to determine an installation failure reason according to the installation failure log;
a first output sub-module, configured to output, when the reason for the installation failure is that the first application signature of the application program is inconsistent with the second application signature of the application program of the other installed version, a confirmation message that the signature is inconsistent, the application program of the other version is uninstalled, or the signature is inconsistent, the currently installed application program is uninstalled;
and the uninstalling submodule is configured to uninstall the corresponding application program according to the detected confirmation operation of the confirmation information.
12. The apparatus of claim 7, further comprising:
a download module configured to download an installation file of an application program;
a determining module configured to determine whether the installation file carries a virus;
a deleting module configured to delete the installation file carrying the virus when it is determined that the installation file carries the virus;
and the second installation module is configured to install the application program according to the installation file when the fact that the installation file does not carry viruses is determined.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610848611.0A CN106406956B (en) | 2016-09-23 | 2016-09-23 | Application program installation method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201610848611.0A CN106406956B (en) | 2016-09-23 | 2016-09-23 | Application program installation method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN106406956A CN106406956A (en) | 2017-02-15 |
| CN106406956B true CN106406956B (en) | 2020-06-02 |
Family
ID=57996570
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201610848611.0A Active CN106406956B (en) | 2016-09-23 | 2016-09-23 | Application program installation method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN106406956B (en) |
Families Citing this family (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP6882492B2 (en) * | 2017-09-01 | 2021-06-02 | 株式会社日立製作所 | Software installation system, software installation method, and software installation program |
| CN111221539B (en) * | 2018-11-27 | 2023-05-05 | 阿里巴巴集团控股有限公司 | Application installation processing method and device, electronic equipment and application platform |
| CN109800126A (en) * | 2018-12-27 | 2019-05-24 | 北京奇安信科技有限公司 | The analysis method and device of patch install failure |
| CN109885317B (en) * | 2019-02-22 | 2022-08-26 | 维沃移动通信有限公司 | Information processing method, server and terminal |
| CN109918895B (en) * | 2019-03-07 | 2023-07-14 | 上海掌门科技有限公司 | Method, electronic device, and computer-readable medium for outputting data |
| CN110688125A (en) * | 2019-08-28 | 2020-01-14 | 北京浪潮数据技术有限公司 | Deployment method and system of big data platform |
| CN113282307A (en) * | 2021-06-11 | 2021-08-20 | 云宏信息科技股份有限公司 | Method, server and system for batch installation of ansable server to software |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102880935A (en) * | 2012-09-10 | 2013-01-16 | 曙光信息产业(北京)有限公司 | Method and system for managing Linux cluster software |
| CN103077059A (en) * | 2013-01-07 | 2013-05-01 | 北京播思软件技术有限公司 | Method for judging whether application is matched or not |
| CN103455418A (en) * | 2013-08-02 | 2013-12-18 | 深圳创维数字技术股份有限公司 | Intelligent terminal testing method and intelligent terminal testing device |
| CN104063660A (en) * | 2013-03-20 | 2014-09-24 | 腾讯科技（深圳）有限公司 | Virus scanning method and device as well as terminal |
| CN104331310A (en) * | 2014-10-31 | 2015-02-04 | 北京思特奇信息技术股份有限公司 | Background application one-click installation method and system |
| CN105095006A (en) * | 2015-07-21 | 2015-11-25 | 北京金山安全软件有限公司 | Method and device for repairing software installation failure |
| CN105574369A (en) * | 2015-12-14 | 2016-05-11 | 网易（杭州）网络有限公司 | Method, device and system for re-signing application program |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8589323B2 (en) * | 2005-03-04 | 2013-11-19 | Maxsp Corporation | Computer hardware and software diagnostic and report system incorporating an expert system and agents |
-
2016
- 2016-09-23 CN CN201610848611.0A patent/CN106406956B/en active Active
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN102880935A (en) * | 2012-09-10 | 2013-01-16 | 曙光信息产业(北京)有限公司 | Method and system for managing Linux cluster software |
| CN103077059A (en) * | 2013-01-07 | 2013-05-01 | 北京播思软件技术有限公司 | Method for judging whether application is matched or not |
| CN104063660A (en) * | 2013-03-20 | 2014-09-24 | 腾讯科技（深圳）有限公司 | Virus scanning method and device as well as terminal |
| CN103455418A (en) * | 2013-08-02 | 2013-12-18 | 深圳创维数字技术股份有限公司 | Intelligent terminal testing method and intelligent terminal testing device |
| CN104331310A (en) * | 2014-10-31 | 2015-02-04 | 北京思特奇信息技术股份有限公司 | Background application one-click installation method and system |
| CN105095006A (en) * | 2015-07-21 | 2015-11-25 | 北京金山安全软件有限公司 | Method and device for repairing software installation failure |
| CN105574369A (en) * | 2015-12-14 | 2016-05-11 | 网易（杭州）网络有限公司 | Method, device and system for re-signing application program |
Also Published As
| Publication number | Publication date |
|---|---|
| CN106406956A (en) | 2017-02-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN106406956B (en) | Application program installation method and device | |
| EP3168745B1 (en) | Method, device and system for application updating | |
| CN106775903B (en) | Security policy file updating method and device | |
| CN111427622B (en) | Execution method and device of script codes in application program | |
| CN107911482B (en) | Target application opening method and device | |
| CN111240694B (en) | Application detection method, application detection device and storage medium | |
| CN111538502A (en) | Installation package processing method and device, electronic equipment and storage medium | |
| CN108153540B (en) | System upgrading method, device, terminal and storage medium | |
| CN107733674B (en) | Component upgrading method and terminal | |
| CN107861666B (en) | Desktop application installation method and device | |
| CN106293683B (en) | Project compiling method and device | |
| CN112163192A (en) | root authority acquisition method, root authority acquisition device, root authority acquisition medium and electronic equipment | |
| CN107220082B (en) | Application program installation method, device and equipment | |
| CN111198706A (en) | Method for updating system function, apparatus for updating system function and storage medium | |
| CN106201634B (en) | Software installation method and device | |
| CN112733092B (en) | Information processing method and device | |
| CN112631695A (en) | Data verification method and device, electronic equipment and storage medium | |
| CN109933357B (en) | Application program upgrading method and device | |
| CN111813426A (en) | Fingerprint data processing method and device | |
| CN110377312B (en) | Software upgrading method, device and medium | |
| CN110990073B (en) | Method and device for verifying customization requirements of application program | |
| CN109726118B (en) | Application program development method and device, electronic equipment and storage medium | |
| CN113934452B (en) | Data processing method and device, electronic equipment and storage medium | |
| CN111596949B (en) | Method and device for developing application program | |
| CN107463414B (en) | Application installation method and device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |