LiveCode Forums.

Colleagues

There seems to be other changes in the App screening process after uploading binaries. Just uploaded a new version of one of our apps via iTunes Connect and received an email which included the following message:

"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 users with the Vendor or Advertising identifiers introduced in iOS 6.

If method names in your source code match the private Apple APIs listed above, altering your method names will help prevent this app from being flagged in future submissions. In addition, note that one or more of the above APIs may be located in a static library that was included with your app. If so, they must be removed.

If you think this message was sent in error and that you have only used Apple-published APIs in accordance with the guidelines, send the app's nine-digit Apple ID, along with detailed information about why you believe the above APIs were incorrectly flagged, to Apple (email address removed). For further information, visit the Technical Support Information page."

Never seen this before and the App does not contain iAds, Push Notifications or anything else other than just a standard build without . The build was using LC 5.5.4 as this is stable and was reliable. Any suggestions on how to fix this? Why were APIs incorrectly flagged? Is LC now designated as a non-Apple API!!!

The App review will not be processed until this is resolved. There were also other notifications about "Missing Push Notification Entitlement" and "Non-PIE Binary". Apparently "The executable is not a Position Independent Executable. Please ensure that your build settings are configured to create PIE executables." whatever that means!

Has anyone else come across this? Any advice and suggestions most welcome.

Colleagues

Just checked the quality forums and this issue has been reported (Bug 10895), been confirmed and has been assigned to a LC developer for investigation.

Will await outcome and post an update here for other colleagues.

Dave

Hi:

I have just received the same error message from Apple. I submitted the app (built with LC 5.5.4) about a month ago and it was accepted, but my first upgrade, submitted today, was rejected. Hope this gets solved soon.

--paul

Paul

paulsr wrote:I have just received the same error message from Apple. I submitted the app (built with LC 5.5.4) about a month ago and it was accepted, but my first upgrade, submitted today, was rejected. Hope this gets solved soon.

Things never stand still long enough it seems!! As mentioned earlier, I will post an update here once things have been resolved within LC.

Dave

Any news on this bug?

We are having the same problem.

Andres

I also have just recently experienced this problem. To help narrow in on the timeframe, here is the sequence of events:

May 01, 2013 - I completed building APP1 using LC 5.4.4 and then submitted it to the App Store

May 07, 2013 - APP1 was approved and available on the App Store

May 13, 2013 - I created a new app (APP2) using the same LC 5.4.4 and submitted it to the App Store. Later the same day, I received the notification from Apple that APP2 was flagged for "Non-public API usage" due to accessing the UDID.

So it would seem that within the last 6 - 7 days, Apple modified their policies and/or procedure for reviewing and approving apps. i have been frantically scanning and re-writing my code, building with different configurations, etc. and then submitting revisions to try and get past this issue. So far, nothing has been successful.

Hopefully, there is a resolution soon !

the same here.

Still no news from LC guys?

I need to upload a new version of my app with several bugs fixed and major improvements.
The previous one was uploaded and approved a couple of weeks ago. Now I'm stuck with this: "non-public API usage", "Apps are not permitted to access the UDID ..." stuff.
I have no idea about what should I have to do on my side.
I'm using Livecode 5.5.4 Commercial.

Thanks in advance for any help.

It needs to be fixed in the standalone builder. RR knows and has fixed it, but I can't remember if it was in the 6.0.1 release or if it will be in the next one. If anyone has tried a submission with the latest version of LiveCode, maybe they can report here.

Today we tried with 6.0.1 Build 1513 and got that error.

jacque wrote:It needs to be fixed in the standalone builder. RR knows and has fixed it, but I can't remember if it was in the 6.0.1 release or if it will be in the next one. If anyone has tried a submission with the latest version of LiveCode, maybe they can report here.

I don't have a commercial license for vers. 6, so I really need a fix for 5.5.4.

--paul

Colleagues

The App builds appear to be rejected by Apple from all versions of commercial LC and is clearing having a negative impact on a number of folk around the world. Certainly it is frustrating and knocks confidence! Obviously Apple changed their screening process and LC ran foul of this.

As reported earlier, this problem had been confirmed by RR as a bug and a software engineer has been assigned but to date there has been no further updates on when this critical issue will be addressed.

Hopefully, RR will release an update to fix the problem for the various versions of LC and not just to LC 6+. I would have thought this ought to include LC 5.5 onwards at the very least as many have been using previous versions whilst gremlins in LC 6 are squeezed out and a stable commercial build is available. All this at the same time as the big RunRevLive13 gathering in Edinburgh.

Will post more here when there is something more positive to say.

Regards

Dave

Thank you Dave

When can we expect the update to version 6?

Andres

Andres

andres wrote: When can we expect the update to version 6?

The latest information from RR via the quality forum suggests there will be update releases for versions 5.5.4 (to 5.5.5) and 6.0.1 (to 6.0.2). Currently undergoing internal testing so I guess it could be next week sometime.

Hope this is helpful.

Dave

Thanks Dave

DRJ-UK wrote:The latest information from RR via the quality forum suggests there will be update releases for versions 5.5.4 (to 5.5.5) and 6.0.1 (to 6.0.2). Currently undergoing internal testing so I guess it could be next week sometime.

That's very generous of them to take on the additional expense of backporting the fix to the older version to account for Apple's policy change. Thanks for the update.