Hello,
I just noticed that the exact same built (iOS) version of my Corona app that I built couple of days ago, is now almost 10MB larger. What’s going on?
I can easily verify the problem by checking out an old git commit and building the app. The build size used to be around 15MB and now it’s over 24MB.
Is the build server including something new to all builds? And can I prevent it from doing that? I tried to search the forums and release notes but couldn’t find a reason.
Thanks!
This sounds like the same problem I had a month or so ago. Naomi helped me with some good info.
When you choose build from the corona simulator menu, near the bottom of the dialog window where it reads ‘Save to Folder’, DO NOT choose to save to folder where you have your lua files for this app.
I create a special folder on my desktop to save to. It sounds strange, but when you choose to save to the same directory as the app files, it just keeps adding the ‘compiled’ file into the newer compilation(I think).
Anyway, just save to folder other then the app folder.
Good luck.
Thanks for the tip, but I don’t think that’s the reason in my case. I’ve been saving the builds to a completely different directory all along and I haven’t change anything between Monday and today 
Hmm… is there something being done for the PNGs on the build server? I just happened to notice that my app has 10MB of PNGs… or maybe it’s just a coincidence…
Aha! I found the reason, my images were in directory called Images, when I changed that to all lowercase (images) the build size is back to normal.
Note to self: always use all lowercase directory names!
WTF… It worked only once… now I keep getting oversized builds again. I’m starting to suspect that a load balancer taking my build requests to a different server time to time and some of them are doing the oversized builds and some not… I’m confused.
Sorry for the message spam
Oh man… I seems that the problem was OS X Finder all along. It seems to be randomly showing different MB for the built app file (which is a directory btw). ‘du -sh’ command in terminal seems to tell the truth.
Sorry about all this… Hopefully my monologue is at least helpful to someone else in the future 
This sounds like the same problem I had a month or so ago. Naomi helped me with some good info.
When you choose build from the corona simulator menu, near the bottom of the dialog window where it reads ‘Save to Folder’, DO NOT choose to save to folder where you have your lua files for this app.
I create a special folder on my desktop to save to. It sounds strange, but when you choose to save to the same directory as the app files, it just keeps adding the ‘compiled’ file into the newer compilation(I think).
Anyway, just save to folder other then the app folder.
Good luck.
Thanks for the tip, but I don’t think that’s the reason in my case. I’ve been saving the builds to a completely different directory all along and I haven’t change anything between Monday and today
Hmm… is there something being done for the PNGs on the build server? I just happened to notice that my app has 10MB of PNGs… or maybe it’s just a coincidence…
Aha! I found the reason, my images were in directory called Images, when I changed that to all lowercase (images) the build size is back to normal.
Note to self: always use all lowercase directory names!
WTF… It worked only once… now I keep getting oversized builds again. I’m starting to suspect that a load balancer taking my build requests to a different server time to time and some of them are doing the oversized builds and some not… I’m confused.
Sorry for the message spam
Oh man… I seems that the problem was OS X Finder all along. It seems to be randomly showing different MB for the built app file (which is a directory btw). ‘du -sh’ command in terminal seems to tell the truth.
Sorry about all this… Hopefully my monologue is at least helpful to someone else in the future