iOS apps being generated with plist key CFBundleResourceSpecification, now prevents uploading to App Store

Apps generated for iOS with 4.9 cannot be uploaded to TestFlight or iTunes Connect because they have started to enforce, server side, the deprecation of the Info.plist key CFBundleResourceSpecification. This key needs to be removed from the generated app or nobody is going to be able to submit their apps to the app store or test them using Test Flight.

Digging a little, it looks like this is generated in CodeSigning.cs. I’m going to see if I can remove this key and get my project to upload. If it does, I’ll submit a pull request.

Commented out the code that added that key, but the generated app still have it. Not sure where it’s coming from.

Relevant portion:

Systems before OS X Mavericks v10.9 documented a signing feature (–resource-rules) to control which files in a bundle should be sealed by a code signature. This feature has been obsoleted for Mavericks. Code signatures made in Mavericks and later always seal all files in a bundle; there is no need to specify this explicitly any more. This also means that the Code Signing Resource Rules Path build setting in Xcode should no longer be used and should be left blank.

It is thus no longer possible to exclude parts of a bundle from the signature. Bundles should be treated as read-only once they have been signed.

I’ve tried commenting out lines 80 - 82 in CompileTime.cs and am testing it. I think I’ll also need to comment out some code in CodeSigning.cs. There’s a check there to make sure that there’s a CFBundleResourceSpecification key that may still trigger this problem.

I’ll have to do some more digging because it sounds like you are just doing this from the PC. There are other places when doing this from a Mac which add the CustomResourceRules as well (XcodeProjectFileGenerator.cs). I also want to see the error from the app upload first hand so I can understand what the failure message is.

I am very much not doing this from a PC :slight_smile:

XcodeProjectFileGenerator.cs may also add it. I wasn’t sure if that came into play with a UBT build, though.

I can certainly understand you wanting to do your homework, unfortunately, I’m now a few days late on delivering a build, so I need to keep pushing forward on my own.

Following up with the answer from on the other post:

I just verified the fixes on a Mac and uploaded an App. Just need to verify the PC side and then it should be all ready. -

From: iOS / Xcode 7 compiled apps not accepted by iTunes Connect - Mobile - Epic Developer Community Forums

We will likely be providing this fix in a QFE as soon as it is ready.