kellymdempewolf <kellymdempew...@gmail.com> wrote:
> Is there any way that I can work around this to fix it in my own app in the > meantime? Sadly not, this is why I suggested some sort of community supported process as a safety net for Apple rule changes. Your app almost certainly doesn't use the UDID but the LiveCode engine binary links to the banned method, so you can't pass the automated test until you have a LiveCode commercial build with the offending method call removed. I could build a standalone with it removed from the community version source code but that can't be used to submit to the app store. Probably worth adding a note to the bug report and let them know which LiveCode version you're using since they may want to prioritise patch releases for those actively waiting to submit apps. Mark ________________________________ From: kellymdempewolf <kellymdempew...@gmail.com> To: use-revolut...@lists.runrev.com Sent: Thursday, 9 May 2013, 14:46 Subject: Re: automated iOS rejection: Non-public API usage Is there any way that I can work around this to fix it in my own app in the meantime? I have an app that needs to be sent to iTunes but I have the same rejection happening! (I have subscribed to the bug report so I'll see when it's fixed but for now I need to get the app sent!) Thanks! -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/automated-iOS-rejection-Non-public-API-usage-tp4664353p4664566.html Sent from the Revolution - User mailing list archive at Nabble.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