-
Notifications
You must be signed in to change notification settings - Fork 67
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
Build Template Settings has no schemes in dropdown #38
Comments
Can you make sure your scheme is shared? Otherwise Buildasaur won't be able to find it. You can share a scheme in Xcode, Manage Schemes. More here. Let me know if this helps. Otherwise it might be a genuine Buildasaur issue, thanks! |
Oh I see, I don't think I've tested with the scheme being in the workspace instead of the project, let me try to reproduce it locally. |
Yea, I can confirm the scheme shows up if I set to project. Trying that now |
Yes, it doesn't pick it up if it's owned by the workspace. I'll look at it, thanks for reporting it! In the meantime, I'd suggest just selecting the scheme to be owned by the project, if that's possible. I'll try to push a fix ASAP. Did you download Builda as .app or as code? To know whether a new release with the fix will need to be made :) //Edit - just saw your reply. Yeah I'll fix it for workspaces as well but if you could use it in the project that'd fix it for now. |
Yea, I've switched to project all is fine. Thanks for the fast response! |
Actually, I fixed it in #39. Thanks again for reporting! |
Quick followup... Bot Issue: error. Build Service Error. Any chance this is related to the fact I pointed buildasaur at the xcworkspace instead of the project? Both the top left and right say Verified access, all is well! The same ssh keys are working just fine in the actual repo on this machine. |
Can you please copy this to #30? I'm actually working on validation of SSH keys as we speak :) We can discuss there, thanks. |
This is building with an xcworkspace, none of the schemes show up in template settings
The text was updated successfully, but these errors were encountered: