Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]
Photo

[RESOLVED] App submission reject - Your app contains non-public API usage
Started by Yoger Games Sep 04 2014 11:48 AM

141 replies to this topic

Best Answer walter , 09 September 2014 - 04:47 PM

Apple has confirmed the false positive issue on their end:

 

While you are getting that, we are aware of the issue. Please tell your developers to keep trying to submit and, if necessary, submit a DTS incident about the rejection. Feel free to pass along to those folks who are getting rejected on this the information about this API in their review appeal. 

 
Thanks.

 

 

 

Anecdotally, several of you have confirmed that you can submit your binaries now. You should be able to use the last public release; you do *not* need the daily build with the workaround (but you will need to add the "CFBundleShortVersionString" to the plist section of build.settings for builds below 2407).
 
If you are still seeing issues, Apple says to follow up with Apple DTS (e.g. file a DTS incident: https://developer.apple.com/support/technical/submit/). You should reference the fact that GameCenter's public API ('setComposeViewDelegate:' a.k.a the 'composeViewDelegate' property in GKFriendRequestComposeViewController) is being incorrectly flagged as a non-public API.
 
Thanks to everyone who filed a report to Apple. That definitely helped escalate Apple's attention to the matter!

[TOPIC CONTROLS]
« Page 5 of 6 3 4 5 6
This topic has been archived. This means that you cannot reply to this topic.
[/TOPIC CONTROLS]
[modOptionsDropdown]
[/modOptionsDropdown]
[reputationFilter]
[TOPIC: post.html]
#101

dfoxinator

[GLOBAL: userInfoPane.html]
dfoxinator
  • Enthusiast

  • 49 posts
  • Enterprise

Have tried again today and am not getting this error anymore?

 

Maybe Apple have fixed it?

 

Thanks for the heads up! It appears they've fixed it, worked for me too.



[TOPIC: post.html]
#102

jennifer.marie.indovina

[GLOBAL: userInfoPane.html]
jennifer.marie.indovina
  • Observer

  • 4 posts
  • Corona SDK

@mark504 yes, I saw that today too, application loader took me past the false positives - but we're not out of the woods yet, now the failure is a string name mismatch ... thanks Corona guys for all your hard work! We'll just have to wait on Apple... Hoping today is worth it :)

[TOPIC: post.html]
#103

becauseinterwebs

[GLOBAL: userInfoPane.html]
becauseinterwebs
  • Observer

  • 6 posts
  • Enterprise

I was able to upload my app, although the first time it tagged it for not having the "CFBundleShortVersionString" which I thought was fixed previously?  Anyway, I added it manually and uploaded but got a warning about some game network functions...same thing about non-public API, but it took the app and it is in processing status :)



[TOPIC: post.html]
#104

shielded

[GLOBAL: userInfoPane.html]
shielded
  • Observer

  • 15 posts
  • Corona SDK

I was able to upload my app, although the first time it tagged it for not having the "CFBundleShortVersionString" which I thought was fixed previously?  Anyway, I added it manually and uploaded but got a warning about some game network functions...same thing about non-public API, but it took the app and it is in processing status :)

 

It's fixed in daily builds, but not in the latest public release.



[TOPIC: post.html]
#105

mark504

[GLOBAL: userInfoPane.html]
mark504
  • Observer

  • 4 posts
  • Corona SDK

Solution for "CFBundleShortVersionString" is here

http://forums.coronalabs.com/topic/50461-publish-app-failure/



[TOPIC: post.html]
#106

Tom

[GLOBAL: userInfoPane.html]
Tom
  • Moderator

  • 1,480 posts
  • Corona Staff

I just tested the uploads again and it does seem that Apple fixed the error that was preventing uploads to the App Store.

 

Daily build users can use build 2407, which contains the "CFBundleShortVersionString" fix.

 

Starter and Basic users can use build 2393A but need to add the "CFBundleShortVersionString" parameter to the plist section of the build.settings file.

 

When you upload, you will get a warning message but will no longer receive the error message that prevented uploads.

 

Thanks to everyone who reported this issue to Apple. 



[TOPIC: post.html]
#107

dylestorm

[GLOBAL: userInfoPane.html]
dylestorm
  • Enthusiast

  • 56 posts
  • Corona SDK

Hey guys,

 

I managed to successfully upload the game using Application Loader 2.9.1. However I didn't receive any email notification nor was the build shown in iTunes Connect. Pressing the 'Submit For Review' button pops up a message saying "Please select a build".

 

Does anyone have this problem?

 

Edit: It went through. I guess Apple servers are taking a hit from high traffic. All is good  :)



[TOPIC: post.html]
#108

Tom

[GLOBAL: userInfoPane.html]
Tom
  • Moderator

  • 1,480 posts
  • Corona Staff

I had the same issue where the upload didn't show when I clicked on the "+" symbol next to Build. I went back 30 minutes later and it was there so I guess it doesn't show up immediately. You do have to click the "Build +" in order to select the build you want to submit.

 

If you try to upload the same build again, you will get an error that there is already a build with the same version in iTunesConnect.



[TOPIC: post.html]
#109

memoryx17

[GLOBAL: userInfoPane.html]
memoryx17
  • Observer

  • 3 posts
  • Corona SDK

Ok. Apple have fixed problem. Yuppiiiiiiiiii.

[TOPIC: post.html]
#110

jan0

[GLOBAL: userInfoPane.html]
jan0
  • Enthusiast

  • 64 posts
  • Corona SDK

Why the error from Apple regarding Push Notifications (see below)?  Is this something I need to fix or I broke?... or is it an error or issue with Corona SDK (API)?    I do not use push notifications in my app and I did not check 'Push Notifications' when I created the apps certificate.  I am using build 2424.

 

From Apple:  "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."

 

I would like to know so if I do another build I will not have the same issue or at least I will have an explanation for it!  Thank you.

 

-----------------------------------------------------------------------------------------------------------------------------------------------

Here is the entire message from Apple: "

We have discovered one or more issues with your recent delivery for "U-Boat Bunker St Amiot". Your delivery was successful, but you may wish to correct the following issues in your next delivery:

 

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

-----------------------------------------------------------------------------------------------------------------------------------------------



[TOPIC: post.html]
#111

PickionGames

[GLOBAL: userInfoPane.html]
PickionGames
  • Enthusiast

  • 67 posts
  • Corona SDK

Looks like the apps are no longer giving back errors, I want to thank the staff for keeping us up to date with everything and I never was too worried that a fix was in the works the entire time.

 

I know patience is difficult but I think this was something Apple cooked up on their end anyway.

 

 

It's a little weird how their new process works. You upload the build with application loader first but can't submit it until it's uploaded and in the Application Loader it shoots an error saying you have to check the IDFA box but that's the following step. Otherwise, it looks very intuitive and "new".



[TOPIC: post.html]
#112

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 25,535 posts
  • Enterprise

You can safely ignore the push notification email.

 

Rob



[TOPIC: post.html]
#113

nipon.ph

[GLOBAL: userInfoPane.html]
nipon.ph
  • Observer

  • 21 posts
  • Corona SDK

Well I got this error. Is this Certificate Problem?

 

Error ITMS-9000 "Missing or Invalid siganature. The Bundle 'come.coronalabs.CoranaResouces' at bundlepath 'myapp.app/CoroanResouces.bundle" is not signed using Apple submission certificate



[TOPIC: post.html]
#114

nipon.ph

[GLOBAL: userInfoPane.html]
nipon.ph
  • Observer

  • 21 posts
  • Corona SDK

I can install myapp,app on my iphone normally



[TOPIC: post.html]
#115

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 25,535 posts
  • Enterprise

To me it sounds like you didn't build the app with a provisioning profile that was set for submitting to the App Store.  There are three types of provisioning profiles:

 

Developer

Submission: AdHoc

Submission: App Store

 

You need to goto the provisioning portal, make sure you have a profile setup for the app store, download it using Xcode or manually put it in your ~/Library/MobileDevice/Provisioning\ Profiles/ folder.  Quit Corona SDK and relaunch it.  Select the right profile and build.

 

If you think this is correct, we would need to see your build.settings and a screen shot of the Corona SDK build screen just before you click the "Build" button.  Please don't black anything out to hide information.

 

Rob



[TOPIC: post.html]
#116

PickionGames

[GLOBAL: userInfoPane.html]
PickionGames
  • Enthusiast

  • 67 posts
  • Corona SDK

Now that we're allowed to upload apps, has anyone else had the message 

This bundle is invalid - New apps and app updates submitted to the App Store must be built with public (GM) versions of Xcode 5.1.1 or higher and iOS 7 SDK. Do not submit apps built with beta software.

I wrote a question about that here
 
Wondering if this is tied to the issue from this thread?


[TOPIC: post.html]
#117

dislam

[GLOBAL: userInfoPane.html]
dislam
  • Contributor

  • 182 posts
  • Corona SDK

Well I got this error. Is this Certificate Problem?

 

Error ITMS-9000 "Missing or Invalid siganature. The Bundle 'come.coronalabs.CoranaResouces' at bundlepath 'myapp.app/CoroanResouces.bundle" is not signed using Apple submission certificate

 

I got the same error.  This had been working for the same app for many months.  

 

