CocoaPods / CocoaPods/Xcodeproj

Missing attributes

Open
#314 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Ruby
Stars
2.4k
Forks
488
PR merge metrics
No merged PRs in 30d

Description

Versions used:
XCode version: 7.0.1
xcodeproj version: git master

I'm trying to use cocoapods to add some dependencies to our project, only I'm running
into some problems with this.
I'm using Qt to create the initial xcode project.

(1) this looks like a bug and easy to solve:

Some of the build phases miss a name attribute

PBXResourcesBuildPhase
PBXFrameworksBuildPhase
PBXSourcesBuildPhase

some other buildphases do have a name attribute (for example PBXCopyFilesBuildPhase)

Adding a new buildphase from xcode also sets the name attribute (this is the visible name in xcode
under the build phase tab). So It should be supported in order to use a xcode generated project.

(2) would be easy to solve, but I'm not sure the attribute should be there..
An other problem I'm runnin into is missing the refType attribute in PBXFileReference.
This one is also ignored/removed by xcode so maybe it's old?.. (I can't seem to find anything about this)

(3) Definitely not a bug, but maybe an improvement for later...
But this leads to the following question:
Why the choice to bail out when attributes exist that you don't know of? Would it not be more
future proof to ignore the fact that you don't know about them (or just warn the user) and leave the original
value intact?
(this way when something changes things don't break immediatly, but it's still noticed)

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the Qt-generated Xcode project and inspect how xcodeproj reads PBXResourcesBuildPhase, PBXFrameworksBuildPhase, PBXSourcesBuildPhase, and PBXFileReference. Compare their name and refType attributes with an Xcode-generated project; done means the supported attributes and behavior for unknown attributes have been agreed and verified.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.