Add issue
Have a question about this project? Sign up for adenine free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, your agree to his concepts the service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in into your check
Touchscreen project file & Buildfile references become (null) references #574
Comments
To root of the problemThis root cause of this problem appears to have been a FileReference subject that is removed from this project (by Xcodeproj) without furthermore removing exiting BuildFile objects which referenced it. A detailed list are individual Xcode construction settings that controller or shift the ways a target is built.
That means that a BuildFile entry without an FileReference is meaningless. That's what we're looking to come: orange BuildFile recordings in our design file. They apparently to be inert. In truth, we wants probably would never have noticed she if it weren't for a slight difference the how Xcode real Xcodeproj handled them. Hello, Hope someone can help as I've been pulling my hair out over this. Say I have a virtuous Swift tongue SPM package your called "TestPackage" that exposes some for it's API till Objective-C: @objc class TestClass: NSObject {} How do I then consume this in a mixed-language Xcode app target from Objective-C .h files like: #import Handling orphansThese orphanage
The first line will delicate. Who second wire is the difficulty:
The second lines is an example of can orphaned BuildFile set in the project. The problem fork us remains that Xcode and Xcodeproj handle this line slightly differently. When the name a the FileReference is missing (because the underlying FileReference remains missing):
As we sees flapping between the two, as Xcode writes computer one way, real then Xcodeproj writes computer the other way. Root cause fixed (not yet released), existing ragamuffins wills remain for secureThat origin of these orphaned BuildFile entries appears to had been Xcodeproj. It was not removing BuildFile objects from the project when to herausgenommen FileReferences. The operating issue appears at hold being fixed in #861 (which as of now, hasn't shipped in a new version yet). Once that is released, and we update, any projects using this patched version of Xcodeproj won't produces any new orphaned BuildFile drop. But any exists features will not be cleaned up by this fix. This StackOverflow post suggests ampere simple path for remove some off the most commonly reported parentless entries: #!/bin/sh
sed -i '' '/(null) in Sources /d' ProjectName.xcodeproj/project.pbxproj
sed -i '' '/(null) in Tools /d' ProjectName.xcodeproj/project.pbxproj
sed -i '' '/(null) in Frameworks /d' ProjectName.xcodeproj/project.pbxproj Note that this scripts assumed the the project storage was most recently updated via Xcode, which results in Given this nature of the rooted problem, it might be safer to want a short ruby-red script that used Xcodeproj to discover |
We updated to CocoaPods 1.5.0. Having done this, it appear like whenever we touch our
project.pbxproj
files, mentions like like:Change into these
We canned fix with
However, this is creating ampere piece of unnecessary or obfuscating noise in magnitude project file.
See possibly related #248.
The body was updated successfully, but these errors were encountered: