Apple sent this email to anyone who submitted builds earlier, to help out to whomever didn’t resolve the issue (not only Corona uses car files).
If this message doesn’t contain reference to specific build, disregard it. Also you can check your iTunesConnect app’s page, Activity → All Builds, and see if your recent builds are marked with ⛔
I got a same mail for resource.car. I made and submitted the app with 2948 and i didnt understand 2948 is free from resource.car problem(because staffs refered to 2949 version only…). I am sorry but can you confirm and explain it once more easily? I dont know the best way is just waiting or resubmitting with 2949 or over version. Thanks every corona staff.
kinradiology, please read previous message.
2948 is the build with the Apple Fix. However 2949 is where we turn on iOS 10 with a release SDK. Those wanting to upgrade to Xcode 8 will need 2949 to release apps with Xcode 8. Those keeping Xcode 7.3 can still build with 2949 too. It also picked up a couple of other features including one where if you use Corona SDK to install to our iOS device, it will sometimes timeout. You would have to rebuild to try again. Now you get a button to retry the connection after unplugging and replugging in your device.
So 2949 is a better choice.
Yep, got the email message too, Fri 19:13 Vienna time. Used CoronaSDK-2950. On Saturday it was approved. So now they take .car, I guess?
Same Here.
While processing your iOS app, Lotto Lockdown 1.0.3(2016.9.191220), 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.
My Build.settings
settings =
{
orientation =
{
– Supported values for orientation:
– portrait, portraitUpsideDown, landscapeLeft, landscapeRight
default = “portrait”,
supported = { “portrait”, },
},
plugins =
{
[‘plugin.qrscanner’] = {publisherId = ‘com.spiralcodestudio’}
},
–
– iOS Section
–
iphone =
{
plist =
{
UIStatusBarHidden = false,
UIPrerenderedIcon = true, – set to false for “shine” overlay
--UIApplicationExitsOnSuspend = true, – uncomment to quit app on suspend
enable_bitcode = NO,
CFBundleIconFiles =
{
“Icon.png”,
“Icon@2x.png”,
“Icon-167.png”,
“Icon-60.png”,
“Icon-60@2x.png”,
“Icon-60@3x.png”,
“Icon-72.png”,
“Icon-72@2x.png”,
“Icon-76.png”,
“Icon-76@2x.png”,
“Icon-Small.png”,
“Icon-Small@2x.png”,
“Icon-Small@3x.png”,
“Icon-Small-40.png”,
“Icon-Small-40@2x.png”,
“Icon-Small-50.png”,
“Icon-Small-50@2x.png”,
},
},
},
–
– Android Section
–
android =
{
usesPermissions =
{
“android.permission.INTERNET”,
},
},
}
download and use the latest Daily Build. Your problem should go away. The Corona engineers fixed this problem.
Hey folks,
I just want to confirm something, because it seems like you are bashing users with an issue.
I’ve created the ipa using updated corona enterprise, I have made sure the car files is now named corona-archive. Double and triple checked.
I’ve sent the ipa to Test flight and got this message after a day or two [don’t remember]:
Dear Krystian,
During app thinning, your app experienced issues due to a third-party generated file namedresource.car. As a result, your app build cannot be added to iTunes Connect for submission to TestFlight or the App Store.
We are currently updating the app thinning process to accommodate files of this type. When this update is complete, we will retry processing your app. No action is needed on your part at this time. We will send you an email once your app has been successfully thinned, processed, and made available for TestFlight or submission to the App Store.
For an overview of diagnosing app thinning issues, read Tech Note 2432.
If you have any questions or would like to get in touch, go to Resources and Help.
Best regards,
The App Store Team
And now, the most important info.
I did NOT send any build to Apple after the issue with thinning started to occur.
I have followed the thread, I know my clients have had issues, but I did not send anything there.
This was the first time, and it was after I have updated.
So… don’t bash other users saying that they did not update, they might have and they still got this email, as I did.
Thanks
Krystian
Krystian: nobody’s bashing anyone here. 
Quote from the email sent to you: “No action is needed on your part”.
This means that Apple will reprocess your already uploaded app. Unless there’s something else wrong with it, it will be published in a day or two, like mine was.
I think you missed the point.
I have sent this using updated corona, where there’s no resources.car file, thus how do they report its existence?
I understand that for folks who sent apps using older corona builds it makes sense, but in my case - it does not.
So did I, and I got the same email, and now my app is published with no action taken on my part.
That, to me, is the point.
sure, we just have a different view on things.
For me, just because I get the expected result, doesn’t mean everything works as expected 
I’ve received emails from Apple containing incorrect information before. If you want to investigate this message further, you must contact them.
Guys! Please, read above. This is a diagnostic message about builds which failed processing earlier. Disregard it. Everyone who submitted a build got this message, this is not an error about specific build, this is a message if you still can not resolve problems with your build.
If your builds do pass processing - disregard that email.
There is no need to say that you got this email, everyone who submitted a build did. Apple sent this email to help people who also had some .car files, may be it wasn’t Corona app and they still don’t have a way to resolve the issue.
sorry to bring it up again, all I wanted to say is that I got this message even though I have NOT sent any builds prior the version that fixed the problem.
Unless you are saying that this message is about some other game I have not updated in few years and Apple reprocessed it, then cool, otherwise, it’s just weird.
I am disregarding the email, since I was able to put it on testflight, but I wanted to let you know that something like this has happened.
Ok, EOT.
Today I’ve uploaded a build to iTunesConnect and get the thinning email again.
I used daily build 2951, Xcode 8 and I have added all new plist values.
A few days agon I could upload another app successfully with the same build settings.
Can you post the exact email message? There are two: one is a rejection, one says it’s going to retry after they solve the problem. We need to know which message you’re getting.
Rob
Hi Rob,
this is the Apple email.
While processing your iOS app, XXXXXXXX(2016.9.191501), 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.
Regards,
The App Store team
What happens if you drop back to 2949?
The same problem.