If you encounter an error similar to the following: Then you should check the Silk Mobile error.log located at “C:\Users\username\AppData\Roaming\silkmobile” as the log file will show something similar to the following: Running jarsigner Command line: C:\app\user\product\11.2.0\client_3\jdk\bin\jarsigner.exe -keystore C:\Users\user\AppData\Roaming\silkmobile\apk\local.keystore -digestalg SHA1 -sigalg MD5withRSA -storepass android -keypass android C:\Users\user\AppData\Local\Temp Note that the command line above the jarsinger is being executed using a custom Oracle DB client JDK The command line output, displayed below shows how a valid command line looks when executed using the standard Sun 1.7 JDK Running jarsigner Command line: C:\Program files (x86)\java\jdk1.7.0\bin\jarsigner.exe -keystore C:\Users\user\AppData\Roaming\silkmobile\apk\local.keystore -digestalg SHA1 -sigalg MD5withRSA -storepass android -keypass android C:\Users\user\AppData\Local\Temp To resolve the issue, you need to install a supported version of Sun JDK (either version 1.6 or version 1.7) and ensure that the JAVA_HOME, JRE_HOME or bundled JRE directory has been set as a System Environment Variables on the machine.
↧
