Weird Simulator Problem: Corona Windows works great, Corona Mac won't run my app.

Solar2D General Questions/Discussion
#1

Ok I have a weird problem.

For months, I have used Corona Windows build 894 is what I have. The simulator runs my app just fine, no problems, I even have the output window and everything seems great.

Today, I installed Corona Mac build 894 on my Mac Book. It opens find, and runs all the built in sample apps, but it will not run my app that works find in the Windows simulator.

Anyone seen this problem? Or is this a basic problem and am over looking something?

I also noticed that the debug console output window does not open in Mac Corona. This doesn’t open for any of the sample apps either and I can’t seem to find a setting for this to enable it in the Mac simulator.

But more importantly, why does my app work fine in Windows, but won’t run at all in Mac? Anyone pointers on where to start looking? [import]uid: 152474 topic_id: 31077 reply_id: 331077[/import]

#2

Ok. I think I figure it out.

I still don’t know why the debugger console won’t start on the Mac, but I can manually start it. Once I manually started the console window, I was able to see the problem.

On the windows machine I made “path to assets” like this:

“/assets/gpageturn.wav”

Notice the extra “/” in front of assets.

On a Mac machine, this extra lash doesn’t work. Once I removed all my asset locations from:

“/assets/gpageturn.wav”

to

“assets/gpageturn.wav”

No more problems.

If the console debugger window had opened on it’s own, I might have figured this out sooner. But instead I still have to manually invoke the debugger on the Mac. So little lesson for the night. [import]uid: 152474 topic_id: 31077 reply_id: 124252[/import]

#3

Thanks for updating; on Windows the debugger shouldn’t open on its own I don’t believe (not a PC person) but the terminal window should - on the Mac you should launch Corona via the terminal shortcut located in the Corona SDK folder.

For the path thing, out of interest, can you leave off the initial / on PC? As I said I’m unsure on the PC side though if you have any Qs I’m happy to talk to another member of the team to try and get you some answers, just let me know.

Peach :slight_smile: [import]uid: 52491 topic_id: 31077 reply_id: 124267[/import]

#4

Ms. Pellen, yes I went through my code on the Windows Corona Simulator, and deleted the extra “/” in the front, and I had no problems in the Windows Simulator Corona. Windows doesn’t seem to care if you have the extra “/” in front or not, it works both ways.

But Mac Corona Simulator would only work after I removed the extra “/” in the front.

So obviously, since Windows works both ways, I’ll just remember not to include the “/” beginning for the path to assets so when I build on the Mac I don’t have that issue again.

Ok on the terminal window for Mac. Thanks. [import]uid: 152474 topic_id: 31077 reply_id: 124271[/import]

#5

I believe windows doesn’t care for uppercase filenames.
OSX does. [import]uid: 100901 topic_id: 31077 reply_id: 124310[/import]

#6

Thanks very much for that update - and a valid point raised by Juf Jannie - on PC you wont get uppercase/lowercase warnings if not correct, IIRC - something else to watch for as these errors can cause a “corrupted” error when trying to install on device. [import]uid: 52491 topic_id: 31077 reply_id: 124466[/import]

#7

Ok. I think I figure it out.

I still don’t know why the debugger console won’t start on the Mac, but I can manually start it. Once I manually started the console window, I was able to see the problem.

On the windows machine I made “path to assets” like this:

“/assets/gpageturn.wav”

Notice the extra “/” in front of assets.

On a Mac machine, this extra lash doesn’t work. Once I removed all my asset locations from:

“/assets/gpageturn.wav”

to

“assets/gpageturn.wav”

No more problems.

If the console debugger window had opened on it’s own, I might have figured this out sooner. But instead I still have to manually invoke the debugger on the Mac. So little lesson for the night. [import]uid: 152474 topic_id: 31077 reply_id: 124252[/import]

#8

Thanks for updating; on Windows the debugger shouldn’t open on its own I don’t believe (not a PC person) but the terminal window should - on the Mac you should launch Corona via the terminal shortcut located in the Corona SDK folder.

For the path thing, out of interest, can you leave off the initial / on PC? As I said I’m unsure on the PC side though if you have any Qs I’m happy to talk to another member of the team to try and get you some answers, just let me know.

Peach :slight_smile: [import]uid: 52491 topic_id: 31077 reply_id: 124267[/import]

#9

Ms. Pellen, yes I went through my code on the Windows Corona Simulator, and deleted the extra “/” in the front, and I had no problems in the Windows Simulator Corona. Windows doesn’t seem to care if you have the extra “/” in front or not, it works both ways.

But Mac Corona Simulator would only work after I removed the extra “/” in the front.

So obviously, since Windows works both ways, I’ll just remember not to include the “/” beginning for the path to assets so when I build on the Mac I don’t have that issue again.

Ok on the terminal window for Mac. Thanks. [import]uid: 152474 topic_id: 31077 reply_id: 124271[/import]

#10

I believe windows doesn’t care for uppercase filenames.
OSX does. [import]uid: 100901 topic_id: 31077 reply_id: 124310[/import]

#11

Thanks very much for that update - and a valid point raised by Juf Jannie - on PC you wont get uppercase/lowercase warnings if not correct, IIRC - something else to watch for as these errors can cause a “corrupted” error when trying to install on device. [import]uid: 52491 topic_id: 31077 reply_id: 124466[/import]