Sorry if this sounds like ranting, but Its ridiculous that I cant run my game on my phone (Nexus 5) because of a bug in the sdk that was fixed months ago. (http://forums.coronalabs.com/topic/42581-black-screen-loading-hello-world-sample-app-on-android-20132099/page-2)
I was going to pay for a year of basic once I got farther into it but now I’m a bit annoyed. These major bug fixes should be released into the SDK much earlier.
Is my only option to shell out 200$ for a year of basic?
Are you using the new 2014.2189 public release?
yes I am, but whenever i try to use this, my screen goes blank (but not in the sim)
local background = display.newImageRect( "background.jpg", display.contentWidth, display.contentHeight ) background.anchorX = 0 background.anchorY = 0
Is there a way to test for errors on my smartphone itself?
Im going to go ahead and support the SDK. I have managed to fix it, it was actually my fault! The bug was a matter of a .JPG extension (instead of .jpg). I’ll make sure to watch out for this in the future.
Remember, smartphones’ oses are usually case sensitive when it comes to files.
Read also
http://coronalabs.com/blog/2013/07/09/tutorial-basic-debugging/
Also, when you see black screen always make application error (due to bad code) the first culprit.
Everyone, when getting black screens on their devices should always check their console logs for errors and warnings. This is one of the most critical skills needed for success with mobile development. Please read this tutorial on basic debugging. It will save you plenty of grief.
http://coronalabs.com/blog/2013/07/09/tutorial-basic-debugging/
Agreed Rob, I guess diving straight into the SDK and creating something so fast made me forget about the corona console! I’ll be using print to debug for now on. Amazing work on the SDK. I used it last year and I had to drop it because of random cross-platform issues. But It seems to be mostly resolved now !
I had the exact same problem. First 2 years ago, and then some days ago.
It was easier the first time because i was using Xcode, but now im using Windows and i’ve spent 2 days trying to figure what was wrong. I had a hard time trying to debug my app and get a log of the device . Finally it ended up being a “.PNG” file. In those cases you just open it and save it again, deleting the .PNG extension and saving as png, for example.
It feels awsome to know it was just that, and to know how to get a log now… but i think it’s a fixeable error (even if its a user problem, corona might be able to fix it in the build process?)
We can’t fix it because the OS allows apps to open files regardless of the case. You tell me to open “xyz.png” and we ask the OS can we open “xyz.png” and it says "Sure you can, here is “xyz.PNG”. But on the device, it goes “there is no xyz.png”.
Rob
Are you using the new 2014.2189 public release?
yes I am, but whenever i try to use this, my screen goes blank (but not in the sim)
local background = display.newImageRect( "background.jpg", display.contentWidth, display.contentHeight ) background.anchorX = 0 background.anchorY = 0
Is there a way to test for errors on my smartphone itself?
Im going to go ahead and support the SDK. I have managed to fix it, it was actually my fault! The bug was a matter of a .JPG extension (instead of .jpg). I’ll make sure to watch out for this in the future.
Remember, smartphones’ oses are usually case sensitive when it comes to files.
Read also
http://coronalabs.com/blog/2013/07/09/tutorial-basic-debugging/
Also, when you see black screen always make application error (due to bad code) the first culprit.
Everyone, when getting black screens on their devices should always check their console logs for errors and warnings. This is one of the most critical skills needed for success with mobile development. Please read this tutorial on basic debugging. It will save you plenty of grief.
http://coronalabs.com/blog/2013/07/09/tutorial-basic-debugging/
Agreed Rob, I guess diving straight into the SDK and creating something so fast made me forget about the corona console! I’ll be using print to debug for now on. Amazing work on the SDK. I used it last year and I had to drop it because of random cross-platform issues. But It seems to be mostly resolved now !
I had the exact same problem. First 2 years ago, and then some days ago.
It was easier the first time because i was using Xcode, but now im using Windows and i’ve spent 2 days trying to figure what was wrong. I had a hard time trying to debug my app and get a log of the device . Finally it ended up being a “.PNG” file. In those cases you just open it and save it again, deleting the .PNG extension and saving as png, for example.
It feels awsome to know it was just that, and to know how to get a log now… but i think it’s a fixeable error (even if its a user problem, corona might be able to fix it in the build process?)
We can’t fix it because the OS allows apps to open files regardless of the case. You tell me to open “xyz.png” and we ask the OS can we open “xyz.png” and it says "Sure you can, here is “xyz.PNG”. But on the device, it goes “there is no xyz.png”.
Rob