Scott, If I'm understanding correctly, the limitation is on the actual executable inside the app bundle, not the entire app bundle. I too have downloading very large apps in the past, but I'm pretty sure these all have their resources external to the executable. That's why my suggestion was to pull out all possible embedded resources (images, sounds, etc.) and access them externally to the executable. Again, I'm not 100% sure this is the issue.
Chris On Jun 3, 2013, at 1:10 PM, Scott Rossi <sc...@tactilemedia.com> wrote: > I wonder if there's something else going on with the size limitation. I > routinely download games that are 300, 400, 500MB in size all the time (even > more sometimes). > > Regards, > > Scott Rossi > Creative Director > Tactile Media, UX/UI Design > > -------- Original message -------- > Subject: Re: First App rejected for odd reasons > From: Thomas McGrath III <mcgra...@mac.com> > To: How to use LiveCode <use-livecode@lists.runrev.com> > CC: > > Roger, > > I was hoping to have to avoid that. It seems that 80 MB is the max limit > which seems crazy to me. I can't seem to reclaim any of the memory from > reducing from 2048 down to 1024 and that bother me. I was hoping to find out > why that is happening. But I will have to rewrite this to reference the > images to get this down below 80 I think. > > Tom > > -- Tom McGrath III > http://lazyriver.on-rev.com > mcgra...@mac.com > > On Jun 3, 2013, at 2:19 PM, Roger Eller <roger.e.el...@sealedair.com> wrote: > >> Can you make the images referenced from a URL, or must they be included in >> the app? >> >> ~Roger >> >> On Mon, Jun 3, 2013 at 2:17 PM, Thomas McGrath III <mcgra...@mac.com> wrote: >> >>> Ok, after upgrading to 5.5.5 and changing the iOS to 5.0 and above I am >>> still getting a Binary rejection for Three of the four reasons: >>> >>> Invalid Executable Size - Your app's executable file >>> 'GospelOfMark.app/GospelOfMark' is a size of 243446992 bytes, which exceeds >>> the maximum allowed size of 80 MB. Abnormally large executable files are >>> often the result of using a development environment that stores excessive >>> or unnecessary data in the compiled binary. You may need to contact your >>> tool vendor for assistance if your app was built with a developer tool >>> other than Xcode. If your app was built using Xcode, you may contactApple >>> Developer Technical Support if you need assistance. >>> >>> Though you are not required to fix the following issues, we wanted to make >>> you aware of them: >>> >>> Missing Push Notification Entitlement - Your app appears to include API >>> used to register with the Apple Push Notification service, but the app >>> signature's entitlements do not include the "aps-environment" entitlement. >>> If your app uses the Apple Push Notification service, make sure your App ID >>> is enabled for Push Notification in the Provisioning Portal, and resubmit >>> after signing your app with a Distribution provisioning profile that >>> includes the "aps-environment" entitlement. See "Provisioning and >>> Development" in the Local and Push Notification Programming Guide for more >>> information. If your app does not use the Apple Push Notification service, >>> no action is required. You may remove the API from future submissions to >>> stop this warning. If you use a third-party framework, you may need to >>> contact the developer for information on removing the API. >>> >>> Non-PIE Binary - The executable 'GospelOfMark.app' is not a Position >>> Independent Executable. Please ensure that your build settings are >>> configured to create PIE executables. For more information, refer to >>> Technical Q&A QA1788 - Building a Position Independent Executable >>> >>> >>> >>> Tom >>> >>> -- Tom McGrath III >>> http://lazyriver.on-rev.com >>> mcgra...@mac.com >>> >>> >>> _______________________________________________ >>> use-livecode mailing list >>> use-livecode@lists.runrev.com >>> Please visit this url to subscribe, unsubscribe and manage your >>> subscription preferences: >>> http://lists.runrev.com/mailman/listinfo/use-livecode >>> >> _______________________________________________ >> use-livecode mailing list >> use-livecode@lists.runrev.com >> Please visit this url to subscribe, unsubscribe and manage your subscription >> preferences: >> http://lists.runrev.com/mailman/listinfo/use-livecode > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
