I cannot build an Android apk. It works in the simulator, but for some reason it doesn’t work. I have attached two snapshots of the error message box .
I’ve followed the docs and all, but to no avail.
From the screenshots I can tell you’re on Windows … which version of Windows and which version of Corona Simulator are you running?
Can you build one of the sample apps (like “HelloWorld”)?
@Perry i am using windows 8.1 x64 with the corona simulator product version 15.0.2731.0. I tried to build HelloWorldLocalized, but run into the same error (build error #12).
What version of Java are you using? Run this command in a CMD.EXE window to check:
java -version -d32I am using java version 1.8.0_66
I can think of 2 possible things that might be causing this issue.
1st, make sure that you are not running out of disk space on your C:\ drive. If you’re running low on disk space, then Corona won’t be able to generate the APK in the system’s default temp directory during the build.
2nd, you *might* be running into a digital signing issue. I’m guessing you are attempting to sign with your own keystore, right? If so, then try building with Corona’s default “debug.keystore”. You can do this in the Android build window by clicking the “Keystore” field’s “Browse” button and selecting it under the following path (assuming this is where you installed the Corona SDK)…
C:\Program Files (x86)\Corona Labs\Corona SDK\resources\debug.keystore
If it builds successfully with the “debug.keystore”, then you know there is something wrong with your keystore.
If it does *not* build successfully successfully with our “debug.keystore”, then it *might* be an issue with your project. A good way to verify this is by building one of Corona’s sample projects.
@Quick I have enough space on my drive. I made my own sign because i thought the debug wasn’t working. When trying to build the default HelloWorldLocalized with the default debug.keystore, i run into build error #12 still.
Okay, so this sounds like a system issue. Did builds use to work? If so, then think of any system updates or installs you’ve done since now and then. Such as Windows Updates, Java/JDK updates, installing new software, etc. If you did any of those things, that’s likely what broke it.
I’ve never seen anyone run into the error you’re seeing. But if I had to ***guess***, I suspect that you’ve done a Java update recently, right? Typically that works fine, but it’s possible you might have a bad installation. If so, then I recommend that you uninstall the JDK and then re-install it. Also, remember that you must use the 32-bit (x86) version of the JDK. You can use JDK 6, 7, or 8.
http://picpaste.com/49d12fa752ea9c4c2c42cbb91aafc078.PNG < my snapshot.
I used the 32 bit version, still ran into the same error.
Perhaps you don’t have permission to write to your build’s destination directory?
Have a look at the build window’s “Save to Folder” field.
Try changing its destination (via the Browse button) to another directory, such as your local C:\ drive’s “Documents” or “Desktop”.
Also, try building one of Corona’s sample projects to that new destination directory because we know those will build successfully.
I looked at my permissions, i have full access to my folders. The problem is not that the project nor folders are an issue, it is that when the apk is being built, a temporary folder is made and all the project source is copied to this folder. Then corona tries to copy some kind of apk to the same folder. This is the problem, because the apk is somehow not being found. Then the build fails and the temp folder is deleted. The temp folder is in the appdata/local directory. Could this just be an installation problem?
At this point, I think the actual error message is misleading us and it’s not the real issue. It’s failing to copy over the built APK (that doesn’t exist) because the operations before it failed without displaying an error message.
Did you try changing the build folder location? I recommend that you try it.
I moved the debug.keystore and copied HelloWorldLocalized to my desktop. Then i tried to build, but still run into the same error.
I’m not sure how to help you any further then. We can’t reproduce this issue.
At this point, you have to think back on all of the things you did on your PC since last it worked and work backwards from there. Some kind of change happened on your PC broke it.
From the screenshots I can tell you’re on Windows … which version of Windows and which version of Corona Simulator are you running?
Can you build one of the sample apps (like “HelloWorld”)?
@Perry i am using windows 8.1 x64 with the corona simulator product version 15.0.2731.0. I tried to build HelloWorldLocalized, but run into the same error (build error #12).
What version of Java are you using? Run this command in a CMD.EXE window to check:
java -version -d32I am using java version 1.8.0_66
I can think of 2 possible things that might be causing this issue.
1st, make sure that you are not running out of disk space on your C:\ drive. If you’re running low on disk space, then Corona won’t be able to generate the APK in the system’s default temp directory during the build.
2nd, you *might* be running into a digital signing issue. I’m guessing you are attempting to sign with your own keystore, right? If so, then try building with Corona’s default “debug.keystore”. You can do this in the Android build window by clicking the “Keystore” field’s “Browse” button and selecting it under the following path (assuming this is where you installed the Corona SDK)…
C:\Program Files (x86)\Corona Labs\Corona SDK\resources\debug.keystore
If it builds successfully with the “debug.keystore”, then you know there is something wrong with your keystore.
If it does *not* build successfully successfully with our “debug.keystore”, then it *might* be an issue with your project. A good way to verify this is by building one of Corona’s sample projects.
@Quick I have enough space on my drive. I made my own sign because i thought the debug wasn’t working. When trying to build the default HelloWorldLocalized with the default debug.keystore, i run into build error #12 still.