App created in Corona stuck loading: Only Mac/ iOS devices

Hi all,

I’m currently working on a game designed for iOS devices, using corona. The game works fine on pc, it loads up the menu fine and all levels work (this is with using corona). When I run the game on a device/x code simulator/ or even corona itself it has a problem loading. The menu works perfectly fine, however once i click ‘play’ - the level is loaded up but I’m met with a the default iOS loading icon (circular thingy). The level can be seen, it’s just dimmed because of the loading screen. I can’t do anything and I’ve tried to see if the game will eventually load, but it never does.

So in short, i’m stuck loading the level.

I’ve looked around for an answer but found nothing. I’m stumped. Any ideas?

Thank you.

  1. Look at the error logs.

  2. Make sure that any files you are accessing match exactly case wise. Example: accessing foto.png for a file named Foto.png might work on some platform but will fail in others.

  3. Make sure that the plugins are configured and coded so that they are not used on unsupported platforms.

Every time I have seen this issue where it runs somewhere and doesn’t someplace else it has always been a case issue or a plugin trying to be accessed on a non-supported platform, but it could be something different. In any case for people to help you here people will probably need to see the error and at the very least the build.settings file.

  1. Look at the error logs.

  2. Make sure that any files you are accessing match exactly case wise. Example: accessing foto.png for a file named Foto.png might work on some platform but will fail in others.

  3. Make sure that the plugins are configured and coded so that they are not used on unsupported platforms.

Every time I have seen this issue where it runs somewhere and doesn’t someplace else it has always been a case issue or a plugin trying to be accessed on a non-supported platform, but it could be something different. In any case for people to help you here people will probably need to see the error and at the very least the build.settings file.