blocks|key|1448826|text|我遇到了一个类似的问题，那是因为我试图用同一个apk的前一个版本在手机上安装一个apk，而这两个apk都没有用相同的证书签名。我的意思是，当我使用相同的证书时，我可以覆盖以前的安装，但当我在不同版本之间更改证书时，安装是不可能的。您是否在使用相同的证书？|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1448827|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had a similar issue and it was because I was trying to install an apk on a phone with a previous version of the same apk, and both apks hadn't been signed with the same certificate. I mean when I used the same certificate I was able to overwrite the previous installation, but when I changed the certificate between versions, the installation was not possible. Are you using the same certificate?

blocks|key|3769752|text|最后，我发现除了我的应用程序之外，没有任何应用程序安装成功。我将默认安装应用程序从SD卡设置为自动。这解决了它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3769753|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In the end I found out that no apps were being installed successfully, not just mine. I set the Install App default from SD card to Automatic. That fixed it.

blocks|key|1658858|text|我遇到了同样的问题，下面是如何解决它的:转到Manifest文件，并确保将"Debuggable“和"Test+Only”属性设置为false。它对我很有效:)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1658859|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same problem and here is how solved it : Go to the Manifest file and make sure you have the "Debuggable" and the "Test Only" attributes set to false. It worked for me :)

blocks|key|3769772|text|如果您有该应用程序以前版本，请先尝试擦除它，现在我的问题已经通过该方法解决了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3769773|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you have a previous version for that application try to erase it first, now my problem was solved by that method.

blocks|key|1453060|text|当我的自定义构建工具有一个bug时，我遇到了这个问题，它会使用ADT和一个针对iOS的证书(这当然不是我的第一个猜测，因为除了你应该有一个证书之外，Android证书似乎没有什么特别之处，它们只是RSA-1024证书，即使是自签名也可以，至少对于非市场安装是可以的)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1453061|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I ran into this when I had a bug with my custom build tool that would use ADT with a certificate intended for iOS (It certainly wasn't my first guess, since there doesn't seem to be anything special about the Android certificates other than only you should have one, they are just RSA-1024 certs, even self-signed is ok, at least for non-marketplace installs).

blocks|key|1658900|text|我也面临着同样的问题。问题是我的AndroidManifest.xml文件中的主要活动被写了两次。我删除了副本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1658901|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I faced with the same problem. The problem was the main activity in my AndroidManifest.xml file was written twice. I deleted the duplicate.

blocks|key|5188101|text|我知道这是一个老帖子，但对于新用户可能是有用的。我也遇到了同样的问题:我的应用程序在调试时运行得很好。当我在APK上签名时，我得到了同样的消息：“应用程序未安装”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5188102|我修复了卸载的JDK+(我使用的是jdk-6u14-windows-x64)，并安装了一个新的(jdk-6u29-windows-x64)。导出并再次签署APK后，一切正常！|5188103|继续，我的问题出在JAVA版本上。感谢先知！！|5188104|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I know this is an old post, but for new users may be useful. I had the same problem: my application worked fine while debbuging. When I signed the APK I got the same message: "Application not installed".

I fixed that uninstalled my JDK (I was using jdk-6u14-windows-x64) and installed a new one (jdk-6u29-windows-x64). After export and sign the APK again, everything was ok! 

Resuming, my problem was in JAVA version. Thank's Oracle!!

blocks|key|1658940|text|检查Android版本。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1658941|如果您正在安装非市场应用程序，并且版本不兼容，则会出现此错误。|1658942|例如:应用程序的目标是2.3.4你的设备是2.2，那么你会得到这个错误。|1658943|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Check with the Android version.

If you are installing non-market apps, and incompatible version you will get this error.

Ex: Application targetted to 2.3.4 
 Your device is 2.2
 Then you will get this error.

blocks|key|1658950|text|我也解决了这个问题，|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1658951|问题是我声明了两次我的主要活动，On作为第一个要加载的活动，我还为它指定了一个intent-filter，在它下面我再次声明了它。|1658952|只需确保您不会两次声明您的活动。|1658953|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I have also solved this issue,
The problem was that i declared my main activity twice,
On as the first activity to load and i specified also an intent-filter for it
And once again below it i declared it again .
Just make sure you don't declare your activities twice .

blocks|key|1658965|text|我也遇到了同样的问题，即App显示为正在安装，但在点击图标时不会启动。经过一番努力之后，我发现我愚蠢地在AndroidManifest文件中为我的主要启动程序活动设置了‘android:exported=’false‘……一旦我删除它，应用程序就可以正常启动。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1658966|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had the same issue, i.e. App showed up as being installed, but would not launched when the icon was tapped. After some head-banging, I found that I had stupidly placed ' android:exported="false" ' for my main launcher activity within the AndroidManifest file.... Once I removed it, the App launched fine..

blocks|key|5188148|text|如果应用程序已安装或移动到SD卡，然后USB线缆已连接，导致SD卡卸载，也会出现"Application+not+installed“错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5188149|在这种情况下，关闭USB存储或将应用程序移回内部存储可以解决问题。|5188150|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

The "Application not installed" error can also occur if the app has been installed to or moved to the SD card, and then the USB cable has been connected, causing the SD card to unmount.

Turning off USB storage or moving the app back to internal storage would fix the issue in this case.

blocks|key|5188156|text|如果您在AndroidManifest.xml中声明了两次MainActivity，就会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5188157|另一个可能的原因是:您更改了启动活动。提示:永远不要在已经发布的应用程序中这样做！在Android+Developers+blog中讨论了原因。|offset|length|5188158|entityMap|0|LINK|mutability|MUTABLE|url|http://android-developers.blogspot.com/2011/06/things-that-cannot-change.html^0|0|16|N|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

This can happen if you have your MainActivity declared twice in your AndroidManifest.xml.

Another possible reason: you changed the launch activity. Hint: never do it with already published applications! Reasons discussed in <a href="http://android-developers.blogspot.com/2011/06/things-that-cannot-change.html">Android Developers blog</a>.

blocks|key|1448899|text|我也有同样的问题。我没有意识到，即使是为了测试，也必须对应用程序进行签名。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1448900|自签名后，它安装得很好。|1448901|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had the same problem. I did not realise that an app must be signed even for testing.

After self signing it, it installed fine.

blocks|key|1658992|text|我已经用2个不同的证书签署了应用程序，所以删除旧版本和旧证书，然后重新安装新的解决了我的问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1658993|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I'd signed the app with 2 different certs, so removing the older version with the older cert and then reinstalling the new one solved the problem for me

blocks|key|1659006|text|我也遇到过这个问题。请尝试此解决方案。请确保项目的包名不同于已安装在移动电话中的以前的项目。我认为他们的名字有冲突。它在我身上很管用。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1659007|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I also encountered this issue. 
Kindly try this solution. Make sure that the package name of your project is different from your previous project that was already installed in your mobile phone. I think they get conflict in their names. It works in me.

blocks|key|5188192|text|我有相同类型的错误，这是由我的android清单XML文件中的这一行警告的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5188193|android:permission="android.permission.INSTALL_LOCATION_PROVIDER"|code-block|syntax|javascript|5188194|我删除了这行代码，它解决了我的问题。希望这能有所帮助|5188195|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I had the same type of error this was cauysed by this line in my android manifest XML file.

<pre><code>android:permission="android.permission.INSTALL_LOCATION_PROVIDER"
</code></pre>

I removed the line and it solved my issue. Hope this helps

blocks|key|5188200|text|您也可能会遇到此问题，因为您的设备制造商未授权谷歌商业应用程序，如Play+Store、YouTube、谷歌地图等。请关注this+answer来解决此问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|5188201|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/11816042/779408^0|1P|B|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

