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:




  1. The repo contains both a PROJECT.xcworkspace and a project.xcworkspace, but my local folder only contains a PROJECT.xcworkspace

  2. Even more strange, is that in the repo, the lowercased workspace
    folder contains the contents.xcworkspacedata file and the uppercased workspace folder contains the xcshareddata folder (neither contain xcuserdata as that is ignored)

  3. My local PROJECT.xcworkspace contains all that is expected (i.e. contents.xcworkspacedata, xcshareddata/, and xcuserdata/)


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?










share|improve this question






















  • 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















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:




  1. The repo contains both a PROJECT.xcworkspace and a project.xcworkspace, but my local folder only contains a PROJECT.xcworkspace

  2. Even more strange, is that in the repo, the lowercased workspace
    folder contains the contents.xcworkspacedata file and the uppercased workspace folder contains the xcshareddata folder (neither contain xcuserdata as that is ignored)

  3. My local PROJECT.xcworkspace contains all that is expected (i.e. contents.xcworkspacedata, xcshareddata/, and xcuserdata/)


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?










share|improve this question






















  • 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













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:




  1. The repo contains both a PROJECT.xcworkspace and a project.xcworkspace, but my local folder only contains a PROJECT.xcworkspace

  2. Even more strange, is that in the repo, the lowercased workspace
    folder contains the contents.xcworkspacedata file and the uppercased workspace folder contains the xcshareddata folder (neither contain xcuserdata as that is ignored)

  3. My local PROJECT.xcworkspace contains all that is expected (i.e. contents.xcworkspacedata, xcshareddata/, and xcuserdata/)


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?










share|improve this question













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:




  1. The repo contains both a PROJECT.xcworkspace and a project.xcworkspace, but my local folder only contains a PROJECT.xcworkspace

  2. Even more strange, is that in the repo, the lowercased workspace
    folder contains the contents.xcworkspacedata file and the uppercased workspace folder contains the xcshareddata folder (neither contain xcuserdata as that is ignored)

  3. My local PROJECT.xcworkspace contains all that is expected (i.e. contents.xcworkspacedata, xcshareddata/, and xcuserdata/)


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






share|improve this question













share|improve this question











share|improve this question




share|improve this question










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


















  • 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

















active

oldest

votes











Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















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






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































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.




draft saved


draft discarded














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





















































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







這個網誌中的熱門文章

Xamarin.form Move up view when keyboard appear

Post-Redirect-Get with Spring WebFlux and Thymeleaf

Anylogic : not able to use stopDelay()