Re: Non-Public API Usage

I switched back to 8.1.2 RC1 and compiled. I submitted to Apple and the result was just the "Missing Push Notification Entitlement" message. So whatever the problem is, it must be specific to RC2. -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Non-

> Subject: Re: Non-Public API Usage

We have discovered one or more issues with your recent delivery for "PlanningBoard 2". To process your delivery, the following issues must be corrected: Non-public API usage: The app references non-public symbols in MadPink Planning Board: _getcontext, _makecontext, _setcontext

Re: Non-Public API Usage

Hi Pink - have you seen this related thread: http://runtime-revolution.278305.n4.nabble.com/iTunes-Connect-rejection-td4710481.html > I have not used those names, so I submitted it: > > http://quality.livecode.com/show_bug.cgi?id=18958 >

Re: Non-Public API Usage

I have not used those names, so I submitted it: http://quality.livecode.com/show_bug.cgi?id=18958 -- View this message in context: http://runtime-revolution.278305.n4.nabble.com/Non-Public-API-Usage-tp4710840p4710842.html Sent from the Revolution - User mailing list archive at Nabble.com

Re: Non-Public API Usage

ing issues must be corrected: Non-public API usage: The app references non-public symbols in MadPink Planning Board: _getcontext, _makecontext, _setcontext If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from bei

Non-Public API Usage

or more issues with your recent delivery for "PlanningBoard 2". To process your delivery, the following issues must be corrected: Non-public API usage: The app references non-public symbols in MadPink Planning Board: _getcontext, _makecontext, _setcontext If method names in your source

Re: automated iOS rejection: Non-public API usage

Hi Michael There is a quality.runrev.com section to the website where we can report bugs and get updates as to how progress is going on fixing them. As you are fairly new to LiveCode you may not have yet gone through the process of getting Heather to set up an account for you there (at least

Re: automated iOS rejection: Non-public API usage

If the bug is also present in version 5.5.4, there is the possibility RR will not go back to fix it there. That would be a business decision that has not been revealed to the public yet. Best regards, Mark Talluto http://www.canelasoftware.com On May 16, 2013, at 2:36 AM, Magicgate

Re: automated iOS rejection: Non-public API usage

Mark Waddingham just posted this on Bug 10895: Hi all, Just an update on this issue. The 'non-public API' usage error is caused because the engine still has a linkage to the 'systemIdentifier' device property which Apple are now scanning for in their automated tests before an app goes

Re: automated iOS rejection: Non-public API usage

I too have been effected by this issue. Having been in possession of the 5.5 iOS deployment option for only a little while, I'm quite bummed as it seems to have become obsolete. If someone knows or discovers a workaround in 5.5 It would save my project and make my month. On Mon, May 13, 2013 at

RE: automated iOS rejection: Non-public API usage

... tempus fugit ! Date: Wed, 15 May 2013 15:08:52 -0700 Subject: Re: automated iOS rejection: Non-public API usage From: hatchfact...@gmail.com To: use-livecode@lists.runrev.com I too have been effected by this issue. Having been in possession of the 5.5 iOS deployment option for only a little

Re: automated iOS rejection: Non-public API usage

On 5/15/13 5:08 PM, Michael Hatch wrote: I too have been effected by this issue. Having been in possession of the 5.5 iOS deployment option for only a little while, I'm quite bummed as it seems to have become obsolete. If someone knows or discovers a workaround in 5.5 It would save my project

Re: automated iOS rejection: Non-public API usage

So that will also mean that it will force all of us running the commercial version of 5.5.4 to pay for the new commercial version, right? SKIP On Wed, May 15, 2013 at 7:18 PM, J. Landman Gay jac...@hyperactivesw.comwrote: On 5/15/13 5:08 PM, Michael Hatch wrote: I too have been effected by

Re: automated iOS rejection: Non-public API usage

I also have been bitten by this bug - at 04:20 this morning - I would be tearing my hair out but I have none left! Anyone got any information on when RunRev will put out a new version? Kind regards - Dave ___ use-livecode mailing list

Re: automated iOS rejection: Non-public API usage

! -- 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

Re: automated iOS rejection: Non-public API usage

...@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

Re: automated iOS rejection: Non-public API usage

I see RunRev have jumped on the bug report quickly, which is great, but Apple deprecated the UDID a very long time ago and recently gave fair advanced warning that they'd be rejecting any apps still using it from May 1st. Since I was able to find: engine/src/mbliphoneextra.mm:t_identifier =

automated iOS rejection: Non-public API usage

When submitting an app for iOS the Application Loader completes successfully but shortly an email from Apple arrives explaining that the binary is invalid because: - Non-public API usage: • Apps are not permitted to access the UDID and must

Re: automated iOS rejection: Non-public API usage

from Apple arrives explaining that the binary is invalid because: - Non-public API usage: • Apps are not permitted to access the UDID and must not use the uniqueIdentifier method of UIDevice. Please update your apps and servers to associate

Re: automated iOS rejection: Non-public API usage

Apple arrives explaining that the binary is invalid because: - Non-public API usage: • Apps are not permitted to access the UDID I wonder if this is in the engine. There are calls that allow us to get that info. If so, RR needs to remove those