great in simulator, blank screen on device

Getting Started Newbie Questions
#1

I am having a really frustrating issue where my game looks great in the simulator but it’s a blank screen on device. There are no errors when building, and the startup image Default.png even shows while it is starting up, but after that is just a black screen.

Does anyone have any thoughts about what could be causing this issue?

Now I realize that it’s unlikely anyone can diagnose the problem from such a vague description. I’m still stripping out what I’ve added since it last worked in order to narrow down the problem, but in the meantime I’m wondering if anyone has encountered these symptoms before and can suggest things to check. [import]uid: 12108 topic_id: 4617 reply_id: 304617[/import]

#2

Incidentally, here are a couple things I’ve tried so far that haven’t fixed it:

First I removed the build.settings and config.lua files I added.

Then I tested building “Ghosts vs. Monsters” to make sure my copy of Corona hasn’t gotten borked. That app works fine.

Next I’m planning to rename the module “continuous.lua” back to “level.lua”
Is having more than 8 letters in the name a problem? [import]uid: 12108 topic_id: 4617 reply_id: 14571[/import]

#3

Try putting this at the top of your main.lua file -

io.output():setvbuf('no')

And then when you run the app on your device make sure it is still connected to XCode, errors and print statements should then be sent to the XCode console. [import]uid: 5833 topic_id: 4617 reply_id: 14587[/import]

#4

I had a similar problem that drove me nuts. This is one possible solution:

  1. Check and double check file names of any graphics or audio resources you’re loading.
  2. Check and double check lua module file names you are importing with “require()”.
  3. Repeat from step 1

File names are NOT case sensitive in the Corona emulator but ARE case sensitive when building for the device.

I now use lowercase by default on all imported resources.

[import]uid: 11393 topic_id: 4617 reply_id: 14598[/import]

#5

Thanks for the tips guys! Turns out the issue was capitalization; the file was lower case, but the require statement was capitalized. [import]uid: 12108 topic_id: 4617 reply_id: 14625[/import]