安装错误：INSTALL_PARSE_FAILED_NO_CERTIFICATES [英] Installation error: INSTALL_PARSE_FAILED_NO_CERTIFICATES

问题描述

在重复这似乎是一个很常见的投诉的风险，我觉得我有这个bug出现重大变化。

At the risk of repeating what appears to be a very common complaint, I think I have a substantial variation on this bug.

应用程序将不会从Eclipse的安装，这会出现在控制台：安装错误：INSTALL_PARSE_FAILED_NO_CERTIFICATES

The application won't install from Eclipse and this appears in the console: Installation error: INSTALL_PARSE_FAILED_NO_CERTIFICATES.

LogCat中提供了一些照明：包装com.xxx没有证书，在入境的资产/字体/ helvetica_neue.ttf;忽略！

LogCat provides some illumination: Package com.xxx has no certificates at entry assets/fonts/helvetica_neue.ttf; ignoring!

代表设备（或模拟器）认为，这个特定的文件没有签名。

Meaning that the device (or emulator) believes that this particular file wasn't signed.

提出了这一通常的解决方案是：
- 重命名有问题的文件。我们已经试过了，它再抱怨下一个文件，那么接下来，依此类推。
- 添加一个虚拟文件。试过了。它抱怨新的文件，无论它叫什么。
- 编译为超过了Android 1.6。我们编译了2.3。​​

The usual solutions proposed for this are:
- Rename the offending file. We've tried that, it then complains about the next file, then the next, and so on.
- Add a dummy file. Tried that too. It complains about the new file, regardless of what it's called.
- Compile for greater than Android 1.6. We're compiling for 2.3.

值得一提的这个只有当我们推出一个单元测试情况。我们可以安装在自己的真正的应用程序没有任何困难。我们还使用Maven，当然，Maven的Andr​​oid插件。

It's worth noting this only happens when we launch a unit test. We can install the "real" application on its own with no difficulties. We're also using Maven and, of course, the Maven Android plugin.

如果我们搞清楚我们自己，我会发布任何调查结果的任何见解或建议将是非常欢迎的，当然。

Any insights or suggestions would be very welcome and of course if we figure it out on our own I'll post any findings.

推荐答案

这是现在固定。如果有人发现自己有相同的唯一项目设置和错误的解决方案可能是有一定价值。

This is fixed now. Should someone find themselves with the same unique project setup and bug the solution may be of some value.

这个问题从我们的测试项目中的POM（包含我们的单元测试项目）我们的资源目录的配置朵朵。他们被指向的项目的资源目录被测试。这套起来应该工作，所以我要去猜测，它在Maven的Andr​​oid插件，导致资源仍然未签名的错误。

The problem stemmed from the configuration of our resource directories in the POM of our test project (the project containing our unit tests). They were pointing to the resource directories of the project being tested. This set up should work so I'm going to guess that it's a bug in the Maven Android plugin that causes the resources to remain unsigned.

因此​​，解决方法是删除引用的外部资源目录（我不能说，为什么有人那么做，但最初删除它们似乎没有任何不良影响），并配置以标准方式的资源目录（以作为一个例子的Maven插件项目的原型与测试提供的POM）。

So the solution was to remove the references to external resource directories (I can't say why it was done that way initially but removing them appears to have no ill effects) and configure the resource directories in the standard way (taking as an example the POM provided by the maven plugin project archetype with tests).

这篇关于安装错误：INSTALL_PARSE_FAILED_NO_CERTIFICATES的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！