Document toolboxDocument toolbox

Common Errors while Configuring Mac

Owned by ravi.chandran (Unlicensed)
Feb 10, 2021

You may face some issues while configuring Mac to execute Qualitia automated test cases. This section helps you to resolve the issues coming at the time of configuring Mac.

Requested 'libusbmuxd >= 1.1.0' but version of libusbmuxd is 1.0.10

To resolve this error:

Launch terminal and execute following commands one by one:

  1. brew update
  2. brew uninstall --ignore-dependencies libimobiledevice
  3. brew uninstall --ignore-dependencies usbmuxd
  4. brew install --HEAD usbmuxd
  5. brew install --HEAD libimobiledevice

Error while brew install --HEAD usbmuxd

While executing the brew install --HEAD usbmuxd command from the list above, you may face the following error. This error appears due to compliance and IT policies of the organization.

fatal: unable to access 'https://git.sukimashita.com/libusbmuxd.git/': SSL certificate problem: self signed certificate in certificate chain

To resolve this error, ask IT team to unblock access to  https://git.sukimashita.com/libusbmuxd.git

Error while xcpretty

While executing the gem install xcpretty command from the list above, you may face the following error.

ERROR:  Could not find a valid gem 'xcpretty' (>= 0), here is why:

Unable to download data from https://rubygems.org/ - SSL_connect SYSCALL returned=5 errno=0 state=SSLv3 read server hello A (https://api.rubygems.org/specs.4.8.gz)

To resolve this error, ask IT team to unblock access to: https://rubygems.org/

Error:  You don't have write permissions for the /Library/Ruby/Gems/2.3.0 directory.

To resolve this error, use sudo gem install xcpretty command. 

Command CodeSign failed with a nonzero exit code

While building a webdriver agent project in Xcode, you may face this error.

To resolve this error, 

  1. Launch XCODE and navigate to Xcode > Preferences > Account .
  2. Download all signing profiles manually one-by-one and reboot the system.
  3. After reboot, launch Key Chain Access using application finder.
  4. Navigate to the Certificate section and from the Trust section, mark all developer certificate as System defaults.
  5. Rebuild the Xcode project.