Page 1 of 1
Unable to build for Android (apk Preparation failed)
Posted: Fri Feb 14, 2014 11:10 am
by Peter@multidesk.se
I'm trying to build my project for Android, which was originally built for iOS. I have now saved the project under a new name and configured as a standalone for Android. But after that, I get the "Unable to build: apk Preparation failed" message. I have tried to delete the file "debug.keystore" under the folder. android but it does not help. I have also updated the android SDK and instalerat Android 2.2 - 4.3 (API 8 through 18), but it made no difference. However, I can build old projects that are built for android from the beginning, so there is basically nothing wrong with my paths or settings. What should I do?
I gratefully accept any help in solving this annoying problem.
/ / / Peter
Re: Unable to build for Android (apk Preparation failed)
Posted: Fri Feb 14, 2014 2:24 pm
by james8
Peter - in the signing options if you try "Sign for development only" does that work? Does it only fail when you try to build an APK and sign it with a key? You mentioned that some of your old projects work ok ... is there something in your stack that's for iOS only that's preventing it from being built possibly?
Re: Unable to build for Android (apk Preparation failed)
Posted: Fri Feb 14, 2014 2:30 pm
by LCNeil
Hi Peter,
This does sound stack related. If possible you could send your stack to
support@runrev.com and we will happily take a look at it for you.
Kind Regards,
Neil Roger
--
RunRev Support Team ~
http://www.runrev.com
-
Re: Unable to build for Android (apk Preparation failed)
Posted: Wed May 07, 2014 4:43 pm
by ludo
Hello,
I'ved a same problem with one stack (with others stacks all is fine) and on different computers.
I found that is a folder of pictures which cause the bug. I remove specials chars from the name of files "&.()", limit their length but it's the same.
Finally, i've made the files executables (chmod +x) and it's work !
[Edit : no, it doesn't work because no images was added in the standalone ![/edit]
[edit2] Finally it's was others specials chars like accents which causes the bug.