I'm having a problem getting the .apk file generated by the adt tool to actually install on an Android phone running 5.0.2. I think the problem is that the phone is not accepting the self-signed certificate I used to sign the file with jarsigner. Is it possible Android now requires its own certificate be used to sign the file? Clearly, apps generated with Android Studio can be deployed to the phone.
Anyway, the steps I follow to sign and install the apk are: keytool -genkey -v -keystore debug.keystore -alias TabletClient -keyalg RSA -keysize 2048 -validity 20000 jarsigner -verbose -sigalg SHA1withRSA -digestalg SHA1 -keystore debug.keystore Release\TabletClient.apk TabletClient zipalign -v 4 Release\TabletClient.apk Release\TabletClientZ.apk adb install Release\TabletClientZ.apk The error I'm getting from adb is INSTALL_PARSE_FAILED_NO_CERTIFICATES. And adb logcat shows "java.lang.SecurityException: Can not recognize a critical extension." BTW I found on StackOverflow comments indicating that Java 6 should be used to sign -- apparently Android had a problem with certificates generated using Java 7 or 8 -- so I uninstalled everything but Java 6 from my PC and did the above steps using it. Another way to ask my question is, is there an explanation somewhere of how to get the .apk file generated by adt to run on an Android phone? -- View this message in context: http://apache-flex-users.2333346.n4.nabble.com/Problem-installing-apk-on-Android-5-0-2-phone-Certificates-problem-tp12655.html Sent from the Apache Flex Users mailing list archive at Nabble.com.
