We're also using Maven and, of course, the Maven Android plugin.Īny insights or suggestions would be very welcome and of course if we figure it out on our own I'll post any findings. We can install the "real" application on its own with no difficulties. It's worth noting this only happens when we launch a unit test. It complains about the new file, regardless of what it's called. We've tried that, it then complains about the next file, then the next, and so on. The usual solutions proposed for this are: ![]() Meaning that the device (or emulator) believes that this particular file wasn't signed. LogCat provides some illumination: Package com.xxx has no certificates at entry assets/fonts/helvetica_neue.ttf ignoring! ![]() ![]() The application won't install from Eclipse and this appears in the console: Installation error: INSTALL_PARSE_FAILED_NO_CERTIFICATES. At the risk of repeating what appears to be a very common complaint, I think I have a substantial variation on this bug.
0 Comments
Leave a Reply. |