I am experiencing some strange behavior with my app. The app runs fine when I run it (Run Main Project) from the glider environment. But if I open the main.lua file directly from the corona simulator it crashes. Even the project sandbox directory folder seems to be different. I was under the assumption that the builds would be identical. Any troubleshooting techniques would be greatly appreciated.
Hey
I am at work at the moment so can’t really test this out - but I know Glider creates some sort of debug files when you’re running your app through their interface onto Corona Simulator. It complains if you try to push this to mobile device unless you build it first - which I assume gets rid of all those files.
Try doing the build in Glider then try restarting the Corona simulator directly and attempting to run the app again (without running/debugging it first in Glider). I can try and replicate this once I get home if you’re still having issues.
Rich
Hey
I am at work at the moment so can’t really test this out - but I know Glider creates some sort of debug files when you’re running your app through their interface onto Corona Simulator. It complains if you try to push this to mobile device unless you build it first - which I assume gets rid of all those files.
Try doing the build in Glider then try restarting the Corona simulator directly and attempting to run the app again (without running/debugging it first in Glider). I can try and replicate this once I get home if you’re still having issues.
Rich
Thank you kindly for your help!
@Quantum,
Just as Rich said Glider will add a debug library and add a require line to your main.lua file. Before making the modifications it will first copy the project contents to a separate build folder so that the asset manager can build your project without messing up the master project folder. If you run this main.lua directly in the simulator it will just stop and wait for a debugger connection before even rendering the first frame. In this state the simulator will appear frozen but it is just waiting for a Glider debugger connection. However, if you click the “build” button (the hammer next to debug) then Glider will strip the debug library and require line from main.lua and you will now be able to run the file directly without Glider. You use the build button when you want to compile a binary app package from the simulator.
Regards,
M.Y. Developers
Thank you kindly for your help!
@Quantum,
Just as Rich said Glider will add a debug library and add a require line to your main.lua file. Before making the modifications it will first copy the project contents to a separate build folder so that the asset manager can build your project without messing up the master project folder. If you run this main.lua directly in the simulator it will just stop and wait for a debugger connection before even rendering the first frame. In this state the simulator will appear frozen but it is just waiting for a Glider debugger connection. However, if you click the “build” button (the hammer next to debug) then Glider will strip the debug library and require line from main.lua and you will now be able to run the file directly without Glider. You use the build button when you want to compile a binary app package from the simulator.
Regards,
M.Y. Developers