You also may encounter this issue because your device manufacturer did not license the Google commercial apps, such as Play Store, YouTube, Google Maps, etc. Follow <a href="https://stackoverflow.com/a/11816042/779408">this answer</a> to solve the problem.

blocks|key|1448922|text|如果应用程序未安装，请从SD卡中删除文件.android_secure/smdl2tmpl.asec。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1448923|如果文件管理器中的文件夹.android_secure为空，请将其从PC中删除。|1448924|entityMap^0|K|U|0|C|F|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@$9|N|A|O|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|P|8|@]|D|@]|E|$]]]|I|$]]

If application's not installing, delete the file <code>.android_secure/smdl2tmpl.asec</code> from the SD card.

If the folder <code>.android_secure</code> is empty in the file manager, delete it from the PC.

blocks|key|1453130|text|我的问题和@Lunatikzx类似。由于错误的权限标记被写为应用程序的属性：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1453131|<application
++++android:permission="android.permission.WRITE_EXTERNAL_STORAGE"
++++android:label="@string/app_name"
++++android:icon="@drawable/ic_launcher"
++++android:testOnly="false"
++++android:debuggable="true">|code-block|syntax|javascript|1453132|对我来说，修复它的是将权限标签更改为单独的标签，如下所示：|1453133|<uses-permission+android:name="android.permission.WRITE_EXTERNAL_STORAGE"+/>|1453134|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

My problem was similar to that of @Lunatikzx. Because of wrong permission tag which was written as attribute to application:

<pre><code>&lt;application
 android:permission="android.permission.WRITE_EXTERNAL_STORAGE"
 android:label="@string/app_name"
 android:icon="@drawable/ic_launcher"
 android:testOnly="false"
 android:debuggable="true"&gt;
</code></pre>

What fixed it for me was changing permission tag to separate tag like this:

<pre><code>&lt;uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" /&gt;
</code></pre>

blocks|key|5188216|text|我修复了这个问题，不是先给应用签名，也不是用Maven。我将其添加到我的构建路径中。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5188217|++++<plugin>
++++++++<groupId>com.jayway.maven.plugins.android.generation2</groupId>
++++++++<artifactId>android-maven-plugin</artifactId>
++++++++<inherited>true</inherited>
++++++++<configuration>
++++++++++++<sign>
++++++++++++++++<debug>false</debug>
++++++++++++</sign>
++++++++</configuration>
++++</plugin>|code-block|syntax|javascript|5188218|之后，我手签了我的应用程序:+jarsigner+-verbose+-sigalg+MD5withRSA+-digestalg+SHA1+-keystore+/home/myself/.android/-verbose+ase.keystore+myapp-1.0.apk+androidreleasekey|5188219|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|K|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|L|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|M|8|@]|9|@]|A|$]]|$1|I|3|-4|5|6|7|N|8|@]|9|@]|A|$]]]|J|$]]

I fixed this by not signing the app first and not with Maven. I added this to my build path.

<pre><code> &lt;plugin&gt;
 &lt;groupId&gt;com.jayway.maven.plugins.android.generation2&lt;/groupId&gt;
 &lt;artifactId&gt;android-maven-plugin&lt;/artifactId&gt;
 &lt;inherited&gt;true&lt;/inherited&gt;
 &lt;configuration&gt;
 &lt;sign&gt;
 &lt;debug&gt;false&lt;/debug&gt;
 &lt;/sign&gt;
 &lt;/configuration&gt;
 &lt;/plugin&gt;
</code></pre>

After that I signed my app by hand: jarsigner -verbose -sigalg MD5withRSA -digestalg SHA1 -keystore /home/myself/.android/release.keystore myapp-1.0.apk androidreleasekey

blocks|key|3769995|text|通过命令行创建密钥库文件|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3769996|keytool+-genkey+-alias+key_file_name.keystore+-keyalg+RSA+-validity+1000000000000000+-keystore+key_file_name.keystore|3769997|通过Eclipse导出apk，右键单击Android项目Android+Tools+>+export+Signed+Application+Package，然后给出keystore位置和密码。|offset|length|style|BOLD|3769998|这将创建签名的apk，同时apk将压缩对齐。并且可以安装。|3769999|如果您通过所有命令行，有时您可能会遇到“应用程序未安装”的错误。(使用命令行时，不仅会发生应用程序未安装错误。这也可能是其他一些原因)|3770000|entityMap^0|0|0|S|1D|0|0|0^^$0|@$1|2|3|4|5|6|7|P|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Q|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|R|8|@$F|S|G|T|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|U|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|V|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|W|8|@]|9|@]|A|$]]]|O|$]]

create keystore file through command line

keytool -genkey -alias key_file_name.keystore -keyalg RSA -validity 1000000000000000 -keystore key_file_name.keystore

export apk through Eclipse, right click on Android project Android Tools > Export Signed Application Package, then give keystore location &amp; password.

this will crate signed apk at the same time apk will be zipaligned. And installable.

If you go through command line for all, some times you may face "Application not installed" error.
(Application not installed error can happen not only, when using command line. It can be some other reasons as well)

blocks|key|1448954|text|当制作主屏幕小部件时，如果小部件XML文件在其android:configure属性中指定了不正确的活动，也会发生这种情况。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1448955|entityMap^0|N|H|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

This can also occur when making a home screen widget, and your widget XML file has an incorrect Activity specified in its <code>android:configure</code> property.

blocks|key|1659103|text|当这个问题发生在我身上时，我通过删除我的项目文件夹中的一些不必要的文件来修复它，比如keystore。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1659104|事后看来，把游戏的钥匙给别人可能是不好的。|1659105|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

When this problem happened to me, I fixed it by deleting some non-essential files that I had in my project folder, like the keystore.

In hindsight, it'd probably be bad to give people the keys to your game.

blocks|key|3770021|text|尝试在AndroidManifest.xml中进行此更改|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3770022|3770023|设置可调试为true的|unordered-list-item|3770024|签名apk|3770025|3770026|entityMap^0|3|J|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|R|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|S|8|@]|D|@]|E|$]]|$1|J|3|K|5|I|7|T|8|@]|D|@]|E|$]]|$1|L|3|-4|5|6|7|U|8|@]|D|@]|E|$]]|$1|M|3|-4|5|6|7|V|8|@]|D|@]|E|$]]]|N|$]]

try to this change in the AndroidManifest.xml:

<ul>
<li>setting debuggable to true</li>
<li>signing the apk</li>
</ul>

blocks|key|3770033|text|显然，这也可能是由于在安装之前重命名APK造成的。我想通过缩短文件名来减少用户从我们的网站上获取应用程序所需的打字量。在那之后，他们无法安装它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3770034|一旦我恢复到创建和签名包时使用的原始文件名，我就能够更新已安装的应用程序。|3770035|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Apparently this can also be caused by renaming the APK prior to installing it. I wanted to reduce the amount of typing users had to do to get the app from our web site by shortening the file name. After that, they were unable to install it.

Once I reverted to the original file name used when creating and signing the package I was able to update the installed app.

blocks|key|5188301|text|显然，这个问题有很多原因。对我来说，情况是这样的:我从Android+Studio+(v1.3.2)中部署到我的nexus7(实际设备)上。一切都很好。然后我创建了一个签名的apk并上传到我的Google+Drive上。断开连接后，我转到设置/应用程序并卸载了我的应用程序(App1)。然后我打开google驱动器，点击我的App1.apk，选择安装它(需要确保你在设置中允许安装apks+)。然后我收到一条可怕的消息"App+not+Installed“|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5188302|我的解决方案:回到设置/应用程序，滚动浏览所有的应用程序，底部的是我的App1的一个苍白版本的(注意，原来的App1按字母顺序在顶部，如上所述被删除了)。当点击苍白的版本时，它显示"Not+installed+for+this+user“。(我已经将我的连接设置为拥有多个用户)。但是在的右上角有一个三个点的按钮。我按了这个，它说“为所有用户卸载”。我这样做了，它解决了问题。我现在可以点击App1.apk，它安装得很好，没有出现错误。|offset|length|style|BOLD|5188303|entityMap^0|0|W|F|3Z|D|0^^$0|@$1|2|3|4|5|6|7|J|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|K|8|@$D|L|E|M|F|G]|$D|N|E|O|F|G]]|9|@]|A|$]]|$1|H|3|-4|5|6|7|P|8|@]|9|@]|A|$]]]|I|$]]

