I tried with new projects and sample projects. But the apk file is not signed properly.
My current environment:
Windows 7 64bit
JDK 7u15 x64
Microsoft Windows [Versione 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Tutti i diritti riservati.
C:\Users\Workstation-001>d:
D:>cd Loom
D:\Loom>cd WhackAMole
D:\Loom\WhackAMole>loom clean
Cleaning...
removing build
removing bin
creating bin
removing logs
Project Cleaned.
D:\Loom\WhackAMole>loom run --android
Checking for sdk 1.0.776
Preparing sdk files...
Copying assets to D:/Loom/WhackAMole/assets
"C:/Users/Workstation-001/.loom/sdks/1.0.776/tools/lsc"
-DassetAgentPort=12340 -DassetAgentHost=192.168.1.100
-DwaitForAssetAgent=150 -DdebuggerPort=8171 -DdebuggerHost=192.168.1.100
-DwaitForDebugger=0
LSC - JIT Compiler
[loom.compiler] SDK Path: C:\Users\Workstation-001.loom\sdks\1.0.776\
Building Main.loom with default settings
[loom.compiler] Compiling: Main
[loom.compiler] Compile Successful: .\bin\Main.loom
Packaging APK...
Re-signing APK...
Uninstalling APK...
Failure
Installing APK...
2662 KB/s (3669503 bytes in 1.346s)
pkg: /data/local/tmp/loom.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
Error type 3
Error: Activity class {co.theengine.TapAMole/co.theengine.loomdemo.LoomDemo} doe
s not exist.
[platform.network] WinSock initialized.
[loom.asset] Starting file watcher thread...
[loom.asset] o OK!
[loom.asset] Starting socket listener thread...
[loom.asset] o OK!
[loom.asset] Listening on port 12340
[loom.asset] o OK!
Currently there is a problem with JDK7 cross signing with JDK6 on Windows. Since we currently have JDK6 on our build server this will cause JDK 7 to fail to sign properly.
This is a known bug and is tracked as CLI-174. To work around it, please have JDK 6 installed and in your path when running the android packaging/deploy step in the cli.
Thanks,
-J
Solved the Sign issue... thank a lot :)
But now i have a compatibility issue. ([INSTALL_FAILED_CPU_ABI_INCOMPATIBLE])
The device is a old Samsung Galaxy Next Turbo (GT-S5570I) with modded rom.
D:\Loom>cd SignTry
D:\Loom\SignTry>loom clean
Cleaning...
removing build
removing bin
creating bin
removing logs
Project Cleaned.
D:\Loom\SignTry>loom run --android
Checking for sdk 1.0.776
Preparing sdk files...
Copying assets to D:/Loom/SignTry/assets
"C:/Users/Workstation-001/.loom/sdks/1.0.776/tools/lsc"
-DassetAgentPort=12340 -DassetAgentHost=192.168.1.100
-DwaitForAssetAgent=150 -DdebuggerPort=8171 -DdebuggerHost=192.168.1.100
-DwaitForDebugger=0
LSC - JIT Compiler
[loom.compiler] SDK Path: C:\Users\Workstation-001.loom\sdks\1.0.776\
Building Main.loom with default settings
[loom.compiler] Compiling: Main
[loom.compiler] Compile Successful: .\bin\Main.loom
Packaging APK...
Re-signing APK...
Uninstalling APK...
Failure
Installing APK...
3463 KB/s (2692175 bytes in 0.759s)
pkg: /data/local/tmp/loom.apk
Failure [INSTALL_FAILED_CPU_ABI_INCOMPATIBLE]
Error type 3
Error: Activity class {com.yourcompany.SignTry/co.theengine.loomdemo.LoomDemo} d
oes not exist.
[platform.network] WinSock initialized.
[loom.asset] Starting file watcher thread...
[loom.asset] o OK!
[loom.asset] Starting socket listener thread...
[loom.asset] o OK!
[loom.asset] Listening on port 12340
[loom.asset] o OK!
What android API is your Galaxy running, Loom currently supports API 10 and above, although we can look into supporting lower APIs if the demand is there.
-J
Gingerbread (API level 10).
Nice catch, I filed LOOM-996 to track this. I will keep this thread updated with it's progress.
-J
From what i've read, it's probably a problem with the compiler and processor. The device of which i speak has an ARMv6 processor, while by default the latest versions of the android sdk, avoid compile your code compatible with that processor. So as to take advantage of the floating-point functions have made available by the newest ARMv7.
Right. Loom includes libraries only for ARMv7
You could also add support for older CPUs?
You can however add the following line to your Application.mk to generate the secondary ARMv5/6 compatible machine code:
APP_ABI := armeabi-v7a armeabi
I'm having the same problem as in the original post.
"This is a known bug and is tracked as CLI-174. To work around it, please have JDK 6 installed and in your path when running the android packaging/deploy step in the cli."
I'm just not sure how to do the above.
EDIT: I meant to mention, I have JDK 6 installed, I'm just not sure how to set the path for loom.
MyComputer>Properties>Advanced System Settings>EnvironmentVariables and add the location of your installed JDK bin to the end of your User or System Path, mine looks like the following:
<other paths and junk>;C:\Program Files (x86)\Java\jdk1.6.0_39\bin
Alright, I added in the path. Still having the same problem though.
Here's the code:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\JRocSupreme>cd project
C:\Users\JRocSupreme\project>loom clean
Cleaning...
removing build
removing bin
creating bin
removing logs
Project Cleaned.
C:\Users\JRocSupreme\project>loom build android
Checking for sdk 1.0.776
Preparing sdk files...
Copying assets to C:/Users/JRocSupreme/project/assets
LSC - JIT Compiler
[loom.compiler] SDK Path: C:\Users\JRocSupreme.loom\sdks\1.0.776\
Building Main.loom with default settings
[loom.compiler] Compiling: Main
[loom.compiler] Compile Successful: .\bin\Main.loom
Packaging APK...
Re-signing APK...
C:\Users\JRocSupreme\project>loom android deploy
Packaging APK...
Re-signing APK...
Uninstalling APK...
Failure
Installing APK...
3258 KB/s (2689651 bytes in 0.806s)
pkg: /data/local/tmp/loom.apk
Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
C:\Users\JRocSupreme\project>
Awesome! Got it working! Thanks guys!
What did you do that finally made it work?
I believe I am having the same problem, with 'Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]'. I have the JRE 6 installed, and I added the path to the end of the line as demonstrated above, but it has not fixed the problem. Could you tell us how you finally fixed it? Thanks!
