Coming back to this after a while. Sorry for the late response.
First thing’s first, the build settings, file names, function names, etc. Had no errors. The error was that I was having was happening because I had three old calls that were bundled into one function that I forgot to remove.
Then there is the issue of the weirdness. My directory is structured as you said. Is has main.lua in it, build.settings, all images, etc., in a single directory. The strangeness comes because in my main working directory (that housed all the files) I could simulate in Corona non-stop. No issues whatsoever. But as soon as I downloaded that directory from bitbucket into a fresh directory I’d get the build error.
The problem with that is that I should have been getting the Corona build error in my local directory without having to download fresh. Even if I just drug all the files out of that directory into a new one, the error would be present whereas if they stayed in the original directory it wouldn’t have been present. So I had two locations with the exact same files but one location generated the error, the other didn’t.
That is a pretty big issue to me. I had to go back roughly 20 commits to find the source of the error, even though the entire time it was present - Corona was just not showing it.
I now feel as though I need to build the app to xcode at every turn just to make sure this doesn’t happen again.
Is it possible that Corona Simulator caches certain files? [import]uid: 228837 topic_id: 36170 reply_id: 144463[/import]