Clearly there are many causes of this problem. For me the situation was this: I had deployed to my nexus 7 (actual device) from within the Android Studio (v1.3.2). All worked fine. I then created a signed apk and uploaded to my Google Drive. After disconnecting my nexus from the usb, I went to the settings/apps and uninstalled my app (App1). I then opened google drive and clicked on my App1.apk and chose to install it (need to ensure you have allowed installation of apks in settings). Then I got the dreaded message "App not Installed"

Solution for me: go back into settings/apps and scroll though all apps and at the bottom was a pale version of my App1 (note the original App1 was at the top in Alphabetical order which was deleted as above). When clicking on the pale version it said "Not installed for this user". (I had set up my nexus to have more than one user). But in the top right corner there is a three dot button. I pressed this and it said "Uninstall for all users". Which I did and it fixed the problem. I was now able to click on App1.apk and it installed fine without the error.

blocks|key|1659184|text|使用Android+Studio，我之前安装了APK的未签名调试版本(Build+>+Build+APK)，在安装签名版本之前必须卸载它(Build+Variants+>+Build+Variant:+release，Build+>+Generate+Signed+APK)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1659185|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Using Android Studio, I had previously installed the unsigned debug version of the APK (Build > Build APK) and had to uninstall it before installing the signed release version (Build Variants > Build Variant: release, Build > Generate Signed APK).

blocks|key|1659209|text|我的问题是我在设备上有多个用户帐户。我删除了一个帐户上的应用程序，但它仍然安装在另一个帐户上。因此，命名空间发生冲突，无法安装。从所有用户卸载应用程序为我修复了它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1659210|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

My problem was that I have multiple user accounts on the device. I deleted the app on 1 account, but it still was installed on the other account. Thus the namespace collided and did not install. Uninstalling the app from all user fixed it for me.

blocks|key|3770163|text|对我来说，原因是我在同一部手机上使用了多个不同的构建版本：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3770164|​|3770165|📷|atomic|offset|length|3770166|3770167|发生的事情是，其中一些构建是由我构建的，另一个是由另一个开发人员发送给我的。当我有其他构建(由我构建)时，尝试安装开发人员导致了上述错误。|3770168|所以解决方法很简单:删除我手机上的所有构建(不管构建版本是什么)。然后安装我的同级发来的apk。它的效果就像一个护身符|3770169|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/7913a550d3ed8b39695b2d2a82d34c2b.png|imageAlt^0|0|0|0|1|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@$G|Z|H|10|1|11]]|A|$]]|$1|I|3|C|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|13|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|14|8|@]|9|@]|A|$]]|$1|N|3|-4|5|6|7|15|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U|V|-4]]]]

for me the cause was that i had multiple builds using different build variants on same phone: 

<a href="https://i.stack.imgur.com/gCJNd.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/gCJNd.png" alt="enter image description here"></a>

what happened was that some of these builds were built by me, another one was sent to me by another developer.. trying to install the developers while i had other builds (built by me) caused the above error.

so the fix was simple: delete all the builds on my phone (regardless of build variant).. then install the apk sent by my peer.. and it worked like a charm

blocks|key|5188374|text|在Marsmallow中，所有者和来宾用户是there.If来宾安装了相同的应用程序，我们无法在所有者中安装相同的应用程序。我修复了此问题，删除来宾中的应用程序|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5188375|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

In Marsmallow in owner and guest user is there.If guest installed the same app we can not install the same app in owner.I fixed this delete the app in guest

blocks|key|3770201|text|在我的情况下，我之前发布的应用程序已经用另一个密钥签名，所以我已经卸载了它，但在我的测试手机(LG+G4+H-818)上，2用户存在，所以以前的应用程序仍然在我的手机上安装了，而没有正确卸载！所以当我再次尝试安装它时，它失败了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3770202|所以我试着改变用户的和卸载以前的应用程序，最后应用程序正确安装。|3770203|希望它能在将来对您有所帮助:)|3770204|entityMap^0|1P|5|24|B|2H|6|0|5|5|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]|$9|O|A|P|B|C]|$9|Q|A|R|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|V|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|W|8|@]|D|@]|E|$]]]|K|$]]

In my case my previous released app had signed by another key, so I've uninstalled it, but on my test phone (LG G4 H-818) 2 users exists so previous app still installed on my phone and didn't uninstalled properly! so when I tried to install it again, it failed...

So I've tried to change user and uninstall previous app, finally app installed properly.

Hope it helps you in future :)

blocks|key|1659341|text|主要适用于旧版手机的|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1659342|我只是在我的手机上安装apk时遇到了App+not+installed错误，我的手机运行在4.4.2，也就是KitKat上，但我的朋友在他的6%2B手机上没有遇到这个错误。我尝试了其他解决方案，比如删除应用程序的旧/调试版本，因为apk是发布版本，清除调试应用程序的数据，甚至清除所有缓存的数据。然后，我终于意识到，在构建我的签名apk时，我所要做的就是选择两个签名版本。|offset|length|style|CODE|1659343|​|1659344|📷|atomic|1659345|1659346|在我之前只选择了V2+(Full+APK+Signature)，但在选择了V1+Jar+Signature之后，我能够在我的4.4.2设备上成功地安装我的签名的APK。希望这对其他人有帮助！|1659347|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/590a49d15a8d8423885704ab59360951.jpeg|imageAlt^0|0|I|H|0|0|0|1|0|0|0|8|N|11|G|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|Z|8|@$D|10|E|11|F|G]]|9|@]|A|$]]|$1|H|3|I|5|6|7|12|8|@]|9|@]|A|$]]|$1|J|3|K|5|L|7|13|8|@]|9|@$D|14|E|15|1|16]]|A|$]]|$1|M|3|I|5|6|7|17|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|18|8|@$D|19|E|1A|F|G]|$D|1B|E|1C|F|G]]|9|@]|A|$]]|$1|P|3|-4|5|6|7|1D|8|@]|9|@]|A|$]]]|Q|$R|$5|S|T|U|A|$V|W|X|-4]]]]

<h1>Primarily for older phones</h1>
I only encountered the <code>App not installed</code> error when trying to install an apk on my phone which runs on 4.4.2 aka KitKat, but my friend did not encounter this error on his phone which runs on 6+. I tried the other solutions such as removing the old/debug version of the app because the apk was a release version, clearing the debug app's data, and even clearing all of my cached data. Then, finally I realized all I had to do was select both signature versions when building my signed apk.
<a href="https://i.stack.imgur.com/XLH2G.jpg" rel="noreferrer"><img src="https://i.stack.imgur.com/XLH2G.jpg" alt="enter image description here" /></a>
Before I only had <code>V2 (Full APK Signature)</code> selected, but after selecting <code>V1 Jar Signature</code> as well, I was able to successfully install my signed APK on my 4.4.2 device. Hope this helps others!

blocks|key|3770278|text|在尝试安装应用程序时打开您的logCat。将其设置为“无过滤器”。搜索"InstallAppProgress“包标识符。如果安装失败，您应该看到“安装错误代码”。在我的例子中是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3770279|D/InstallAppProgress:+Installation+error+code:+-7|code-block|syntax|javascript|3770280|在这里，您可以使用此link查找有关特定错误代码的信息。|offset|length|3770281|entityMap|0|LINK|mutability|MUTABLE|url|http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/5.1.1_r1/android/content/pm/PackageManager.java#PackageManager.0INSTALL_FAILED_INVALID_APK^0|0|0|A|4|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|T|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|U|8|@]|9|@$I|V|J|W|1|X]]|A|$]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|A|$]]]|L|$M|$5|N|O|P|A|$Q|R]]]]

