Test bundling doesn't work on physical iOS devices

[bartekpacia]

Since iOS 14, Flutter apps built in debug/profile mode must be run through a debugger.

Before test bundling, we've been accomplishing this by doing just this – starting the app under test in debug mode (with the lldb debugger attached using ios-deploy).

This approach breaks with test bundling because we're running every Dart test in a separate app process – which doesn't work, because there's no debugger attached.

In other words, this is prohibited:

[[[XCUIApplication alloc] init] launch];

We depend on the above heavily.

The only workaround I see around this is to build the app in release mode.

See also:

• App crashes on launch on physical iOS 14 device in debug mode when debugger not attached, EXC_BAD_ACCESS (SIGKILL - CODESIGNING) flutter/flutter#60657
• POC Translate Dart-side Flutter integration tests to virtual XCTest on iOS #1236

[bartekpacia]

Trying to run tests in release-built app, but failing to do so. The error (visible in go-ios logs and in Console.app) is:

Failed to create a bundle instance representing '/private/var/containers/Bundle/Application/9A9D727D-E401-46F4-98BB-B4B7888615D9/RunnerUITests-Runner.app.ipa.app/PlugIns/build/ios_integ/Build/Products/Runner_iphoneos16.4-arm64.xctestrun'. Check that the bundle exists on disk.

Possible cause: RunnerTests is present in the .xctestrun, but we want only RunnerUITests nope, most likely not this (still getting the same error after deleting the RunnerTests target)

[bartekpacia]

More notes about the error above: the test runner process dies before testInvocations is called. Verified by:

  +(NSArray<NSInvocation *> *)testInvocations {                                                                 
    NSLog(@"testInvocations called");
    // ...
  }

That line is not visible in the logs.

[bartekpacia]

This issue is about a feature that isn't yet released to the stable channel.

If you're experiencing problems with the stable version, please report a new bug.

[bartekpacia]

This was fixed by #1303. Caveats apply

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar problem, please file a new issue. Make sure to follow the template and provide all the information necessary to reproduce the issue.