Page Comparison

...

1. 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:

     • brew update

     • brew uninstall --ignore-dependencies libimobiledevice

     • brew uninstall --ignore-dependencies usbmuxd

     • brew install --HEAD usbmuxd

     • brew install --HEAD libimobiledevice

2. Error while building iOS Simulator

   • While building iOS Simulator, you may face the following error: Building for iOS Simulator, but the linked and embedded framework was built for iOS + iOS Simulator.

     To resolve this error, set Validate Workspace to Yes in the Build Settings tab. 

     

3. 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

4. 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. 

5. 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,

     • Launch XCODE and navigate to Xcode > Preferences > Account .

     • Download all signing profiles manually one-by-one and reboot the system.

     • After reboot, launch Key Chain Access using application finder.

     • Navigate to the Certificate section and from the Trust section, mark all developer certificate as System defaults.

     • Rebuild the Xcode project.

   You may face some issues while setting up the Mac for automation testing. You may refer to this troubleshooting section to resolve these issues

📞📚 Here to Help: Support and Resources

If you have questions that are not addressed in the documentation, you may raise them in the Qualitia Community.