Open your logCat when trying to install the app. Set it to "No Filters". Search for "InstallAppProgress" package identifier. If the install fails you should see an "Installation error code". In my case it was 

<pre><code>D/InstallAppProgress: Installation error code: -7
</code></pre>

From here you can use this <a href="http://grepcode.com/file/repository.grepcode.com/java/ext/com.google.android/android/5.1.1_r1/android/content/pm/PackageManager.java#PackageManager.0INSTALL_FAILED_INVALID_APK" rel="nofollow noreferrer">link</a> to find information about your specific error code.

blocks|key|1453257|text|请确保考虑到以下提示：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1453258|1453259|你的build+variants和Flavors应该是相同的(安装的应用和新的)，通常，release|ordered-list-item|offset|length|style|CODE|1453260|Signature文件必须相同(*.jks文件)，您在directory|1453261|Setting或AndroidManifest中设置的版本与当前版本相比具有更大的价值(建议在|1453262|+build.gradle)|1453263|URL中设置版本正确(没有打字错误)，并且服务器可访问(+set服务/WebMethod/WIFI正在运行/可用等...)|1453264|文件下载并正确保存到所需的directory|1453265|Setting*.jks|1453266|+Data+|1453267|+Type+in+setDataAndType是否正确|1453268|1453269|entityMap^0|0|0|2|E|H|7|0|0|9|0|8|F|0|1|C|0|0|0|0|0|9|E|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|13|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|14|8|@$F|15|G|16|H|I]|$F|17|G|18|H|I]]|9|@]|A|$]]|$1|J|3|K|5|E|7|19|8|@$F|1A|G|1B|H|I]]|9|@]|A|$]]|$1|L|3|M|5|E|7|1C|8|@$F|1D|G|1E|H|I]]|9|@]|A|$]]|$1|N|3|O|5|E|7|1F|8|@$F|1G|G|1H|H|I]]|9|@]|A|$]]|$1|P|3|Q|5|E|7|1I|8|@]|9|@]|A|$]]|$1|R|3|S|5|E|7|1J|8|@]|9|@]|A|$]]|$1|T|3|U|5|E|7|1K|8|@]|9|@]|A|$]]|$1|V|3|W|5|6|7|1L|8|@]|9|@]|A|$]]|$1|X|3|Y|5|E|7|1M|8|@$F|1N|G|1O|H|I]]|9|@]|A|$]]|$1|Z|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]|$1|10|3|-4|5|6|7|1Q|8|@]|9|@]|A|$]]]|11|$]]

Make sure that these tips considered:

<ol>
<li>Your <code>build variants</code> and <code>Flavors</code> should be same(App installed and new one), usually release</li>
<li><code>Signature</code> file must be the same(*.jks file)</li>
<li>The version you set in <code>build.gradle</code> or <code>AndroidManifest</code> have greater value compared to current version(it is recommended to set version in <code>build.gradle</code>)</li>
<li>URL is correct(doesn't have typo) and server is reachable(WebService/WebMethod/WIFI is running/available and ...)</li>
<li>File downloaded completely</li>
<li>File saved correctly into desired directory</li>
<li>Setting for Data and Type in <code>setDataAndType</code> is correct</li>
</ol>

blocks|key|1659423|text|我也面临着同样的问题。在我的应用程序中有服务。即使在卸载应用程序后，服务仍在后台运行，在强制停止应用程序后，收到一条消息，表明应用程序已卸载。然后我安装了应用程序，没有任何问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1659424|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I also faced the same issue.
In my application had services in it.
The services was running in the background even after the application was uninstalled, after doing a force stop of the application, got a message saying the application was uninstalled.
Then I installed the application with out any problem.

blocks|key|3770373|text|如果您尝试了上面所有的答案，但都不起作用，那么您可能想要尝试一下：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3770374|如果你的build+variant是'debug'，那么你应该在应用程序build+gradle中的buildTypes下添加这个，以便应用程序安装在你的设备上：|offset|length|style|CODE|3770375|debug+{
++++minifyEnabled+false
}|code-block|syntax|javascript|3770376|entityMap^0|0|J|5|1E|A|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]|$D|S|E|T|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|U|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|V|8|@]|9|@]|A|$]]]|N|$]]

If you tried all the answers above and none of them worked, you might want to try this:

If your build variant is '<code>debug</code>', then you should add this under <code>buildTypes</code> in the app build gradle for the app to install on your device:

<pre><code>debug {
 minifyEnabled false
}
</code></pre>

blocks|key|1659478|text|我在playstore发布的最新应用程序中就遇到了这个问题。这个问题是MainLauncher和应用快捷键的组合。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1659479|我们已经添加了一个闪屏，并且我们的入口点是SplashActivity而不是MainActivity。因此，拥有以前版本并在主屏幕上有应用程序快捷方式的用户无法打开该应用程序。它总是说像App+not+installed吐司这样的东西。这并不是在每个启动器上都会发生(对我们来说，在Samsungs上更常见)。|1659480|在幕后，App+shortcut应该是从MainActivity到SplashActivity的无缝更新入口点。但是，由于某些原因，许多第三方发射器没有遵守它。修复方法是清除快捷方式并重新添加它。|1659481|如果你还没有在playstore中更新你的应用程序，请通过this+article。|1659482|在更新launcher活动时，要小心。|BOLD|1659483|entityMap|0|LINK|mutability|MUTABLE|url|http://andrzejchm.github.io/android/never_change_your_launcher_activity/^0|Z|C|0|L|E|12|C|2L|H|0|4|C|K|C|X|E|0|T|C|0|0|F|4|0^^$0|@$1|2|3|4|5|6|7|W|8|@$9|X|A|Y|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|Z|8|@$9|10|A|11|B|C]|$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|16|8|@$9|17|A|18|B|C]|$9|19|A|1A|B|C]|$9|1B|A|1C|B|C]]|D|@]|E|$]]|$1|J|3|K|5|6|7|1D|8|@]|D|@$9|1E|A|1F|1|1G]]|E|$]]|$1|L|3|M|5|6|7|1H|8|@$9|1I|A|1J|B|N]]|D|@]|E|$]]|$1|O|3|-4|5|6|7|1K|8|@]|D|@]|E|$]]]|P|$Q|$5|R|S|T|E|$U|V]]]]

I faced this issue with my latest app release to playstore. The issue is combination of change of <code>MainLauncher</code> and app shortcut . 

