@vlads @PerryClarke
Sorry for late response.
It’s 2015.2744
We can’t upgrade due to a constraint we have from our client, and it’s related to app discovery on ios.
Believe me, I’ve tried many times to influence them to update but it seems like a lost cause until Apple disallows it.
I would really be grateful for the upgrade on info on how to do it myself if it’s possible.
Thanks in advance
Krystian
Corona engineers, you guys are going straight to heaven.
Thanks so much! What a mammoth job that must’ve been to figure it all out!
Much appreciated!
I just tried the new corona build with Xcode 7.3 (ios 9.3). It works!! Thanks a lot for Corona!!!
Worked like a charm! Thanks a lot Corona! 
Thanks so much Rob Miracle and Corona engineers for your great support!!!
OK, so here’s some details for the curious. The reason for failing was that Apple tried to process our “.car” files in the update to iTunesConnect verification they rollout week ago. Apparently, at some point, they started to use this file extension internally.
While issue seems quite simple, it was very hard to track down - because they seem to process this files only on the server, without paying them attention in Xcode Archive & Export. Also, their tools were just failing without producing a specific error message, just with the generic exit code. When the issue was identified, our solution was to change use extension to “.corona-archive” (on iOS and tvOS) to avoid the issue in the future.
The error message sent by iTunesConnect really lead us astray from identifying a problem because we were focusing on bitcode for a while since the wording was extremely vague and bitcode has a record of causing problems.
Thats really interesting, I don’t build with corona but I was seeing the same error. iTC was seeing plist files in my project (just app data files), replacing these with ‘.json’ & I no longer see TN2432 after submitting.
If you are still getting this error its worth trying to remove your plist files (not Info.plist of course) and see whether iTC will accept it.
Hello I’m also getting the same error.
I’m using Corona SDK.
Corona build: 2016.2906 (2016.6.21)
Mac Version: El Capitan 10.11 (15A284)
XCode version: 7.3.1 (7D1014)
On my email I received the following message:
While processing your iOS app, XXXXXXX, 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.
and on Application loader I get the following warning message:
The resulting API analysis file is too large. We were unable to validate your API usage prior to delivery. This is just an informational message.
Here is my full build settings:
–
– For more information on build.settings see the Corona SDK Build Guide at:
– http://docs.coronalabs.com/guide/distribution/buildSettings/index.html
–
settings =
{
orientation =
{
default = “portrait”,
supported = { “portrait”, “portraitUpsideDown”, “landscapeRight”, “landscapeLeft”, “faceUp”, “faceDown”}
},
plugins =
{
[“plugin.facebook.v4”] =
{
publisherId = “com.coronalabs”,
},
[“plugin.notifications”] =
{
publisherId = “com.coronalabs”,
},
},
android =
{
supportsTV = false,
isGame = true,
minSdkVersion = “14”,
largeHeap = true,
permissions =
{
{ name = “.permission.C2D_MESSAGE”, protectionLevel = “signature” },
},
usesPermissions =
{
“android.permission.INTERNET”,
“com.google.android.c2dm.permission.RECEIVE”,
“android.permission.INTERACT_ACROSS_USERS”,
“android.permission.INTERACT_ACROSS_USERS_FULL”,
“android.permission.GET_ACCOUNTS”,
“android.permission.RECEIVE_BOOT_COMPLETED”,
“com.google.android.c2dm.permission.RECEIVE”,
“.permission.C2D_MESSAGE”,
},
facebookAppId = “XXXXXX”,
usesFeatures =
{
},
supportsScreens =
{
smallScreens = true,
normalScreens = true,
largeScreens = true,
xlargeScreens = false,
},
},
iphone =
{
plist =
{
CFBundleDisplayName = “XXXXX”,
CFBundleName = “XXXX”,
CFBundleShortVersionString = “1.0.2”,
CFBundleVersion = “1.0.4”,
CFBundleIconFiles = {
“Icon.png”,
“Icon@2x.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-167.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”,
}, – Required
UILaunchImages = {
{ – iPhone 4 Portrait
[“UILaunchImageMinimumOSVersion”] = “7.0”,
[“UILaunchImageName”] = “Default-ios”,
[“UILaunchImageOrientation”] = “Portrait”,
[“UILaunchImageSize”] = “{320, 480}”
},
{ – iPhone 4 LandscapeLeft
[“UILaunchImageMinimumOSVersion”] = “7.0”,
[“UILaunchImageName”] = “Default”,
[“UILaunchImageOrientation”] = “LandscapeLeft”,
[“UILaunchImageSize”] = “{320, 480}”
},
{ – iPhone 4 LandscapeRight
[“UILaunchImageMinimumOSVersion”] = “7.0”,
[“UILaunchImageName”] = “Default”,
[“UILaunchImageOrientation”] = “LandscapeRight”,
[“UILaunchImageSize”] = “{320, 480}”
},
{ – iPhone 5 Portrait
[“UILaunchImageMinimumOSVersion”] = “7.0”,
[“UILaunchImageName”] = “Default-568h”,
[“UILaunchImageOrientation”] = “Portrait”,
[“UILaunchImageSize”] = “{320, 568}”
},
{ – iPhone 5 LandscapeLeft
[“UILaunchImageMinimumOSVersion”] = “7.0”,
[“UILaunchImageName”] = “Default-568h”,
[“UILaunchImageOrientation”] = “LandscapeLeft”,
[“UILaunchImageSize”] = “{320, 568}”
},
{ – iPhone 5 LandscapeRight
[“UILaunchImageMinimumOSVersion”] = “7.0”,
[“UILaunchImageName”] = “Default-568h”,
[“UILaunchImageOrientation”] = “LandscapeRight”,
[“UILaunchImageSize”] = “{320, 568}”
},
{ – iPad Portrait
[“UILaunchImageMinimumOSVersion”] = “7.0”,
[“UILaunchImageName”] = “Default-Portrait-ios”,
[“UILaunchImageOrientation”] = “Portrait”,
[“UILaunchImageSize”] = “{768, 1024}”
},
{ – iPad LandscapeLeft
[“UILaunchImageMinimumOSVersion”] = “7.0”,
[“UILaunchImageName”] = “Default-Landscape-ios”,
[“UILaunchImageOrientation”] = “LandscapeLeft”,
[“UILaunchImageSize”] = “{768, 1024}”
},
{ – iPad LandscapeRight
[“UILaunchImageMinimumOSVersion”] = “7.0”,
[“UILaunchImageName”] = “Default-Landscape-ios”,
[“UILaunchImageOrientation”] = “LandscapeRight”,
[“UILaunchImageSize”] = “{768, 1024}”
},
{ – iPhone 6 Portrait
[“UILaunchImageMinimumOSVersion”] = “8.0”,
[“UILaunchImageName”] = “Default-667h”,
[“UILaunchImageOrientation”] = “Portrait”,
[“UILaunchImageSize”] = “{375, 667}”
},
{ – iPhone 6 LandscapeLeft
[“UILaunchImageMinimumOSVersion”] = “8.0”,
[“UILaunchImageName”] = “Default-667h”,
[“UILaunchImageOrientation”] = “LandscapeLeft”,
[“UILaunchImageSize”] = “{375, 667}”
},
{ – iPhone 6 LandscapeRight
[“UILaunchImageMinimumOSVersion”] = “8.0”,
[“UILaunchImageName”] = “Default-667h”,
[“UILaunchImageOrientation”] = “LandscapeRight”,
[“UILaunchImageSize”] = “{375, 667}”
},
{ – iPhone 6 Plus Portrait
[“UILaunchImageMinimumOSVersion”] = “8.0”,
[“UILaunchImageName”] = “Default-736h”,
[“UILaunchImageOrientation”] = “Portrait”,
[“UILaunchImageSize”] = “{414, 736}”
},
{ – iPhone 6 Plus LandscapeLeft
[“UILaunchImageMinimumOSVersion”] = “8.0”,
[“UILaunchImageName”] = “Default-Landscape-736h”,
[“UILaunchImageOrientation”] = “LandscapeLeft”,
[“UILaunchImageSize”] = “{414, 736}”
},
{ – iPhone 6 Plus LandscapeRight
[“UILaunchImageMinimumOSVersion”] = “8.0”,
[“UILaunchImageName”] = “Default-Landscape-736h”,
[“UILaunchImageOrientation”] = “LandscapeRight”,
[“UILaunchImageSize”] = “{414, 736}”
},
{ – iPad Pro Portrait
[“UILaunchImageMinimumOSVersion”] = “9.0”,
[“UILaunchImageName”] = “Default-Portrait-1366”,
[“UILaunchImageOrientation”] = “Portrait”,
[“UILaunchImageSize”] = “{1024, 1366}”
},
{ – iPad Pro Landscape Right
[“UILaunchImageMinimumOSVersion”] = “9.0”,
[“UILaunchImageName”] = “Default-Landscape-1366”,
[“UILaunchImageOrientation”] = “LandscapeRight”,
[“UILaunchImageSize”] = “{1024, 1366}”
},
{ – iPad Pro Landscape Left
[“UILaunchImageMinimumOSVersion”] = “9.0”,
[“UILaunchImageName”] = “Default-Landscape-1366”,
[“UILaunchImageOrientation”] = “LandscapeLeft”,
[“UILaunchImageSize”] = “{1024, 1366}”
},
}, – Required
UIPrerenderedIcon = true,
UIStatusBarHidden = true,
NSAppTransportSecurity =
{
– Required
– Add domain of API or CMS here
–
NSAllowsArbitraryLoads = true,
NSExceptionDomains =
{
[“XXXXX”] =
{
NSIncludesSubdomains = true,
NSExceptionAllowsInsecureHTTPLoads = true,
NSExceptionRequiresForwardSecrecy = true
},
----------------------------------------------------
– Required
----------------------------------------------------
–
[“fbcdn.net”] =
{
NSIncludesSubdomains = true,
NSExceptionRequiresForwardSecrecy = false,
},
[“facebook.com”] =
{
NSIncludesSubdomains = true,
NSExceptionRequiresForwardSecrecy = false,
},
[“akamaihd.net”] =
{
NSIncludesSubdomains = true,
NSExceptionRequiresForwardSecrecy = false,
},
},
},
– Whitelist Facebook Apps
–
LSApplicationQueriesSchemes =
{
“fbapi”,
“fbapi20130214”,
“fbapi20130410”,
“fbapi20130702”,
“fbapi20131010”,
“fbapi20131219”,
“fbapi20140410”,
“fbapi20140116”,
“fbapi20150313”,
“fbapi20150629”,
“fbapi20160328”,
“fbauth”,
“fbauth2”,
“fb-messenger-api20140430”,
},
–
UIApplicationExitsOnSuspend = false,
FacebookAppID = “XXXXX”,
CFBundleURLTypes =
{
{ CFBundleURLSchemes = { “fb254496894905346”, } }
},
},
},
build =
{
neverStripDebugInfo = false,
},
window =
{
defaultMode = “fullscreen”,
titleText =
{
default = “XXXX”,
},
},
}
Thanks I will appreciate if you can fixed this issue ASAP. Hope this could help you analyse the problem.
By the way I also try to create sample app and upload it , it still the same warning message.
To fix this, you need to download daily build 2949 or later.
I just wanted to confirm that the latest build fixed the issue for me. Thanks Corona team!
Apple accidentally. Corona staff are fast and professional.
Excellent work
Just got this email from Apple after I tried the new Corona build and submitted yesterday. Looks like Apple needs to fix things at their end:
During app thinning, your app experienced issues due to a third-party generated file named resource.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
This has to be from previous submission attempts since we no longer use a resource.car file with 2949.
Rob
Yeah seems like it. My app went into “Ready for Sale” state last night, and that version is currently on the app store.
I received this same email this morning
I received this too. Thanks for the clarification Rob.
I used 2949 to build my app, received the same email regarding resource.car
Best to just wait?
Did you submit an app prior to installing 2949 and try to submit?