FaultOrdering asserts with resultData == nil

[randarnold]

Environment

Xcode 16.4
Simulator iOS 18.4

What version are you running? Etc.
FaultOrdering 1.0.0 rev 4e2d510

Steps to Reproduce

1. Following the steps in the readme, I integrated FaultOrdering as an XCUITest to run on our production app.
2. I ran the test in the simulator
3. At the end of the test "Waiting for 120s to give the app time to run post-launch" the resultData in nil

Expected Result

I was expecting an "order-file".

Actual Result

The FaultOrderingTest fails and asserts on line 100 "No result data found"

Here is the log from the run:

Running tests...
t = nans Interface orientation changed to Portrait
Test Suite 'Selected tests' started at 2025-06-25 16:08:45.589.
Test Suite 'SpotlightUITests.xctest' started at 2025-06-25 16:08:45.596.
Test Suite 'FaultOrderingLaunchTest' started at 2025-06-25 16:08:45.601.
Test Case '-[SpotlightUITests.FaultOrderingLaunchTest testLaunch]' started.
t = 0.01s Start Test at 2025-06-25 16:08:45.616
t = 0.22s Set Up
parsed linkmap with 54767 symbols
t = 2.54s Open net.spotlightlabs.spotlight
starting server ::1:38825
t = 2.58s Launch net.spotlightlabs.spotlight
t = 5.95s Setting up automation session
t = 11.96s Wait for net.spotlightlabs.spotlight to idle
Waiting for 10s for app to receive the linkmap
t = 27.52s Open net.spotlightlabs.spotlight
t = 27.57s Launch net.spotlightlabs.spotlight
t = 27.58s Terminate net.spotlightlabs.spotlight:84668
t = 30.37s Setting up automation session
t = 33.65s Wait for net.spotlightlabs.spotlight to idle
Waiting for 120s to give the app time to run post-launch
nw_socket_handle_socket_event [C1.1.1:2] Socket SO_ERROR [61: Connection refused]
nw_protocol_socket_set_no_wake_from_sleep [C1.1.1:2] setsockopt SO_NOWAKEFROMSLEEP failed [22: Invalid argument]
nw_protocol_socket_set_no_wake_from_sleep setsockopt SO_NOWAKEFROMSLEEP failed [22: Invalid argument]
nw_endpoint_flow_failed_with_error [C1.1.1 ::1.38824 in_progress socket-flow (satisfied (Path is satisfied), interface: lo0)] already failing, returning
nw_socket_handle_socket_event [C1.1.2:2] Socket SO_ERROR [61: Connection refused]
nw_protocol_socket_set_no_wake_from_sleep [C1.1.2:2] setsockopt SO_NOWAKEFROMSLEEP failed [22: Invalid argument]
nw_protocol_socket_set_no_wake_from_sleep setsockopt SO_NOWAKEFROMSLEEP failed [22: Invalid argument]
nw_endpoint_flow_failed_with_error [C1.1.2 127.0.0.1:38824 in_progress socket-flow (satisfied (Path is satisfied), interface: lo0)] already failing, returning
nw_endpoint_flow_failed_with_error [C1.1.2 127.0.0.1:38824 cancelled socket-flow ((null))] already failing, returning
Connection 1: received failure notification
Connection 1: failed to connect 1:61, reason -1
Connection 1: encountered error(1:61)
Task .<1> HTTP load failed, 0/0 bytes (error code: -1004 [1:61])
Task .<1> finished with error [-1004] Error Domain=NSURLErrorDomain Code=-1004 "Could not connect to the server." UserInfo={_kCFStreamErrorCodeKey=61, NSUnderlyingError=0x600000c71da0 {Error Domain=kCFErrorDomainCFNetwork Code=-1004 "(null)" UserInfo={_NSURLErrorNWPathKey=satisfied (Path is satisfied), interface: en1[802.11], uses wifi, _kCFStreamErrorCodeKey=61, _kCFStreamErrorDomainKey=1}}, _NSURLErrorFailingURLSessionTaskErrorKey=LocalDataTask .<1>, _NSURLErrorRelatedURLSessionTaskErrorKey=(
"LocalDataTask .<1>"
), NSLocalizedDescription=Could not connect to the server., NSErrorFailingURLStringKey=http://localhost:38824/file, NSErrorFailingURLKey=http://localhost:38824/file, _kCFStreamErrorDomainKey=1}

This is a repeatable result (at least for my setup)

[noahsmartin]

Thanks for reporting @randarnold based on those logs the test host isn’t able to communicate with the app being tested (that’s what those url session errors show). I wonder if there is something interfering with connections on localhost, like a firewall. Can you also attach logs from your app so we can see if there are any errors setting up the server on that side? Thanks!

[randarnold]

@noahsmartin Log attached, it is a bit large, but hopefully you will find it useful.

I'm pretty sure that there is no firewall on the simulator, but I don't really know how the simulator interacts with the host Mac. Thank you.

fault order log.txt

[RomanUvarov]

Is no issues with server?
In logs there is 'starting server ::1:38825'
And the error specified server with different port - 38824

[LoveDahlberg]

I had this problem too, it was solved by making sure the UITest scheme ran with Release configuration and with the debugger enabled.