We have added a splash screen and our entry point is <code>SplashActivity</code> instead of <code>MainActivity</code>. So, people who has previous versions and have app shortcut on their home screen can't open the app. It always says something like <code>App not installed</code> toast. This doesn't happen on every launcher (For us it's more common on Samsungs). 

Behind the scenes, <code>App shortcut</code> should be seamlessly update entry point from <code>MainActivity</code> to <code>SplashActivity</code>. But, for some reason many third party launchers are not obeying it. The fix is clear the shortcut and add it again.

If you havn't update your app yet in playstore, go through <a href="http://andrzejchm.github.io/android/never_change_your_launcher_activity/" rel="nofollow noreferrer">this article</a>.

Beware when updating the launcher activity.

blocks|key|3770463|text|在我的例子中，这是因为Android+Studio3.0在从release构建变体构建的APK上设置了android:testOnly="true"。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|3770464|3770465|+https://commonsware.com/blog/2017/10/31/android-studio-3p0-flag-test-only.html|blockquote|3770466|3770467|3770468|所以运行./gradlew+assembleRelease来解决我问题|3770469|entityMap|0|LINK|mutability|MUTABLE|url|https://commonsware.com/blog/2017/10/31/android-studio-3p0-flag-test-only.html^0|U|7|1F|N|0|0|1|26|0|0|0|0|4|P|0^^$0|@$1|2|3|4|5|6|7|V|8|@$9|W|A|X|B|C]|$9|Y|A|Z|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|10|8|@]|D|@]|E|$]]|$1|G|3|H|5|I|7|11|8|@]|D|@$9|12|A|13|1|14]]|E|$]]|$1|J|3|-4|5|6|7|15|8|@]|D|@]|E|$]]|$1|K|3|-4|5|6|7|16|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|17|8|@$9|18|A|19|B|C]]|D|@]|E|$]]|$1|N|3|-4|5|6|7|1A|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U]]]]

In my case, it's because Android Studio 3.0 sets <code>android:testOnly="true"</code> on APKs that build from the <code>release</code> Build Variant. 

<blockquote>
 <a href="https://commonsware.com/blog/2017/10/31/android-studio-3p0-flag-test-only.html" rel="nofollow noreferrer">https://commonsware.com/blog/2017/10/31/android-studio-3p0-flag-test-only.html</a>
</blockquote>

So run <code>./gradlew assembleRelease</code> solve my issue

blocks|key|5188725|text|当我将我的android从2.3.2升级到3.0.1时，我遇到了这个问题。如果是这种情况，IDE将自动考虑以下几点。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5188726|1.您不能通过常规方法安装android:testOnly=为“true”的应用程序，例如通过安卓文件管理器或从网站下载|5188727|2.+2.Android在运行的APK上设置android:testOnly="true“|5188728|如果你运行你的应用程序，直接将设备连接到你的系统，apk将不会出现安装和运行问题。|5188729|如果你从build+out+put+and+debug文件夹复制了这个apk，它将永远不会安装在设备上。|5188730|Solution+:go+Build+->+Build+apk+->将apk文件共享复制到您的团队|offset|length|style|BOLD|5188731|那么你的问题就解决了。|5188732|entityMap^0|0|0|0|0|0|0|8|D|J|0|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|V|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|X|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|Y|8|@$L|Z|M|10|N|O]|$L|11|M|12|N|O]]|9|@]|A|$]]|$1|P|3|Q|5|6|7|13|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|S|$]]

I faced the issue when I update my android from 2.3.2 to 3.0.1 . If this is the case the IDE will automatically considers the following points.

1.You cannot install an app with android:testOnly="true" by conventional means, such as from an Android file manager or from a download off of a Web site

2.Android Studio sets android:testOnly="true" on APKs that are run from 

if you run your app directly connecting the device to your system, apk will install and run no problem.

if you sent this apk by copy from build out put and debug folder it will never install in the device. 

Solution :go Build ---> Build APK(s) ---> copy the apk file share to your team

then your problem will solve.

blocks|key|1449265|text|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1449266|从应用程序模块(项目主模块)的build>output>apk文件夹中删除.apk文件。|ordered-list-item|1449267|从项目根目录中删除.idea和.gradle文件夹|1449268|清理项目。|1449269|在android+studio的侧边栏中单击gradle图标，然后单击同步图标刷新所有项目。现在运行该项目，它应该可以工作。|1449270|1449271|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|-4|4|5|6|M|7|@]|8|@]|9|$]]|$1|A|3|B|4|C|6|N|7|@]|8|@]|9|$]]|$1|D|3|E|4|C|6|O|7|@]|8|@]|9|$]]|$1|F|3|G|4|C|6|P|7|@]|8|@]|9|$]]|$1|H|3|I|4|C|6|Q|7|@]|8|@]|9|$]]|$1|J|3|-4|4|5|6|R|7|@]|8|@]|9|$]]|$1|K|3|-4|4|5|6|S|7|@]|8|@]|9|$]]]|L|$]]

<ol>
<li>delete .apk file from build>output>apk folder in your app module(project main module). </li>
<li>delete .idea and .gradle folder from root of the project </li>
<li>clean the project.</li>
<li>click on gradle icon from sidebar in android studio and click sync icon to refresh all project. 
now run the project and it should work.</li>
</ol>

blocks|key|1659638|text|如果有人遇到此问题，请检查内部版本号。如果您的内部版本号小于安装的应用程序内部版本号，您的应用程序将不会安装，并且您将得到“损坏的应用程序或apk文件”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1659639|要修复它，只需增加您的内部版本号，直到它等于或大于已安装的内部版本号。|1659640|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

If someone is having this issue, check the build number. If your build number is less than the installed app build number, your app will not install and you will get the “Corrupted app or apk file”. 

To fix it just increment your build number until it is equal or greater than the installed build number.

blocks|key|3770639|text|适用于使用Android+Studio3的用户。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3770640|Suryanarayana+Reddy的答案是正确的，尽管它没有说明解决它的步骤，因此。|3770641|在应用程序标记下的AndroidManifest.xml中，添加testOnly="false"和android:debuggable="true"，如下所示：|offset|length|style|CODE|3770642|<application
++++android:allowBackup="true"
++++android:icon="@mipmap/ic_launcher"
++++android:label="@string/app_name"
++++android:roundIcon="@mipmap/ic_launcher_round"
++++android:supportsRtl="true"
++++android:theme="@style/AppTheme"
++++android:testOnly="false"
++++android:debuggable="true"
++++>|code-block|syntax|javascript|3770643|编辑|BOLD|3770644|然后在AndroidStudio的菜单栏中构建>构建APK(s)|3770645|entityMap^0|0|0|W|G|1D|P|0|0|0|2|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@$F|Y|G|Z|H|I]|$F|10|G|11|H|I]]|9|@]|A|$]]|$1|J|3|K|5|L|7|12|8|@]|9|@]|A|$M|N]]|$1|O|3|P|5|6|7|13|8|@$F|14|G|15|H|Q]]|9|@]|A|$]]|$1|R|3|S|5|6|7|16|8|@]|9|@]|A|$]]|$1|T|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|U|$]]

For those who are using Android Studio 3.

Suryanarayana Reddy's Answer is correct thought it doesn't state steps to solve it, hence.

in your AndroidManifest.xml under the application tag add <code>testOnly="false"</code> and <code>android:debuggable="true"</code> like so:

<pre><code>&lt;application
 android:allowBackup="true"
 android:icon="@mipmap/ic_launcher"
 android:label="@string/app_name"
 android:roundIcon="@mipmap/ic_launcher_round"
 android:supportsRtl="true"
 android:theme="@style/AppTheme"
 android:testOnly="false"
 android:debuggable="true"
 &gt;
</code></pre>

Edit then in AndroidStudio's menubar Build > Build APK(s)

blocks|key|1659721|text|在我的例子中，这是因为我使用的是支持库28的alpha版本。看起来谷歌将这些预发布版本标记为testOnly。如果你真的想像这样发布(例如，你想像我一样推出一个内部测试版)，你可以在你的gradle.properties文件中添加下面这行：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1659722|android.injected.testOnly=false|code-block|syntax|javascript|1659723|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

In my case it was because I was using the alpha version of support library 28. Looks like Google marks these pre release versions as testOnly. If you really want to release like this (for instance, you want to push an internal beta like I did), you can add this line to your gradle.properties file:

<pre><code>android.injected.testOnly=false
</code></pre>

