Local vs. Repo project.xcworkspace inconsistency
up vote
0
down vote
favorite
I am attempting to add a new iOS app into bitrise, but during the validation process I am getting the error: contents.xcworkspacedata does not exist at: PROJECT.xcworkspace/contents.xcworkspacedata
When I look in my repo and my local folder, I notice a couple of things:
- The repo contains both a
PROJECT.xcworkspace
and aproject.xcworkspace
, but my local folder only contains aPROJECT.xcworkspace
- Even more strange, is that in the repo, the lowercased workspace
folder contains thecontents.xcworkspacedata
file and the uppercased workspace folder contains thexcshareddata
folder (neither contain xcuserdata as that is ignored) - My local
PROJECT.xcworkspace
contains all that is expected (i.e.contents.xcworkspacedata
,xcshareddata/
, andxcuserdata/
)
Bitrise validation is failing because it is looking for the file in PROJECT.xcworkspace
in the repo, not project.xcworkspace
where that file is actually located.
The name of the workspace has always been capitalized from the initialization of the project, so I don't understand why there would be a lowercased version in the repo.
Is this some random bug that occurred, or what is a good way to resolve this issue?
ios xcode git bitrise
add a comment |
up vote
0
down vote
favorite
I am attempting to add a new iOS app into bitrise, but during the validation process I am getting the error: contents.xcworkspacedata does not exist at: PROJECT.xcworkspace/contents.xcworkspacedata
When I look in my repo and my local folder, I notice a couple of things:
- The repo contains both a
PROJECT.xcworkspace
and aproject.xcworkspace
, but my local folder only contains aPROJECT.xcworkspace
- Even more strange, is that in the repo, the lowercased workspace
folder contains thecontents.xcworkspacedata
file and the uppercased workspace folder contains thexcshareddata
folder (neither contain xcuserdata as that is ignored) - My local
PROJECT.xcworkspace
contains all that is expected (i.e.contents.xcworkspacedata
,xcshareddata/
, andxcuserdata/
)
Bitrise validation is failing because it is looking for the file in PROJECT.xcworkspace
in the repo, not project.xcworkspace
where that file is actually located.
The name of the workspace has always been capitalized from the initialization of the project, so I don't understand why there would be a lowercased version in the repo.
Is this some random bug that occurred, or what is a good way to resolve this issue?
ios xcode git bitrise
Something like this (capitalization issue) can frequently happen in git if you change the capitalization of the file. Did you check what happens if you do a new, clean git clone into a new directory? Is the workspace file there upper or lowercase? See also e.g. stackoverflow.com/questions/13201906/… If these wouldn't help we might need more info/the logs - I'd suggest you to send those to our support who can check it & help you there.
– Viktor Benei
Nov 13 at 17:39
1
@ViktorBenei It was some weird bug with git... I just deleted the capitalized .xcworkspace folder directly in the git repo, and then re-pushed and everything was fine... Must have just been a git bug.
– Tanner Juby
Nov 13 at 19:11
Indeed I think you were "tricked" by the git case insensitivity behaviour - discuss.bitrise.io/t/react-native-unable-to-resolve-module/2359/…
– Viktor Benei
Nov 15 at 16:19
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am attempting to add a new iOS app into bitrise, but during the validation process I am getting the error: contents.xcworkspacedata does not exist at: PROJECT.xcworkspace/contents.xcworkspacedata
When I look in my repo and my local folder, I notice a couple of things:
- The repo contains both a
PROJECT.xcworkspace
and aproject.xcworkspace
, but my local folder only contains aPROJECT.xcworkspace
- Even more strange, is that in the repo, the lowercased workspace
folder contains thecontents.xcworkspacedata
file and the uppercased workspace folder contains thexcshareddata
folder (neither contain xcuserdata as that is ignored) - My local
PROJECT.xcworkspace
contains all that is expected (i.e.contents.xcworkspacedata
,xcshareddata/
, andxcuserdata/
)
Bitrise validation is failing because it is looking for the file in PROJECT.xcworkspace
in the repo, not project.xcworkspace
where that file is actually located.
The name of the workspace has always been capitalized from the initialization of the project, so I don't understand why there would be a lowercased version in the repo.
Is this some random bug that occurred, or what is a good way to resolve this issue?
ios xcode git bitrise
I am attempting to add a new iOS app into bitrise, but during the validation process I am getting the error: contents.xcworkspacedata does not exist at: PROJECT.xcworkspace/contents.xcworkspacedata
When I look in my repo and my local folder, I notice a couple of things:
- The repo contains both a
PROJECT.xcworkspace
and aproject.xcworkspace
, but my local folder only contains aPROJECT.xcworkspace
- Even more strange, is that in the repo, the lowercased workspace
folder contains thecontents.xcworkspacedata
file and the uppercased workspace folder contains thexcshareddata
folder (neither contain xcuserdata as that is ignored) - My local
PROJECT.xcworkspace
contains all that is expected (i.e.contents.xcworkspacedata
,xcshareddata/
, andxcuserdata/
)
Bitrise validation is failing because it is looking for the file in PROJECT.xcworkspace
in the repo, not project.xcworkspace
where that file is actually located.
The name of the workspace has always been capitalized from the initialization of the project, so I don't understand why there would be a lowercased version in the repo.
Is this some random bug that occurred, or what is a good way to resolve this issue?
ios xcode git bitrise
ios xcode git bitrise
asked Nov 8 at 18:38
Tanner Juby
788
788
Something like this (capitalization issue) can frequently happen in git if you change the capitalization of the file. Did you check what happens if you do a new, clean git clone into a new directory? Is the workspace file there upper or lowercase? See also e.g. stackoverflow.com/questions/13201906/… If these wouldn't help we might need more info/the logs - I'd suggest you to send those to our support who can check it & help you there.
– Viktor Benei
Nov 13 at 17:39
1
@ViktorBenei It was some weird bug with git... I just deleted the capitalized .xcworkspace folder directly in the git repo, and then re-pushed and everything was fine... Must have just been a git bug.
– Tanner Juby
Nov 13 at 19:11
Indeed I think you were "tricked" by the git case insensitivity behaviour - discuss.bitrise.io/t/react-native-unable-to-resolve-module/2359/…
– Viktor Benei
Nov 15 at 16:19
add a comment |
Something like this (capitalization issue) can frequently happen in git if you change the capitalization of the file. Did you check what happens if you do a new, clean git clone into a new directory? Is the workspace file there upper or lowercase? See also e.g. stackoverflow.com/questions/13201906/… If these wouldn't help we might need more info/the logs - I'd suggest you to send those to our support who can check it & help you there.
– Viktor Benei
Nov 13 at 17:39
1
@ViktorBenei It was some weird bug with git... I just deleted the capitalized .xcworkspace folder directly in the git repo, and then re-pushed and everything was fine... Must have just been a git bug.
– Tanner Juby
Nov 13 at 19:11
Indeed I think you were "tricked" by the git case insensitivity behaviour - discuss.bitrise.io/t/react-native-unable-to-resolve-module/2359/…
– Viktor Benei
Nov 15 at 16:19
Something like this (capitalization issue) can frequently happen in git if you change the capitalization of the file. Did you check what happens if you do a new, clean git clone into a new directory? Is the workspace file there upper or lowercase? See also e.g. stackoverflow.com/questions/13201906/… If these wouldn't help we might need more info/the logs - I'd suggest you to send those to our support who can check it & help you there.
– Viktor Benei
Nov 13 at 17:39
Something like this (capitalization issue) can frequently happen in git if you change the capitalization of the file. Did you check what happens if you do a new, clean git clone into a new directory? Is the workspace file there upper or lowercase? See also e.g. stackoverflow.com/questions/13201906/… If these wouldn't help we might need more info/the logs - I'd suggest you to send those to our support who can check it & help you there.
– Viktor Benei
Nov 13 at 17:39
1
1
@ViktorBenei It was some weird bug with git... I just deleted the capitalized .xcworkspace folder directly in the git repo, and then re-pushed and everything was fine... Must have just been a git bug.
– Tanner Juby
Nov 13 at 19:11
@ViktorBenei It was some weird bug with git... I just deleted the capitalized .xcworkspace folder directly in the git repo, and then re-pushed and everything was fine... Must have just been a git bug.
– Tanner Juby
Nov 13 at 19:11
Indeed I think you were "tricked" by the git case insensitivity behaviour - discuss.bitrise.io/t/react-native-unable-to-resolve-module/2359/…
– Viktor Benei
Nov 15 at 16:19
Indeed I think you were "tricked" by the git case insensitivity behaviour - discuss.bitrise.io/t/react-native-unable-to-resolve-module/2359/…
– Viktor Benei
Nov 15 at 16:19
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53214139%2flocal-vs-repo-project-xcworkspace-inconsistency%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Something like this (capitalization issue) can frequently happen in git if you change the capitalization of the file. Did you check what happens if you do a new, clean git clone into a new directory? Is the workspace file there upper or lowercase? See also e.g. stackoverflow.com/questions/13201906/… If these wouldn't help we might need more info/the logs - I'd suggest you to send those to our support who can check it & help you there.
– Viktor Benei
Nov 13 at 17:39
1
@ViktorBenei It was some weird bug with git... I just deleted the capitalized .xcworkspace folder directly in the git repo, and then re-pushed and everything was fine... Must have just been a git bug.
– Tanner Juby
Nov 13 at 19:11
Indeed I think you were "tricked" by the git case insensitivity behaviour - discuss.bitrise.io/t/react-native-unable-to-resolve-module/2359/…
– Viktor Benei
Nov 15 at 16:19