iTunes Connect Errors occurred in the app thinning process, and your app couldn’t be thinned?

Question

I Uploaded the build via Xcode Yesterday it worked fine but while uploading today the build is uploading perfectly but after 10 minutes i got a email form apple stating that

Answer 1

I've experienced the same symptoms and have found a solution.

The root cause of the issue is invalid/incorrect keys in a given bundle's embedded Info.plist.

This is typically the .bundle contained within a third party library e.g. GoogleMaps SDK.

The steps for remediation are:

• For each .bundle containing only resources:
  • Remove the key/value CFBundleExecutable
  • Change the value for key CFBundleSupportedPlatforms to iPhoneOS (Item 0, first element in the array. The previous value was iPhoneSimulator in my case)

The technical reason is that CFBundleExecutable should not be present in a bundle's plist if there is no executable. The value for CFBundleSupportedPlatforms is self explanatory, it should be iPhoneOS.

Tech Note 2432 mentions the above two keys but does not elaborate how to resolve the issue.

I hope this solution works for you.

Answer 2

I met with this issue today, I used google-api-objectivec-client-for-rest (as framework). I tried all the solutions above, but failed.

Now I fixed it by copying all the source of google-api-objectivec-client-for-rest to my own project. Hope it helpful to you.

Answer 3

I had the same problem and I found the solution. In my app, I had the Google Plus framework: GoogleOpenSource.framework. This framework was the problem. I searched about the latest update in Google Plus: https://developers.google.com/+/mobile/ios/upgrading-sdk.

The latest version was 1.7.1. This version has the same problem. In my app, I removed the login with Google Plus (deprecated https://gyazo.com/685a58f98ee0b0fca16a6bd83636aad8) and I added Google: https://developers.google.com/identity/sign-in/ios/sdk/

This works for me.

A greeting.

Answer 4

I had this happen a couple days ago and the temporary solution for me was to not include bitcode for iOS content, which is an uploading option (see image). Apple suggests to do an ad hoc export with an ad hoc provisioning profile to receive the errors and logs of the failure, but I'm unable to reproduce the error(s) and the ad hoc export is successful each time. Will update this post when I find out how to re-enable bitcode, but for now this seems like a good temporary fix. -Update: there was an error in the name of one of my project folders, mixup with symbolic folder name, when I corrected the name to match what was actually in the folder structure I was able to upload properly-

Answer 5

Finally got it to work. In our case, the error was in one of the embedded frameworks. Generating a Production Ad-hoc build and then trying to export it generated an error message that pointed us to an error in a setting within one of the framework files. The framework has been there for a while and we never had any issues with it until this release.

Answer 6

update xcode to 8.0 which published at 0914 from apple store , rebuild project and submit to iturns , the issue was not found , instead any detail info for anouther issue which use ios 10 sdk required . i have submited success, and waiting for approval .