blocks|key|5188955|text|在我的例子中，我删除了不需要的无用的权限|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|5188956|我只需要1+permission|5188957|<uses-permission+android:name="android.permission.ACCESS_FINE_LOCATION"+/>|code-block|syntax|javascript|5188958|并删除不需要的不需要的权限，并开始给出此错误|5188959|<uses-permission+android:name="android.permission.ACCESS_LOCATION_EXTRA_COMMANDS"+/>
<uses-permission+android:name="android.permission.INSTALL_LOCATION_PROVIDER"+/>
<uses-permission+android:name="android.permission.CONTROL_LOCATION_UPDATES"+/>|5188960|entityMap^0|F|3|0|4|C|0|0|7|F|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@$9|T|A|U|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|V|8|@$9|W|A|X|B|C]]|D|@]|E|$]]|$1|H|3|I|5|J|7|Y|8|@]|D|@]|E|$K|L]]|$1|M|3|N|5|6|7|Z|8|@$9|10|A|11|B|C]]|D|@]|E|$]]|$1|O|3|P|5|J|7|12|8|@]|D|@]|E|$K|L]]|$1|Q|3|-4|5|6|7|13|8|@]|D|@]|E|$]]]|R|$]]

In my case i removed Useless permissions that are not required

I Only Needed 1 permission

<pre><code>&lt;uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" /&gt;
</code></pre>

And remove unwanted permissions that are not required and started giving this error

<pre><code>&lt;uses-permission android:name="android.permission.ACCESS_LOCATION_EXTRA_COMMANDS" /&gt;
&lt;uses-permission android:name="android.permission.INSTALL_LOCATION_PROVIDER" /&gt;
&lt;uses-permission android:name="android.permission.CONTROL_LOCATION_UPDATES" /&gt;
</code></pre>

blocks|key|1659826|text|对我来说，在安卓9(API28)上，禁用Google+Play从play商店应用程序中保护的功能奏效了，我能够摆脱App+not+Installed错误。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|CODE|entityRanges|data|1659827|1659828|以禁用谷歌Play保护。打开"Play+Store“应用程序，轻触菜单按钮，选择"Play+Protect”选项，然后禁用"Scan+device+=>+security+threats“选项。|blockquote|1659829|1659830|entityMap^0|K|P|1L|H|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|D]]|E|@]|F|$]]|$1|G|3|-4|5|6|7|S|8|@]|E|@]|F|$]]|$1|H|3|I|5|J|7|T|8|@]|E|@]|F|$]]|$1|K|3|-4|5|6|7|U|8|@]|E|@]|F|$]]|$1|L|3|-4|5|6|7|V|8|@]|E|@]|F|$]]]|M|$]]

For me, On Android 9 (API 28), disabling Google Play Protect from play store app worked the trick, and i was able to get rid of the <code>App not Installed</code> error.

<blockquote>
 To disable Google Play Protect. Open "Play Store" application => tap
 on Menu button => select "Play Protect" option => Disable the options
 "Scan device for security threats".
</blockquote>

blocks|key|1453545|text|打开AndroidMainfest，然后在应用程序标签中添加verionCode，versionName，并确保debug+able等于false：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1453546|<?xml+version="1.0"+encoding="utf-8"?>
<manifest+xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
package="...">

<application
++++...
++++android:debuggable="false"
++++android:versionCode="1"
++++android:versionName="1.0"
++++tools:ignore="HardcodedDebugMode">
++++...
</application>|code-block|syntax|javascript|1453547|​|1453548|然后打开build.gradle+(module:app)，确保退出verionCode，versionName并对你的移动sdk进行<=：|1453549|defaultConfig+{
++++...
++++minSdkVersion+19
++++targetSdkVersion+28
++++versionCode+1
++++versionName+"1.0"
+++...
}|1453550|查看来源：https://developer.android.com/studio/publish/|offset|length|1453551|&+https://developer.android.com/studio/publish/preparing|1453552|&+https://developer.android.com/studio/publish/versioning|1453553|和https://developer.android.com/studio/publish/app-signing|1453554|entityMap|0|LINK|mutability|MUTABLE|url|https://developer.android.com/studio/publish/|1|https://developer.android.com/studio/publish/preparing|2|https://developer.android.com/studio/publish/versioning|3|https://developer.android.com/studio/publish/app-signing^0|0|0|0|0|0|5|19|0|0|2|1I|1|0|2|1J|2|0|1|1K|3|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|1B|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|1C|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1D|8|@]|9|@]|A|$]]|$1|K|3|L|5|D|7|1E|8|@]|9|@]|A|$E|F]]|$1|M|3|N|5|6|7|1F|8|@]|9|@$O|1G|P|1H|1|1I]]|A|$]]|$1|Q|3|R|5|6|7|1J|8|@]|9|@$O|1K|P|1L|1|1M]]|A|$]]|$1|S|3|T|5|6|7|1N|8|@]|9|@$O|1O|P|1P|1|1Q]]|A|$]]|$1|U|3|V|5|6|7|1R|8|@]|9|@$O|1S|P|1T|1|1U]]|A|$]]|$1|W|3|-4|5|6|7|1V|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13]]|14|$5|Z|10|11|A|$12|15]]|16|$5|Z|10|11|A|$12|17]]|18|$5|Z|10|11|A|$12|19]]]]

open AndroidMainfest then add verionCode, versionName in application tag and make sure debug able equal false:

<pre><code>&lt;?xml version="1.0" encoding="utf-8"?&gt;
&lt;manifest xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:tools="http://schemas.android.com/tools"
package="..."&gt;

&lt;application
 ...
 android:debuggable="false"
 android:versionCode="1"
 android:versionName="1.0"
 tools:ignore="HardcodedDebugMode"&gt;
 ...
&lt;/application&gt;
</code></pre>



then open build.gradle (module:app) make sure verionCode, versionName exited and minsdk &lt;= your mobile sdk:

<pre><code>defaultConfig {
 ...
 minSdkVersion 19
 targetSdkVersion 28
 versionCode 1
 versionName "1.0"
 ...
}
</code></pre>

look into sources: <a href="https://developer.android.com/studio/publish/" rel="nofollow noreferrer">https://developer.android.com/studio/publish/</a>

&amp; <a href="https://developer.android.com/studio/publish/preparing" rel="nofollow noreferrer">https://developer.android.com/studio/publish/preparing</a>

&amp; <a href="https://developer.android.com/studio/publish/versioning" rel="nofollow noreferrer">https://developer.android.com/studio/publish/versioning</a>

and <a href="https://developer.android.com/studio/publish/app-signing" rel="nofollow noreferrer">https://developer.android.com/studio/publish/app-signing</a>

blocks|key|3770865|text|我的问题是:我使用了Debug+Apk，它是我在Android+Studio中执行运行命令时生成的|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|3770866|解决方案是:使用代替而不是使用此文件，清除项目并从Android+Studio单击Build+>+Build+APK(S)。然后，您可以使用通常文件夹(app/build/output/+APK+/debug/)中生成的apk|3770867|这样生成的文件在安装时没有出现任何问题。|3770868|entityMap^0|A|Z|0|8|2|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|I|5|6|7|R|8|@]|D|@]|E|$]]|$1|J|3|-4|5|6|7|S|8|@]|D|@]|E|$]]]|K|$]]

My problem was: I used the Debug Apk, that was generated while I did the Run command from Android Studio

Solution was: Instead of using this file, clean project and click Build > Build APK(s) from Android Studio. Then you can use the generated APK from the usual folder (app/build/outputs/apk/debug/)

The file that was generated like this installed without a problem.

blocks|key|5189171|text|我以各种形式遇到过这个问题，但这次是一个新问题：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5189172|在这种情况下，我有提供商名称冲突-相同的提供商名称存在于我的应用程序和我的另一个应用程序中。|5189173|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I have encountered this issue in various forms, but this time it was a new one:

In this case, I had providers names collision - the same provider name existed in my app and another of my apps.

blocks|key|5189201|text|如果你想直接从Google+Drive安装apk，只需重新启动设备就可以解决这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5189202|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you are trying to install an apk directly from Google Drive, just restarting the device solved the issue for me.

blocks|key|5189238|text|当我要安装的设备没有足够的存储空间时，我遇到了这个"App+not+installed“错误。删除几个文件就可以安装应用程序了。奇怪的是，它没有给我一条“空间不足”的消息。(注意:我是从一个“未知”位置手动安装apk的。)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5189239|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I have experienced this "App not installed" error when the device I was installing to didn't have enough storage. Deleting a few files allowed the app to install. Odd that it didn't give me a "not enough space" message instead. (Note: I was installing an apk manually from an "unknown" location.)

blocks|key|5189276|text|有时也应该提到存储不可用，因为我遇到了这个问题，因为需要安装的设备没有足够的空间，而且系统对用户没有警示。你可以通过调试找到答案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5189277|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Sometimes storage not available is also should be mention because I face this issue because that the device that needs to be installed doesn't have enough space and also the system is not alert to the user. You can just find out because of debugging

blocks|key|5189292|text|如果您正在使用cordova，请尝试卸载之前通过cordova构建的任何应用程序。奇怪的是，这个方法解决了我的问题|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5189293|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you are using cordova try to uninstall any previous app that is build through cordova.
Strange but this method solved my problem

blocks|key|5189313|text|在我将手机从Android+Pie升级到Android+10之前，侧载调试应用程序在物理手机上进行测试之前工作得很可靠。在那之后，每次我尝试侧装应用程序时，都会出现"App+not+installed“错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5189314|根据我的AndroidManifest.xml中的警告，我从...|5189315|<application
++++android:name=".App"
++++android:allowBackup="true"+...+/>|code-block|syntax|javascript|5189316|为了..。|5189317|<application
++++android:name=".App"
++++android:allowBackup="false"+...+/>|5189318|在那之后，我可以加载我的应用程序了--一次。然后，我又遇到了同样的"App+not+installed“错误。通过将allowBackup改回true，它再次工作(至少一次)。|offset|length|style|CODE|5189319|从答案的数量和答案的变化来看，很明显，造成这个问题的原因很多。我分享这篇文章，以防对他人有所帮助。|5189320|entityMap^0|0|0|0|0|0|1M|B|1Z|4|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|Y|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|Z|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|10|8|@]|9|@]|A|$G|H]]|$1|M|3|N|5|6|7|11|8|@$O|12|P|13|Q|R]|$O|14|P|15|Q|R]]|9|@]|A|$]]|$1|S|3|T|5|6|7|16|8|@]|9|@]|A|$]]|$1|U|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|V|$]]

Sideloading debug apps for testing on a physical phone worked reliably until I upgraded the phone from Android Pie to Android 10. After that, the "App not installed" error came up every time I tried to sideload the app.

Based on a warning in my AndroidManifest.xml, I changed from...

<pre><code>&lt;application
 android:name=".App"
 android:allowBackup="true" ... /&gt;
</code></pre>

to...

<pre><code>&lt;application
 android:name=".App"
 android:allowBackup="false" ... /&gt;
</code></pre>

After that, I was able to sideload my app -- once. Then, I encountered the same "App not installed" error again. By changing <code>allowBackup</code> back to <code>true</code>, it worked again (at least once).

It is obvious from the number of answers and the variation in the answers that there are many reasons for this problem. I'm sharing this in case it helps others.

blocks|key|5189322|text|ARGHHHHH！当正确的设置是DEBUG+SDK时，我试图安装为未签名的版本APK。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|5189323|一个小时过去了。|5189324|entityMap^0|9|X|0|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|M|8|@]|D|@]|E|$]]|$1|H|3|-4|5|6|7|N|8|@]|D|@]|E|$]]]|I|$]]

ARGHHHHH! I was trying to install as Unsigned Release APK when the proper setting was DEBUG SDK.

There goes an hour.

blocks|key|1449527|text|这个答案只与使用本地库+(Android+NDK)的应用程序相关。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1449528|在我的例子中，问题是目标手机的CPU架构的jniLibs中缺少一些本地库。因此，应用程序在模拟器上工作，但在真正的手机上，我得到了“应用程序未安装”。|1449529|我最初只为x86架构复制了编译后的本地库，因此该应用程序可以在仿真器上运行。然而，缺少其他架构(x86_64、armeabi_v7a、arm64-v8a)。在将所有架构的缺失*.so文件添加到jniLibs中后，“应用程序未安装”错误消失。|1449530|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

This answer is relevant only for apps that use native libraries (Android NDK).

In my case the problem was that some native libraries were missing from jniLibs for the target phone's CPU architecture. Hence the app was working on the emulator, but on a real phone I got "App not installed".

I had originally copied the compiled native libraries only for the x86 architecture, so the app worked on the emulator. However, the other architectures were missing (x86_64, armeabi_v7a, arm64-v8a). After adding the missing *.so files for all architectures into jniLibs, the "App not installed" error went away.

blocks|key|1660219|text|我今天遇到了一个类似的问题，一开始我以为是我的SD卡损坏了它。我在许多运行Android4.4和更高版本的设备上进行了尝试，但它总是带来相同的issue.After，一些谷歌搜索和研究，我意识到我没有选择v1+jar签名，它是用于比Android7.0+nougat旧的设备，所以我通过选择两个复选框应用了这两个签名，并生成了一个签名的apk，它工作了。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1660220|​|1660221|📷|atomic|1660222|1660223|链接到solution+Android+–+App+not+installed+error+when+installing+a+signed+APK+–+How+to+Fix|1660224|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/22644a7d4224262fa710d9d69b36508f.png|imageAlt|1|LINK|MUTABLE|url|https://www.ryadel.com/en/android-app-not-installed-error-signed-apk-fix/^0|2U|8|38|H|0|0|0|1|0|0|0|C|23|1|0^^$0|@$1|2|3|4|5|6|7|11|8|@$9|12|A|13|B|C]|$9|14|A|15|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|16|8|@]|D|@]|E|$]]|$1|H|3|I|5|J|7|17|8|@]|D|@$9|18|A|19|1|1A]]|E|$]]|$1|K|3|G|5|6|7|1B|8|@]|D|@]|E|$]]|$1|L|3|M|5|6|7|1C|8|@]|D|@$9|1D|A|1E|1|1F]]|E|$]]|$1|N|3|-4|5|6|7|1G|8|@]|D|@]|E|$]]]|O|$P|$5|Q|R|S|E|$T|U|V|-4]]|W|$5|X|R|Y|E|$Z|10]]]]

I faced a similar issue today and at first i thought it was my sd card which corrupted it. I tried it on many devices running android 4.4 and up but it kept bringing the same issue.After some googling and research i realized that i didn't select the v1 jar signature which is for devices older than android 7.0 nougat so i applied both of these signatures by selecting the two check boxes and generated a signed apk and it worked.

<a href="https://i.stack.imgur.com/AQyIE.png" rel="noreferrer"><img src="https://i.stack.imgur.com/AQyIE.png" alt="enter image description here"></a>

Link to solution <a href="https://www.ryadel.com/en/android-app-not-installed-error-signed-apk-fix/" rel="noreferrer">Android – App not installed error when installing a signed APK – How to Fix</a>

blocks|key|3771261|text|如果您已经从Google+Play安装了应用程序的旧版本，并且想要测试应用程序的较新发布版本：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3771262|3771263|打开谷歌Play控制台|ordered-list-item|3771264|将您的应用程序的更新发布版本上传到阿尔法/测试版，但不要发布它！|3771265|3771266|​|3771267|📷|atomic|offset|length|3771268|3771269|您现在可以下载派生的apk:|3771270|3771271|3771272|现在就在你的手机上安装下载的派生apk。派生的apk由Google+Play使用与Android+Studio生成的发布应用程序不同的密钥重新签名。|3771273|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/7f9407d9905ed513732066ed9f8510a4.png|imageAlt|1|https://ask.qcloudimg.com/http-save/yehe-900000/bd01234858688c1760868fb9fbc4eed5.png^0|0|0|0|0|0|0|0|1|0|0|0|0|0|0|1|1|0|0^^$0|@$1|2|3|4|5|6|7|17|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|18|8|@]|9|@]|A|$]]|$1|C|3|D|5|E|7|19|8|@]|9|@]|A|$]]|$1|F|3|G|5|E|7|1A|8|@]|9|@]|A|$]]|$1|H|3|-4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|1C|8|@]|9|@]|A|$]]|$1|K|3|L|5|M|7|1D|8|@]|9|@$N|1E|O|1F|1|1G]]|A|$]]|$1|P|3|-4|5|6|7|1H|8|@]|9|@]|A|$]]|$1|Q|3|R|5|E|7|1I|8|@]|9|@]|A|$]]|$1|S|3|-4|5|6|7|1J|8|@]|9|@]|A|$]]|$1|T|3|L|5|M|7|1K|8|@]|9|@$N|1L|O|1M|1|1N]]|A|$]]|$1|U|3|V|5|6|7|1O|8|@]|9|@]|A|$]]|$1|W|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|X|$Y|$5|Z|10|11|A|$12|13|14|-4]]|15|$5|Z|10|11|A|$12|16|14|-4]]]]

In case, you have your app's older version installed from Google Play and you want to test the newer release version of your app: 

<ol>
<li>Open Google Play Console </li>
<li>Upload the newer release version of your app to Alpha / Beta, but do not release it yet! </li>
</ol>

<a href="https://i.stack.imgur.com/HNMAZ.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/HNMAZ.png" alt="enter image description here"></a> 

<ol start="3">
<li>You can now download the derived apk: 
<a href="https://i.stack.imgur.com/R6ql4.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/R6ql4.png" alt="enter image description here"></a> </li>
</ol>

Install the downloaded derived apk on your phone now. 
The derived apk is re-signed by Google Play with a different key from the release app Android Studio generates.

blocks|key|1660280|text|你应该将它保存为Debug而不是release，检查两个JAR符号，并允许从你下载它的地方安装应用程序(WhatsApp，chrome等...)|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1660281|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You should save this as Debug and not release, check the two JAR signs and also allow installing apps from where you have downloaded this (WhatsApp, chrome, etc...)

blocks|key|1453755|text|如果内部存储器中没有足够的空间，也会发生这种情况。我有500Mb的空闲空间，但还不够。像1Gb%2B一样免费试用。|type|unstyled|depth|inlineStyleRanges|offset|length|style|BOLD|entityRanges|data|1453756|entityMap^0|2|5|0^^$0|@$1|2|3|4|5|6|7|H|8|@$9|I|A|J|B|C]]|D|@]|E|$]]|$1|F|3|-4|5|6|7|K|8|@]|D|@]|E|$]]]|G|$]]

It can also happen if there is not enough space in the internal memory. I had 500Mb free, but it wasn't enough. Try free like 1Gb+.

blocks|key|3771312|text|有时是因为你的手机没有足够的空间。如果是这样的话，试着清理你的内存，为新的安装创造空间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3771313|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

Sometimes it is because you have no enough space on your phone. If so, try to clean up your memory to create space for new installations.

blocks|key|5189569|text|我遇到过类似的情况，我能够使用USB在调试模式下安装应用程序，但无法安装签名版本。我可以在其他手机上安装签名版本，但不能在我的设备上安装。无数的原因和解决方案都对我没有帮助。但我从一个解决方案中得到的一个方向是“为所有用户卸载”。我所做的是再次使用USB连接在调试模式下安装应用程序，转到应用程序详细信息并从右上角的3个点"uninstall+for+all+users“-删除调试版本。这看起来清除了所有类型的引用。我通常会执行普通的卸载。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|5189570|现在我可以在设备上获得签名的APK并安装并成功。|5189571|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had a similar situation.I was able to install app in debug mode using USB but not a signed version. I was able to install signed version on other phone, but not on my device. Numerous reasons and solutions did not help me. But one direction I got from a solution &quot;uninstall for all users&quot;.
What I did is to again install app in debug mode using USB connection, go to app details and &quot;uninstall for all users&quot; from right top 3 dots - to remove debug version. This looks like cleared all kinds of references. I usually do a normal uninstall.
Now I am able to get signed APK on the device and install and its success.

blocks|key|1449636|text|我发现，如果我在build.gradle文件中将compileSdkVersion、buildToolsVersion和targetSdkVersion都设置为默认值30来构建我的应用程序，那么该应用程序将不会安装在我的手机上。但是，如果我将它们改回版本29，它就可以工作。问题是，从SDK30开始，您需要选择V2+jar签名。有关更多信息，请参阅Why+does+the+Android+SDK+30+generate+invalid+APK+files?|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1449637|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/66128615/why-does-the-android-sdk-30-generate-invalid-apk-files^0|4U|1J|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I found that if I built my app with compileSdkVersion, buildToolsVersion, and targetSdkVersion all set to the default value of 30 in my build.gradle file, then the app would not install on my phone. However, if I changed them back down to version 29, it worked. What the issue turned out to be was that from SDK 30 onwards you need to select V2 jar signing. For more info see <a href="https://stackoverflow.com/questions/66128615/why-does-the-android-sdk-30-generate-invalid-apk-files">Why does the Android SDK 30 generate invalid APK files?</a>

blocks|key|3771369|text|我尝试了所有通常发布的方法，正要放弃，签名的事情解决了它。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3771370|找到一些应用程序，字面上写着"apk签名者“，它做到了。|3771371|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I tried all the methods that are generally posted,
Was just about to give up,
The signing thing solved it.
Found some app that literally said &quot;apk signer&quot;, and it did it.

blocks|key|1660389|text|在我的例子中，我将启动器活动声明为android:exported="false"|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1660390|<activity+android:name=".MainActivity"
++++++++++++android:exported="false">|code-block|syntax|javascript|1660391|我最近瞄准了Android12，不得不在我的清单组件中放入android:exported属性，但不知道该放什么值。将值更改为android:exported="true"起作用了。|1660392|entityMap^0|H|O|0|0|T|G|1R|N|0^^$0|@$1|2|3|4|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|F|3|G|5|H|7|R|8|@]|D|@]|E|$I|J]]|$1|K|3|L|5|6|7|S|8|@$9|T|A|U|B|C]|$9|V|A|W|B|C]]|D|@]|E|$]]|$1|M|3|-4|5|6|7|X|8|@]|D|@]|E|$]]]|N|$]]

In my case I had the declared my launcher activity as <code>android:exported=&quot;false&quot;</code>
<pre class="lang-xml prettyprint-override"><code>&lt;activity android:name=&quot;.MainActivity&quot;
 android:exported=&quot;false&quot;&gt;
</code></pre>
I recently targeted android 12 and had to put <code>android:exported</code> attribute in my manifest components, but did not know what to put as the value. changing the value to <code>android:exported=&quot;true&quot;</code> worked.

I have a program working in the Android Emulator. Every now and again I have been creating a signed .apk and exporting it to my HTC Desire to test. It has all been fine.

On my latest exported .apk I get the error message 'App not installed' when I try to install the .apk. It runs fine on the emulators.

As I have mainly been testing on the emulators and only every now and again exporting to a real phone I am not sure when this happened. What is the likely cause of it not installing on a physical phone but running fine in the emulators?

I have tried rebooting the phone &amp; removing the existing .apk, does not fix the fault.

'App not Installed' Error on Android

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

我有一个程序在Android模拟器中工作。每隔一段时间，我就会创建一个带签名的.apk，并将其导出到我想要测试的HTC上。一切都很好。在我最新导出的.apk上，当我尝试安装.apk时，收到错误消息“应用程序未安装”。它在模拟器上运行得很好。由于我主要是在模拟器上测试，只是时不时地输出到真实的手机上，我不确定这是什么时候...

问Android上出现“'App Installed”错误
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Android上出现“'App Installed”错误EN