Replies: 1 comment 1 reply
-
Yes, it was safe to ignore the error, and this is fixed in the latest build of uno.check, run |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Just upgraded uno-check to
1.27.0
. When I ran it, I got the following error:At that time, I had Xcode 16.1 and 15.4 installed on my machine ... so I installed Xcode 16.0. Next, I run uno-check again and get the same error.
OK, I'm thinking maybe I'm pointing to the wrong version of the Xcode Command Line Tools? So I launch Xcode and I notice the following...
Hmmm. The error is asking for
16.0 15F31d
but the options say:I've tried both, checked the versions via command line (see below), and I still get the same error in uno-check.
To date, I've had no issues using version 16.1 of the Xcode Command Line tools. Is it safe to ignore this error?
Beta Was this translation helpful? Give feedback.
All reactions