fix build bug due to private framework conflicts#2
Conversation
It appears that Xcode is incorrectly attempting to load Network.framework from PrivateFrameworks rather than regular frameworks directory
|
Yes, this does work to fix the build errors and import the Network framework. Can you help me understand the change and where you made it in the IDE? It's confusing to me that after getting your modified project.pbxproj file and building with that, reverting that file to the previous version does NOT go back to the broken state. It still builds! Even if I do a clean clone of the repository or try the vanilla improvements-1 project with the Network framework imported - that works too now. It's as if building sucessfully once has put files somewhere outside the project that Xcode now finds even with the previous project.pbxproj?!? |
Robertsmania
left a comment
There was a problem hiding this comment.
This does work, switching the Framework Search Path in Build Settings to look in PrivateFrameworks. But its confusing because at the file system level /System/Library/PrivateFrameworks/Network.framework is a symbolic link that points to /System/Library/Network.framework - so I would have kind of expected it to resolve to the same actual files either way...
Well to be fair, most users shouldn't use the private frameworks. v1.1 uses it for the media remote framework which is private. I just made a guess that it could be conflicting and it turned out to be true :) |

It appears that Xcode is incorrectly attempting to load Network.framework from PrivateFrameworks rather than regular frameworks directory
Builds fine from my Mac, please try it out too.