Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]
Photo

Non-public API usage & Missing Push Notification Entitlement Email from iTune Store
Started by sonthai May 09 2013 08:20 PM

9 replies to this topic
[TOPIC CONTROLS]
This topic has been archived. This means that you cannot reply to this topic.
[/TOPIC CONTROLS]
[modOptionsDropdown]
[/modOptionsDropdown]
[reputationFilter]
[TOPIC: post.html]
#1

sonthai

[GLOBAL: userInfoPane.html]
sonthai
  • Observer

  • 1 posts
  • Corona SDK

Hello everyone, 

Yesterday, I uploaded my app update to Apple via Application Loader. After a few minute, I received an email from iTune Store. Nothing has changed in my app. 

"Dear developer,


We have discovered one or more issues with your recent delivery for "WiTurn". To process your delivery, the following issues must be corrected:


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 appreview@apple.com. For further information, visit the Technical Support Information page.


Though you are not required to fix the following issues, we wanted to make you aware of them:


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.


Once the required corrections have been made, go to the Version Details page and click "Ready to Upload Binary." Continue through the submission process until the app status is "Waiting for Upload." You can then deliver the corrected binary.


Regards,


The App Store team"

 

 

If anyone has seen this, or has some ideas, it would be much appreciated.

Thanks.



[TOPIC: post.html]
#2

capellf

[GLOBAL: userInfoPane.html]
capellf
  • Observer

  • 8 posts
  • Corona SDK

I got this message when I attempted to release an app compiled under Corona 2012.971 (2012.11.15).

 

Compiling with 2013.1076 (2013.4.3) seems to have resolved the problem.

 

(In my case, I am using macincloud, and the older version is easier to notice because its icon is Corona-colored. The newer version is there right beside it, but its icon is a default bluish color.)

 

Also see this thread: http://forums.coronalabs.com/topic/34819-ios-message-when-publishing-an-app-today-for-the-new-ios-6-rules/?hl=uidevice



[TOPIC: post.html]
#3

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 26,544 posts
  • Enterprise

The UDID was removed after 971 and Apple no longer permits it's use.



[TOPIC: post.html]
#4

ubj3d.android

[GLOBAL: userInfoPane.html]
ubj3d.android
  • Contributor

  • 741 posts
  • Corona SDK

After submitting the binary (Corona 1076)

 

I got this email from Apple:

 

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.

 

 

My game does not use push notifications.

 

???



[TOPIC: post.html]
#5

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 26,544 posts
  • Enterprise

You can ignore this message.



[TOPIC: post.html]
#6

dingo

[GLOBAL: userInfoPane.html]
dingo
  • Contributor

  • 700 posts
  • Corona SDK

I got this message too today... I guess I still can ignore that? :)



[TOPIC: post.html]
#7

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 26,544 posts
  • Enterprise

Yes, you can ignore it.



[TOPIC: post.html]
#8

greg886

[GLOBAL: userInfoPane.html]
greg886
  • Contributor

  • 920 posts
  • Corona SDK

Just got it myself - guess I'll ignore it too then   :)



[TOPIC: post.html]
#9

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 26,544 posts
  • Enterprise

This is still a non-issue...  :-)



[TOPIC: post.html]
#10

Christopher Bishop

[GLOBAL: userInfoPane.html]
Christopher Bishop
  • Contributor

  • 416 posts
  • Corona SDK

If you have "ever" setup push notifications (even for testing) all your future apps will get this email from Apple after you submit for review and like Rob said simply ignore it :) This happens on my non-corona (ie: straight xcode) applications as well.




[topic_controls]
[/topic_controls]