Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't add Xcode Project/Workspace #140

Closed
concertman opened this issue Sep 29, 2015 · 14 comments
Closed

Can't add Xcode Project/Workspace #140

concertman opened this issue Sep 29, 2015 · 14 comments

Comments

@concertman
Copy link

Greetings! we are really loving Buildasaur. Just having an issue getting a project set up.

on 0.4.0 when I try to add my workspace I get the following message.

Couldn't add Xcode project at path file:///Users/coder/Documents/Projects/iOS/project.xcworkspace, error: Cannot find the Checkout file, please make sure to open this project in Xcode at least once (it will generate the required Checkout file). Then try again..

I follow those steps and still get the same error. I've also tried the steps listed in #127 (just in case) and still couldn't get it to work. I've checked for the presence of .xcworkspace/xcshareddata/PROJECT.xccheckout and there's not one there in the .xcworkspace or in .xcodeproj.

I'm on Xcode 7.

Any suggestions on what I can do to resolve this?

@czechboy0
Copy link
Member

Hi @concertman, sorry that you're having this issue. Xcode 7 seems to have changed the way they generate the checkout file (to the point that I'm not sure when it generates it, if at all).

I am still in the process of trying to figure out what changed, because all the users who have been using Buildasaur from before Xcode 7 are fine (the fine is there and checked into their repo).

There is a way to create the file manually, even though it's a bit fiddly, I described it here. The person I wrote it for got it working that way.

Let me know what you end up doing, I'd love to help as much as I can.

@czechboy0
Copy link
Member

Also, just to check, does the file .xcworkspace/xcshareddata/PROJECT.xcscmblueprint (different file extension) exist? I think that's the new format that Xcode is using.

@Raman148
Copy link

If you have the luxury, simply open the project in Xcode6.4 and then in Xcode 7.
Opening it in 6.4 will auto generate this file

@czechboy0
Copy link
Member

@Raman148 Oh have you actually tried that? Amazing, I was wondering whether that would help. @concertman This is definitely a better solution than having to hack the checkout file yourself :)

Thanks @Raman148!

@Raman148
Copy link

@czechboy0 Confirmed on my end, I had this issue this morning when migrating.

Thank you!

@czechboy0
Copy link
Member

@Raman148 Thanks again, I'll recommend this as a troubleshooting step before I can make Xcode generate these files for us reliably.

Also, in #141 I just added support for .xcscmblueprint files, which, I believe, is what Xcode 7 prefers to generate (sometimes).

@czechboy0
Copy link
Member

@concertman Please try what @Raman148 suggested and let me know if that fixed it for you, thaaaaanks! 😉

@czechboy0
Copy link
Member

Also, @concertman please update to 0.5.0 before you try again, maybe you at least had an xcscmblueprint file there, which would now get picked up by Buildasaur, thanks!

@concertman
Copy link
Author

@czechboy0 I just tried 0.5.0 locally and it seems to work. I'm about to try it on my Xcode CI server to confirm. I'll post back once I have done that.

@czechboy0
Copy link
Member

Ha, if just upgrading to 0.5.0 alone fixed it, it means you had the newer
format checkout file there (xcscmblueprint). Make sure to keep that checked
in in git. Feel free to ping me if you need any help setting Buildasaur up!
On Wed, Sep 30, 2015 at 12:23 PM Jarod McBride [email protected]
wrote:

@czechboy0 https://github.com/czechboy0 I just tried 0.5.0 locally and
it seems to work. I'm about to try it on my Xcode CI server to confirm.
I'll post back once I have done that.


Reply to this email directly or view it on GitHub
#140 (comment)
.

@concertman
Copy link
Author

@czechboy0 just tested it on our server and it's up and running fine. I verified that yes our workspace is using the xcscmblueprint (our project started in Xcode 7 beta) and never did have the .xccheckout file.

Thanks for the help!

@czechboy0
Copy link
Member

Thanks @concertman, this is great to know in case other people are having the same issue.

@grantjk
Copy link

grantjk commented Oct 14, 2015

@czechboy0 Getting this same issue on 0.6.

This project is an older project (pre Xcode7), but currently has a xcscmblueprint file in the .workspace/xcshareddata/. I've created a bot manually that runs fine, but can't get past adding the workspace file in the buildasaur creation workflow

@czechboy0
Copy link
Member

You're saying it has a blueprint file but Buildasaur isn't finding it? That's a bug, can you please create a new issue with all the details? Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants