[RESOLVED] App submission reject - Your app contains non-public API usage

Okay, we think we have found a workaround to Apple’s false alarm. We are making this available in daily build 2422. You may still see warnings about non-public APIs, but you should no longer see errors preventing your app from uploading.

What we are doing:

Pro/Enterprise users: you can use this daily build. We appreciate any reports on this. Expect to continue to see warnings, but the error should (hopefully) go away.

 

Starter/Basic users: Because Apple is making so many things in flux, we are going to wait for the dust to settle post-iOS 8 before we update the public release. Too many variables can change right now, and it doesn’t make sense for us to play a cat-and-mouse game with Apple — there may be other public APIs that Apple will capriciously choose to cause submission errors. Hopefully, given that native iOS devs are affected, Apple will fix this on their servers.

What you can do if you really must submit:

Right off, we recommend that you avoid submitting right now. Experience (https://devforums.apple.com/message/1035262#1035262) suggests you should postpone submissions until 2 weeks after iOS 8.

 

However, if you really must submit right now, you should submit your grievances to Apple. To that end, we have created a form letter (below) that you can send to (appreview@apple.com).

 

You will need to replace NINE_DIGIT_ID with the corresponding nine digit identifier from iTunes Connect.


SUBJECT: False positives in “non-public API usage” preventing app upload

MESSAGE BODY:

Hi, our app binary (NINE_DIGIT_ID) cannot be uploaded to iTunesConnect b/c ApplicationLoader is *incorrectly* flagging non-public APIs. In other words, these are false positives.

We say this with 100% certainty because the code is using public properties that the Xcode compiler (Apple’s own tools) are converting to ‘set’ selector calls (as Obj-C properties are syntactic sugar for selector method calls). These calls are erroneously being flagged as false positives:

* ‘setComposeViewDelegate:’ is equivalent to the ‘composeViewDelegate’ property in GKFriendRequestComposeViewController

* ‘setAchievementDelegate:’ is equivalent to the ‘achievementDelegate’ property in GKAchievementViewController

* ‘setLeaderboardDelegate:’ is equivalent to the ‘leaderboardDelegate’ property in GKLeaderboardViewController

* ‘setShowExistingMatches:’ is equivalent to the ‘showExistingMatches’ property in GKTurnBasedMatchmakerViewController

* ‘setTurnBasedMatchmakerDelegate:’ is equivalent to the ‘turnBasedMatchmakerDelegate’ property in GKTurnBasedMatchmakerViewController

Similar issues have been noted on the Apple’s Developer Forum, e.g. https://devforums.apple.com/message/1035114#1035114

Therefore, our app does *not* contain private APIs, and is consistent with public API usage per Apple’s developer agreement. Please let us know how we can upload our binary and get past these false alarms.

sincerely,

XXX

Worked for me :slight_smile:

Worked for me too. Thanks guys for this quick patch! 

:slight_smile:

@shareng76, @Puzzle Runner: After mail to (appreview@apple.com), you submit immediately or wait to reply from Apple Review team. How long do you receive their reply. I’ve just mail to Appl Review.

Sorry, it’s firt time I upload to Apple store.

Downloaded the latest daily build. The code seems unstable in regards to linear and angular damping. When I apply to a dynamic body all onscreen bodies start sliding downwards.

Havent tried to upload my update to test the non-public API fix.

I’m guessing Apple Review staff are going to be getting a ton of these requests.

Just sent mine in as well. 

@Mobi, I’m thinking we got to wait for the to respond because the uploader won’t take the app.

uploaded, good job!

thanks @PickionGames

Getting this error after using, 

CoronaSDK 2014.2422

Worked for me too :wink:

Thx !

Hi @Gispubc, @xnailbender

Pls tell us more details. What do you mean? You upload successfully?

Follow up from yesterday: The upload was successful, but the status did not change (i.e. did not go into review). I had attributed this to heavy traffic and called it a night, however, the reality is that Apple has changed the submission process (for the better, IMO). 

Here’s what you need to do:

  1. Upload an app

  2. Go to your app in iTunes connect, and choose the build you want.

  3. Save, then hit Submit for Review (top right). Your app immediately goes into the waiting for review phase.

Yes, Apple changed iTunesConnect interface and you need to click on the"+" symbol next to Build and select the build you just uploaded. If you don’t, it will still say “Ready for Upload”. Once you select the build and Save, it will say “Ready for Submission.”

@singletusked, the “upload to iTunes error” is an error is uploading and has nothing to do with Corona or the build you’re using.

just a heads up.

I ran into problems with the new “Build and Save” feature in iTunes Connect.

I uploaded a binary and about 20 minutes later discovered a typo I had made in a text object.

When I went to upload the new binary, I couldn’t remove the old binary and the application loader wouldn’t let upload a second binary to the list. ( I had not yet “Submitted for Review” the first binary.

The only way I could get the second binary to upload was to change the version number of the app and then app loader allowed me to upload the second binary.

Nail

You could try the iTunes Connect app to reject the binary instead of trying through the website.

Has anyone who emailed Apple gotten feedback yet?

I’m assuming they’re not available on the weekend though and getting heavy traffic request.

So basic/starter users are out of luck until ios 8 comes out?

@puppymodz, as Walter said, we are going to wait until all of this settles down before we put out another public build.  They are not things we can whip out over night like a daily build.  With all of the changes to the submission process, there is a good chance Apple is not done making changes.  Once things settle down, and we’ve had a chance to run our full battery of tests against the iOS 8 gold master and fix any issues, then we should be in a much better place to address this for Starter and Basic accounts.

Rob

 I just finished my first app and it’s pretty frustrating that I can’t publish. I don’t have access to the daily build with the quick patch so I’m kinda just sitting here waiting. Is there a date that we can expect ?

I can’t provide a date unfortunately.  There are too many variables right now.

Rob