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.

While processing your iOS app, ---------------Build(1.0.22), errors occurred in the app thinning process, and your app couldn’t be thinned. If your app contains bitcode, bitcode processing may have failed. Because of these errors, this build of your app will not be able to be submitted for review or placed on the App Store. For information that may help resolve this issue, see Tech Note 2432.

I only changed the one line of code and changed the Build Number. And, I uploaded 4 build got the same Error.

Answer 1

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 2

MY SOLUTION THAT DID NOT WORKED BUT MAYBE CAN GIVE U A WAY OUT

In My own case, i developed my IOS APP with PhoneGap

After so much research, was told to disable bitcode from my ItuneConenct App Account https://developer.apple.com/library/mac/documentation/LanguagesUtilities/Conceptual/iTunesConnect_Guide/Chapters/ChangingAppStatus.html

And was introduced to a new phonegap plugin to disable bitcode in my IOS APP https://www.npmjs.com/package/cordova-plugin-cs-disable-bitcode

which i added to my Phonegap app config.xml file

Yet after rebuilding my phonegap IOS app and uploading to ItunesConenct using Application Builder (Got a successful message from the upload). Few mins' after the upload, I got same message from Apple with the same error.

This can give you a hint

Answer 3

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 4

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.