Warning: ftp_nlist() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 438

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_nlist() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 438

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 764

Warning: ftp_nlist() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 438

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_nlist() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 438

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 764

Warning: ftp_mkdir() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 580

Warning: ftp_nlist() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 438

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230

Warning: ftp_pwd() expects parameter 1 to be resource, null given in /home/wvyrfnwn/tutopal.com/wp-admin/includes/class-wp-filesystem-ftpext.php on line 230
Solve the Error “xcrun: error: unable to find utility “instruments”, not a developer tool or in path” - TutoPal

Solve the Error “xcrun: error: unable to find utility “instruments”, not a developer tool or in path”

JavaScript is quite popular among programmers and developers for creating applications and web pages. It is also famous for the frameworks JavaScript offers that add up to programmers’ convenience. React Native is the framework that is frequently used to create mobile applications for Android and iOS. When working with React Native, you may get the error message “xcrun: error: unable to find utility “instruments”, not a developer tool or in path”.

Don’t get panicked when you see the error message as we are here to help you solve the error. We will provide you with simple solutions to tackle the error. First, let’s figure out how the error occurs

How the error pops up

When you try to use a React Native command, you land up in the error warning. Have a look at the command that returns the error:

react-native run-ios

After typing this, you get the following error:

Found Xcode project TestProject.xcodeproj
xcrun: error: unable to find utility "instruments", not a developer   
tool or in PATH

Command failed: xcrun instruments -s
xcrun: error: unable to find utility "instruments", not a developer 
tool or in PATH

You must be wondering what measures to take to get rid of the error. Let’s have a look at the next section to check the options to solve the error

Ways To Tackle the Error Warning “xcrun: error: unable to find utility “instruments”, not a developer tool or in path”

The error appears when you have issues in the command line tools’ location. We have options that can successfully solve the error. Check out the options

Option 1

To get rid of the error warning, you need to follow the before process:

  • Open the Xcode menu in your Xcode
  • Click Preference, and then tap the tab Locations.
  • Here, click the drop-down to choose the Xcode version you have installed.
  • Once done, click to exit Xcode

Check out the Screenshot

Options 2

Another way to resolve the error is to use the command to install as well as set the location of Xcode command line tools. First, you need to use a command if you already have Xcode installed. To set the path, use the following command

sudo xcode-select -s /Applications/Xcode.app

In the case you don’t have command line tools installed, then you need to run the following command first:

xcode-select --install

It is required to accept the license of Xcode prior to installing command line tools. To do that, run the following command

sudo xcodebuild -license accept 

It resolves the error.

Conclusion

In this post, we shed light on the options you can simply try to fix the error “xcrun: error: unable to find utility “instruments”, not a developer tool or in path” efficiently. The options mentioned above are simple yet really effective.

I hope you find it helpful! I wish you happy coding!

Leave a Reply

Your email address will not be published. Required fields are marked *