I cleared all my certificates, emptied the Provisioning Profiles folder, and regenerated everything.  Still same problem :(  



[TOPIC: post.html]
#118

exevio

[GLOBAL: userInfoPane.html]
exevio
  • Observer

  • 16 posts
  • Corona SDK

> Error ITMS-9000 "Missing or Invalid siganature. The Bundle 'come.coronalabs.CoranaResouces' at bundlepath

 

Same error here too!

Just spent two hours to fix this but seems like it's not something we can change at all.



[TOPIC: post.html]
#119

walter

[GLOBAL: userInfoPane.html]
walter
  • Moderator

  • 726 posts
  • Alumni

  Best Answer

Apple has confirmed the false positive issue on their end:

 

While you are getting that, we are aware of the issue. Please tell your developers to keep trying to submit and, if necessary, submit a DTS incident about the rejection. Feel free to pass along to those folks who are getting rejected on this the information about this API in their review appeal. 

 
Thanks.

 

 

 

Anecdotally, several of you have confirmed that you can submit your binaries now. You should be able to use the last public release; you do *not* need the daily build with the workaround (but you will need to add the "CFBundleShortVersionString" to the plist section of build.settings for builds below 2407).
 
If you are still seeing issues, Apple says to follow up with Apple DTS (e.g. file a DTS incident: https://developer.apple.com/support/technical/submit/). You should reference the fact that GameCenter's public API ('setComposeViewDelegate:' a.k.a the 'composeViewDelegate' property in GKFriendRequestComposeViewController) is being incorrectly flagged as a non-public API.
 
Thanks to everyone who filed a report to Apple. That definitely helped escalate Apple's attention to the matter!


[TOPIC: post.html]
#120

gibsonpa

[GLOBAL: userInfoPane.html]
gibsonpa
  • Enthusiast

  • 69 posts
  • Enterprise

> Error ITMS-9000 "Missing or Invalid siganature. The Bundle 'come.coronalabs.CoranaResouces' at bundlepath

 

Same error here too!

Just spent two hours to fix this but seems like it's not something we can change at all.

 

I just built and attempted to upload to the App Store as well, and am getting this exact same error.  Using daily build 2424.



[TOPIC: post.html]
#121

jennifer.marie.indovina

[GLOBAL: userInfoPane.html]
jennifer.marie.indovina
  • Observer

  • 4 posts
  • Corona SDK

The farthest I have gotten is my app was submitted and "Waiting for Review" - after editing the plist file (which got me submitted), and I was reissued new apple root keys and making sure to use the new +build button in iTunes Connect (which finally got my binary accepted), and I ignored the warnings.

 

My binary was rejected, 6 hours after being issued the "waiting for review" update, earlier this morning:

 

This bundle is invalid - New apps and app updates submitted to the App Store must be built with public (GM) versions of Xcode 5.1.1 or higher and iOS 7 SDK. Do not submit apps built with beta software.

 

Which makes no sense, because I am using higher versions, my guess is the editing of the plist isn't the whole fix. So, anyone else see this yet? Before I use up my last DTS. :) 



[TOPIC: post.html]
#122

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 25,535 posts
  • Enterprise

For those of you getting the Xcode 5.1.1 error, what version of Corona SDK are you using to build with?   What version of Xcode to you have installed?

 

For those getting the other error bundle path error, please post your build.settings, version of Corona SDK  you're building with and a screen shot of your build screen just before you hit the build button please.  Also I need an exact copy of the message, not a hand typed version.. Please select the text and copy and paste the text here.

 

Thanks

Rob



[TOPIC: post.html]
#123

exevio

[GLOBAL: userInfoPane.html]
exevio
  • Observer

  • 16 posts
  • Corona SDK

Xcode 5.1.1 (5B1008)

Corona SDK 2014.2393 (2014.8.5)

settings = {

orientation = {
  default = "portrait",
  supported = { "portrait", }
},

iphone = {
  plist = {
            CFBundleName = "Rocket Launcher",
            CFBundleDisplayName = "Rocket L.",
            CFBundleShortVersionString = "1.0",
   UIStatusBarHidden = true,
   UIPrerenderedIcon = true,

            plugins =
            {
                ["CoronaProvider.analytics.flurry"] = { publisherId = "com.coronalabs" }
            }
  }
},

   
    plugins =
    {
        ["CoronaProvider.ads.iads"] =
        {
            publisherId = "com.coronalabs",
            supportedPlatforms = { iphone=true, ["iphone-sim"]=true },
        },
        ["CoronaProvider.analytics.flurry"] =
        {
            publisherId = "com.coronalabs",
        },
    },

}


[TOPIC: post.html]
#124

jennifer.marie.indovina

[GLOBAL: userInfoPane.html]
jennifer.marie.indovina
  • Observer

  • 4 posts
  • Corona SDK

Hey Rob, Xcode 5.1.1 and Corona 2014.2393 - huge thanks to you and Tom for the amazing support



[TOPIC: post.html]
#125

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 25,535 posts
  • Enterprise

If you are providing me this information please do so here in the forums and not as a private message to me.  I can't share the information with engineering if it's a private message.

 

Rob




[topic_controls]
« Page 5 of 6 3 4 5 6
 
[/topic_controls]