Cannot Build For Android (Build Error 5) Corona.get

Solar2D Android
#41

Can you deauthorize and try again?

#42

That Fixed it. Thanks Rob.

#43

I have been getting a Build Error 5 ever time I try it in the last 16 hours.  Anyone else?

#44

Can you deauthorize and try again?

#45

That Fixed it. Thanks Rob.

#46

I get the same error :frowning: I deauthorized already but it did not help! Building for iOS worked fine a few hours ago, I am using the newest daily build - 1170

#47

I get the same error :frowning: I deauthorized already but it did not help! Building for iOS worked fine a few hours ago, I am using the newest daily build - 1170

#48

Same Problem now for Android and iOS. Latest release and already tried deauth.

#49

I’m sorry reported late.
Folder name using the Japanese was the cause in my case.
C: \ Users \ xxxxx
It was resolved After correcting in alphabetical folder names.

(This post has been translated into English Japanese at Google)

#50

i m having problems with my build

at first it builded the app but when I installed it on my Android all I got was a black screen

now its giving me null build error #5 and i need the app build

I m using 2013.1202 builds i really need help

i already tried deauthorizing nothing happened

#51

Are there any errors in your console log (for the simulator regarding your build error) and on device regrading your black screen?

If you don’t know how to see those messages, please read:

http://www.coronalabs.com/blog/2013/07/09/tutorial-basic-debugging/

#52

Same Problem now for Android and iOS. Latest release and already tried deauth.

#53

I’m sorry reported late.
Folder name using the Japanese was the cause in my case.
C: \ Users \ xxxxx
It was resolved After correcting in alphabetical folder names.

(This post has been translated into English Japanese at Google)

#54

I just encountered Build Error #5 null, and the cause of it was I’d dragged an old copy of one of my maps, that happened to be a lua file, into my workspace.  Corona tries to compile all lua scripts in the directory, and I guess in my case there was a syntax error in the file since I didn’t intend for it to be compiled.  (Although that didn’t stop it from running in Simulator, since my code does not actually require the offending file)

Still, I agree “Build Error #5 null” could be a little more specific.  From what the first search results returned, I’d assumed the server was down or something.

#55

If there is one skill that every Corona SDK developer needs, it’s knowing to look at your console log as described in the blog post above.  The console log is where all the errors get printed and should be the first place anyone looks to see why things are not right.

#56

Yes, thanks Rob.  I read your post, and that is what caused me to look there and find the cause of my problem.  In my defense, the reason I did not look there initially was that some other window was covering it up. :ph34r:

#57

i m having problems with my build

at first it builded the app but when I installed it on my Android all I got was a black screen

now its giving me null build error #5 and i need the app build

I m using 2013.1202 builds i really need help

i already tried deauthorizing nothing happened

#58

Are there any errors in your console log (for the simulator regarding your build error) and on device regrading your black screen?

If you don’t know how to see those messages, please read:

http://www.coronalabs.com/blog/2013/07/09/tutorial-basic-debugging/

#59

I just encountered Build Error #5 null, and the cause of it was I’d dragged an old copy of one of my maps, that happened to be a lua file, into my workspace.  Corona tries to compile all lua scripts in the directory, and I guess in my case there was a syntax error in the file since I didn’t intend for it to be compiled.  (Although that didn’t stop it from running in Simulator, since my code does not actually require the offending file)

Still, I agree “Build Error #5 null” could be a little more specific.  From what the first search results returned, I’d assumed the server was down or something.

#60

If there is one skill that every Corona SDK developer needs, it’s knowing to look at your console log as described in the blog post above.  The console log is where all the errors get printed and should be the first place anyone looks to see why things are not right.