Build Not Appearing in iTunes Connect

Solar2D iOS
#1

Has anyone encountered when you send an update to iTunes Connect via Application Loader that says it successfully uploaded, shows as Processing in Activity in iTunesConnect, and then disappears?

  • Corona SDK 2016.2861

  • Xcode 8.0 (8A218a)

  • Application Loader 3.6 (Application Loader 3.0 gives errors)

  • Distribution Certificate

Process:

  1. Corona SDK > Build - Distribution Certificate selected (Only one created) - Open in Finder selectec (Send to App Store gives error ‘Cannot Send to App Store’ even though there’s only a Distribution certificate, nothing else).
  2. Create folder called ‘Payload’
  3. Drag published Corona SDK app into Payload folder
  4. Compress Payload
  5. Change .zip to .ipa (Using .zip throws errors)
  6. Open Xcode > Application Loader (Using Application Loader 3.0 from iTunes Connect throws errors, have to use the one from Xcode)
  7. Upload .ipa file and receive Thank You message for a successful upload
  8. Log into iTunes Connect and select the updated app profile which is waiting for submission
  9. Under Activity tab, new build is “Processing”
  10. Build disappears
  11. Nothing ever appears, just says to upload via Xcode or Application Loader

I’ve attempt this about 6 times and waited overnight, but still nothing. Has anyone else encountered this?

Thanks!

#2

The person who I’m updating the app for said they got a bunch of emails from Apple when I was attempting to upload:

"This app attempts to access privacy-sensitive data without a usage description. The app’s Info.plist must contain an NSPhotoLibraryUsageDescription key with a string value explaining to the user how the app uses this data."

1.) It’s just a storybook app, there’s no exchanging of data

2.) How do I go about correcting this?

:wacko:

#3

I was gong to say if you’re seeing it in “Processing” and then it disappears, then Apples automatic scanning system is rejecting your app and you should be getting an email with the cause.

For this specific error, since Corona has camera and photo library code in it’s core, it’s being flagged as needing these permissions strings even if you don’t invoke those features. You simply need to include a couple of keys in your plist in build.settings.

iphone = { plist = { NSCalendarsUsageDescription = "Not used", NSPhotoLibraryUsageDescription = "Not used", NSCameraUsageDescription = "Not used" } }

This should clear the auto-scanning rejection for this.

Now for your issue of not being able to call application loader from the simulator: Are you getting an error?

Rob

#4

Thanks Rob,

I actually found your post with the code above from a Google search while at work and that seemed to fix it. Is it weird that I exported as iPad Only, but still had provide icons and screenshots for all iPhones in the build and on iTunes Connect?

In the Simulator, I get the error Cannot Send to App Store. Only apps built with distribution profiles can be sent to the App Store…

Which is odd since I only have one and it’s for distribution.

At least I was able to submit the app for review, so that’s a good baby step!

#5

Remember there are two types of “Distribution” profiles:  For the Store and AdHoc. You have to have the “For the Store” version to submit.

Rob

#6

Hey Rob,

It was the For the App Store version, which is the weird part. I didn’t use any Ad-Hoc, Development, etc. profiles for this as it was a faux update just to keep it from being removed from the App Store. I just had to publish the same app using the latest versions of software with a new build name. I’m not sure why it wouldn’t let me send directly to App Store, but the important part is, the updates are live. Thanks for your help on the plist settings, that was a major hurdle!

#7

The person who I’m updating the app for said they got a bunch of emails from Apple when I was attempting to upload:

"This app attempts to access privacy-sensitive data without a usage description. The app’s Info.plist must contain an NSPhotoLibraryUsageDescription key with a string value explaining to the user how the app uses this data."

1.) It’s just a storybook app, there’s no exchanging of data

2.) How do I go about correcting this?

:wacko:

#8

I was gong to say if you’re seeing it in “Processing” and then it disappears, then Apples automatic scanning system is rejecting your app and you should be getting an email with the cause.

For this specific error, since Corona has camera and photo library code in it’s core, it’s being flagged as needing these permissions strings even if you don’t invoke those features. You simply need to include a couple of keys in your plist in build.settings.

iphone = { plist = { NSCalendarsUsageDescription = "Not used", NSPhotoLibraryUsageDescription = "Not used", NSCameraUsageDescription = "Not used" } }

This should clear the auto-scanning rejection for this.

Now for your issue of not being able to call application loader from the simulator: Are you getting an error?

Rob

#9

Thanks Rob,

I actually found your post with the code above from a Google search while at work and that seemed to fix it. Is it weird that I exported as iPad Only, but still had provide icons and screenshots for all iPhones in the build and on iTunes Connect?

In the Simulator, I get the error Cannot Send to App Store. Only apps built with distribution profiles can be sent to the App Store…

Which is odd since I only have one and it’s for distribution.

At least I was able to submit the app for review, so that’s a good baby step!

#10

Remember there are two types of “Distribution” profiles:  For the Store and AdHoc. You have to have the “For the Store” version to submit.

Rob

#11

Hey Rob,

It was the For the App Store version, which is the weird part. I didn’t use any Ad-Hoc, Development, etc. profiles for this as it was a faux update just to keep it from being removed from the App Store. I just had to publish the same app using the latest versions of software with a new build name. I’m not sure why it wouldn’t let me send directly to App Store, but the important part is, the updates are live. Thanks for your help on the plist settings, that was a major hurdle!