1

I'm trying to setup some UI tests but can't get them to run on devices running pre iOS 12.3.

Even if I start a fresh swift project with 'include UI tests' ticked and try to run the UI tests straight away on a pre iOS 12.3 device I get the following:

2019-05-22 15:42:41.543630+0100 testUITests-Runner[461:45630] Running tests... 2019-05-22 15:42:41.601954+0100 testUITests-Runner[461:45630] The bundle “testUITests” couldn’t be loaded because it is damaged or missing necessary resources. Try reinstalling the bundle. 2019-05-22 15:42:41.602043+0100 testUITests-Runner[461:45630] (dlopen_preflight(/var/containers/Bundle/Application/50D1F2AB-69B9-4C3D-B36B-F84F838E3301/testUITests-Runner.app/PlugIns/testUITests.xctest/testUITests): Library not loaded: @rpath/libswiftCore.dylib Referenced from: /var/containers/Bundle/Application/50D1F2AB-69B9-4C3D-B36B-F84F838E3301/testUITests-Runner.app/PlugIns/testUITests.xctest/testUITests Reason: image not found)

I've seen various questions and answers for the same errors going back to betas of Xcode 6 but none of the suggestions there have helped, including:

  • clean build
  • changing certificate trust rules
  • importing CoreLocation
  • including a dummy swift file
  • altering runpath search paths (seems that's been fixed in Xcode)
  • changing the 'always embed swift standard libraries' build setting

I started on Xcode 10.2 and found the issue, upgrading to Xcode 10.3 hasn't helped.

It was working fine on the 12.2 simulator but fails on a device.

CMash
  • 1,987
  • 22
  • 35

3 Answers3

1

The answer to this is infuriatingly simple. Just make sure, in your build settings, that the UI tests target has the same deployment target as the app.

I'd changed the app to target down to iOS 10 but hadn't thought I'd need to make the same change for the UI tests target.

I'd imagine this is something that should be auto-synced for us, presumably no reason to have them targeting different versions really

CMash
  • 1,987
  • 22
  • 35
  • My main target supports iOS 9.3+. When creating a new XCUITest target with Xcode 10.2 set the default to 12.2. This answer was very helpful. – Jessedc Jul 13 '19 at 23:23
0

I have 2 guesses,

  1. dyld: Library not loaded: @rpath/libswiftCore.dylib

  2. Did you download the the components for the ios versions in components?

Turn your computer on and off & worse case uninstall and reinstall xcode.

Revanth Matha
  • 69
  • 1
  • 5
  • Thanks for the comment. Guess 1 is something I've worked through already, though it's a different error caused by different problems. I don't really understand guess 2... by 'components' do you mean the list of simulators in Preferences? Not sure how that would help! – CMash May 23 '19 at 07:42
0

I've found a workaround for this issue, though it's not necessarily reliable for future versions of Xcode so be wary if you decide to try this out (maybe you'd need to repeat the process after an Xcode upgrade).

If you go to the following directory you'll find all the swift libraries for iPhone devices:

 Applications⁩ ▸ ⁨Xcode⁩ ▸ ⁨Contents⁩ ▸ ⁨Developer⁩ ▸ ⁨Toolchains⁩ ▸ XcodeDefault.xctoolchain⁩ ▸ ⁨usr⁩ ▸ ⁨lib⁩ ▸ ⁨swift⁩ ▸ ⁨iphoneos

You can copy those into your UI tests target (not the app being tested) and then add a copy files build phase to bundle the libraries into the test runner, such that they can be found at runtime. You don't need all the swift libraries, the following image shows which ones I found to be required:

copy files build phase

⁩It's also worth noting that this messes up running the tests on simulator (no doubt in part because these swift libraries that have been copied are the versions for a device), though there may be a way to get around that or maybe that's fine if you don't intend to run them on the simulator

CMash
  • 1,987
  • 22
  • 35