-
Notifications
You must be signed in to change notification settings - Fork 0
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
Issue finding Unity on MacOS and Windows #4
Comments
Gah! Thank you, will look into this today. Any chance you could post your |
Sure!
|
Thanks! I made some changes in 128714f to hopefully address this (on the branch |
Great. I can confirm that branch fixes the issue for me. The unit tests pass and the Unity path is consistently found on MacOS. |
Fantastic, thanks! |
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue. |
Had issues finding Unity on MacOS. This is what I saw in my interactive session:
It works if I remove the logic that adds quotation marks to the path and add a beginning slash on this line:
https://github.com/mikemahoney218/unifir/blob/2e5f90cfc09b4456b3751f932f19da49e0dbebc7/R/find_unity.R#L86
On Windows, the
windows_location()
works fine, butfile.exists(unity)
always returns false with the extra"
added to the path. I think this means even if the user profiles a different unity path, it will always select the default system one.Relatedly, if I run the test locally on MacOS, I get this failure:
The text was updated successfully, but these errors were encountered: