Now getting the below error when attempting to run a test:
The operation couldn’t be completed. (Mach error -308 - (ipc/mig) server died)
Full output shared with Apple via Xcode report tool:
The operation couldn’t be completed. (Mach error -308 - (ipc/mig) server died)
Domain: NSMachErrorDomain
Code: -308
User Info: {
DVTErrorCreationDateKey = "2024-09-22 20:22:49 +0000";
IDERunOperationFailingWorker = IDELaunchiPhoneSimulatorLauncher;
}
--
Event Metadata: com.apple.dt.IDERunOperationWorkerFinished : {
"device_identifier" = "3E373B82-D722-4B34-86EE-371210EA496A";
"device_model" = "iPhone17,2";
"device_osBuild" = "18.0 (22A3351)";
"device_platform" = "com.apple.platform.iphonesimulator";
"device_thinningType" = "iPhone17,2";
"dvt_coredevice_version" = "397.21";
"dvt_coresimulator_version" = 987;
"dvt_mobiledevice_version" = "1759.2.1";
"launchSession_schemeCommand" = Run;
"launchSession_state" = 1;
"launchSession_targetArch" = arm64;
"operation_duration_ms" = 1738;
"operation_errorCode" = "-308";
"operation_errorDomain" = NSMachErrorDomain;
"operation_errorWorker" = IDELaunchiPhoneSimulatorLauncher;
"operation_name" = IDERunOperationWorkerGroup;
"param_debugger_attachToExtensions" = 0;
"param_debugger_attachToXPC" = 1;
"param_debugger_type" = 3;
"param_destination_isProxy" = 0;
"param_destination_platform" = "com.apple.platform.iphonesimulator";
"param_diag_113575882_enable" = 0;
"param_diag_MainThreadChecker_stopOnIssue" = 0;
"param_diag_MallocStackLogging_enableDuringAttach" = 0;
"param_diag_MallocStackLogging_enableForXPC" = 1;
"param_diag_allowLocationSimulation" = 1;
"param_diag_checker_tpc_enable" = 1;
"param_diag_gpu_frameCapture_enable" = 0;
"param_diag_gpu_shaderValidation_enable" = 0;
"param_diag_gpu_validation_enable" = 0;
"param_diag_guardMalloc_enable" = 0;
"param_diag_memoryGraphOnResourceException" = 0;
"param_diag_mtc_enable" = 1;
"param_diag_queueDebugging_enable" = 1;
"param_diag_runtimeProfile_generate" = 0;
"param_diag_sanitizer_asan_enable" = 0;
"param_diag_sanitizer_tsan_enable" = 0;
"param_diag_sanitizer_tsan_stopOnIssue" = 0;
"param_diag_sanitizer_ubsan_enable" = 0;
"param_diag_sanitizer_ubsan_stopOnIssue" = 0;
"param_diag_showNonLocalizedStrings" = 0;
"param_diag_viewDebugging_enabled" = 1;
"param_diag_viewDebugging_insertDylibOnLaunch" = 1;
"param_install_style" = 2;
"param_launcher_UID" = 2;
"param_launcher_allowDeviceSensorReplayData" = 0;
"param_launcher_kind" = 0;
"param_launcher_style" = 0;
"param_launcher_substyle" = 0;
"param_runnable_appExtensionHostRunMode" = 0;
"param_runnable_productType" = "com.apple.product-type.application";
"param_structuredConsoleMode" = 1;
"param_testing_launchedForTesting" = 0;
"param_testing_suppressSimulatorApp" = 0;
"param_testing_usingCLI" = 0;
"sdk_canonicalName" = "iphonesimulator18.0";
"sdk_osVersion" = "18.0";
"sdk_variant" = iphonesimulator;
}
--
System Information
macOS Version 15.0 (Build 24A335)
Xcode 16.0 (23051) (Build 16A242d)
Timestamp: 2024-09-22T14:22:49-06:00
Post
Replies
Boosts
Views
Activity
@DTS Engineer Not OP but I am also seeing this issue on Xcode 16.0 (16A242d). I am attempting to run a test to an iPhone 16 Pro/18.0 sim and as @hogman78 said, sim never launches and test runner just hangs. Sim opens fine running & building, but not for UI tests. Tried resetting device (device > erase...) and building to something different, same behavior. Restarted MBP, no change. Sequoia 15.0
I've discovered that using Text(timerInterval:) and setting countsDown=true achieves the same effect as the native Timer when the screen locks
This happens to me as well, have not been able to figure out yet. I'm trying to reproduce the Timer app live activity behavior where for example a "2:37" minutes timer switches to "2:--" when the display sleeps
Same. Hoping to find a non-beta solution as well.
Same here. M1 Pro MacBook Pro and iPhone 15 Pro Max, all on latest OS and Xcode (15.2). Connected via USB cable, and the app launches instantly but its just a blank screen for 20-40+ seconds. About 50% of the time I just have to kill the build and restart because it gets stuck and my app's UI just never shows.
But when I turn wifi off on the device, it's nearly instant as expected. Also no issues at all building to a simulator. Building to a physical device is completely unusable for me currently.
Screen shot of what it's supposed to look like on first load, but instead currently it only looks like this after the supplementary view/cell have been reused:
Here are the CustomHeader and CustomCell classes (restricted due to post character limit):
CustomHeader:
class CustomHeader: UICollectionReusableView {
private lazy var label = makeLabel()
override init(frame: CGRect) {
super.init(frame: frame)
backgroundColor = UIColor.systemBlue.withAlphaComponent(0.10)
setupViews()
}
required init?(coder: NSCoder) {
fatalError("init(coder:) has not been implemented")
}
func set(headerText: String) {
DispatchQueue.main.async {
self.label.text = headerText
}
}
private func setupViews() {
addSubview(label)
NSLayoutConstraint.activate([
label.topAnchor.constraint(equalTo: topAnchor),
label.leadingAnchor.constraint(equalTo: leadingAnchor),
label.trailingAnchor.constraint(equalTo: trailingAnchor),
label.bottomAnchor.constraint(equalTo: bottomAnchor)
])
}
private func makeLabel() -> UILabel {
let label = UILabel()
label.text = "Header Title"
label.font = UIFont.systemFont(ofSize: 18, weight: .semibold)
label.textColor = .label
label.textAlignment = .left
label.numberOfLines = 0
label.translatesAutoresizingMaskIntoConstraints = false
return label
}
}
CustomCell:
class CustomCell: UICollectionViewCell {
private lazy var label = makeLabel()
private let padding: CGFloat = 20
override init(frame: CGRect) {
super.init(frame: frame)
setupViews()
}
required init?(coder: NSCoder) {
fatalError("init(coder:) has not been implemented")
}
func set(cellText: String) {
DispatchQueue.main.async {
self.label.text = cellText
}
}
private func setupViews() {
backgroundColor = .secondarySystemGroupedBackground
layer.cornerRadius = 12
layer.cornerCurve = .continuous
contentView.addSubview(label)
NSLayoutConstraint.activate([
label.topAnchor.constraint(equalTo: contentView.topAnchor, constant: padding),
label.leadingAnchor.constraint(equalTo: contentView.leadingAnchor, constant: padding),
label.trailingAnchor.constraint(equalTo: contentView.trailingAnchor, constant: -padding),
label.bottomAnchor.constraint(equalTo: contentView.bottomAnchor, constant: -padding)
])
}
private func makeLabel() -> UILabel {
let label = UILabel()
label.text = "No text available."
label.font = UIFont.systemFont(ofSize: 15, weight: .regular)
label.textColor = .label
label.textAlignment = .left
label.numberOfLines = 0
label.translatesAutoresizingMaskIntoConstraints = false
return label
}
}
I had the same issue. macOS 12.4, downloaded the first Xcode 14 beta and noticed right away that "toggle appearance" in the simulator no longer works, even when going back to Xcode 13.4. Only option is to trigger manually via Settings > Developer in the simulator.
I tried @bunnyhero 's approach and it worked! Thank you!
We are seeing this issue on our large project. Any recommendations to resolve?
M1 Pro (MacBook Pro, 2021, 16-inch)
macOS Monterey 12.2
Xcode 13.1
iOS 15.0 simulator
Running Xcode via Rosetta due to a dependency that has not supported arm yet.
We just switched over our text entry methods from using XCUIElement.typeText(...) to using paste instead because of the slow typing bug on iOS 15.0+ simulators with the .typeText() method. We paste text into the simulator via setting the string in UIPasteboard.general.string, then triggering & tapping the "Paste" menu item for a text entry element. No errors are thrown or seen, the "<app_name> pasted from..." toast alert shows, but the text just never appears in the app.
The issue persists in the same environment but on a iOS 14.5 simulator, so it doesn't seem to be specific to iOS 15.0+ simulators.
Just downloaded the Xcode 13.2 Beta, which the release notes say has addressed this issue, and no luck. Seeing the same behavior for Xcode 13.2 Beta even after rebooting all devices again. Mac, iPhone, and Apple Watch are on the latest software.
This still seems to be an issue on Xcode 13.1 on M1Pro 14" MacBook Pro.
I see the same error with trying run on on my iPhone 13 Pro Max. Stalls every time on a fresh build, but it will resolve itself after 5 or so minutes and then isn't an issue on subsequent runs. Quitting Xcode and re-opening repeats this process. It never resolves when trying to build to device via network, only when plugged in. Ugh.
Anyone found a solid solution for this? Calling collectionView.collectionViewLayout.invalidateLayout() immediately after my dataSource.apply() call gets the cells to display correctly prior to beginning scrolling, but it seems hacky and doesn't look great while the data loads into the cells.
Having this issue on Xcode 12.5 & iOS 14.6 as well. Previously had no difficulty getting auto-height cells using NSCollectionLayoutSize.estimated() for heights, but now they only correct themselves after scroll begins.
Any resolution yet?
I was having a similar issue, was basically trying to recreate the triple column behavior of the Contacts app on iPad in iOS14. Here's what I found works for me:
I figured out that it's important to set BOTH .preferredDisplayMode and .preferredSplitBehavior when the view transitions. Setting just one or the other will result in lots of weird behavior.
What I figured out works for this case is setting preferredDisplayMode = .twoBesideSecondary and preferredSplitBehavior = .tile when the screen is wide enough to fit all 3 columns, and when it is not, set preferredDisplayMode = .oneBesideSecondary and preferredSplitBehavior = .displace.
I used a function that checks if the view.frame.size.width < 1194 to determine if the screen is full width or not, as using orientation only would cause problems if the app is side by side with another. I'll probably tweak that value over time so don't take it as gospel, but it works for now. I call this function in viewDidLoad for initially setting the behaviors, then again in viewWillTransition(toSize:), using the size property there to update the behaviors.