-
Notifications
You must be signed in to change notification settings - Fork 355
bundle exec fastlane oss Fails #691
Comments
Can you please provide some logs? I’m a little confused why it might break an installation |
I can but it seems straight forward to me. The file is attempting to update a repo that doesn't exist yet. The error I kept getting was about the directory Does that make sense now? I'm coming from linux and dug through the syslog & install.log but didn't find anything there. Would I need to look at a ruby log to find this? If so, where would I find that? Or do you need me to clone the repo again and run through it? |
I have the same issue as above |
I have the same issue
Try using the following command to solve problem: |
Cool, thanks for the info everyone. I've opened a PR here to fix things: #693 |
This commit 1ae692b breaks fresh installs. I had to comment out the changes for the initial run then uncomment to update artsy.
The text was updated successfully, but these errors were encountered: