The android documentation is clearly written.
Applications can only be replaced if the package name and signature are consistent. If only the package names are the same, attempts to replace them will be rejected due to inconsistent signatures.
The apk file generated in the bin directory in eclipse comes with a debug signature.
According to the original poster, it should be installed after exporting the apk. Exporting the apk requires customizing a signature. The two signatures are inconsistent. So the installation failed.
It may be that the signatures of the packages are inconsistent. If the signatures are consistent, check whether the version number is set correctly. A higher version can overwrite a lower version, but not vice versa.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
The android documentation is clearly written.
Applications can only be replaced if the package name and signature are consistent. If only the package names are the same, attempts to replace them will be rejected due to inconsistent signatures.
The apk file generated in the bin directory in eclipse comes with a debug signature.
According to the original poster, it should be installed after exporting the apk. Exporting the apk requires customizing a signature. The two signatures are inconsistent. So the installation failed.
We often encounter inconsistent signatures, so we must uninstall and then install again. Sometimes we need to restart the phone
It may be that the signatures of the packages are inconsistent. If the signatures are consistent, check whether the version number is set correctly. A higher version can overwrite a lower version, but not vice versa.