Open Radar

 
Summary:
I had a named pipe lurking in my app bundle.  As a result, it wouldn't run on a simulator or device - however, the error is very cryptic as it doesn't point out where the unsupported resource is.  I ended up rebuilding my development certificate & provisioning profile (it was code sign complaining after all), before finding out about something else on the bundle causing this issue.

Steps to Reproduce:
1.  Create an iOS project in Xcode.  
2.  Add a folder reference to it.
3.  In a terminal, navigate to that folder you've just added a reference to, and type the following commands:

mkfifo my_pipe
gzip -9 -c < my_pipe > out.gz &

4.  Build the project and attempt to run it on a simulator or device!

Expected Results:
Either codesign ignores this resource, or points out where the offending resource is.

Actual Results:
Codesign tells you there's an unsupported resource, but doesn't tell you where it is!

Version:
Xcode 8.0 (8A218a)
macOS 10.12 (16A319)
iOS 10 SDK


Notes:
One way I easily got a named pipe lurking is from using the Realm browser to open up one of my Realm files inside my app bundle (please don't shoot me for not using Core Data......)