Hi,
I am new to Apple development in general and iOS development in particular.
I've been trying to run UI tests on the simulators (15.0-15.5).
When I run them on a physical device (iPhone), all tests work fine. When I run them on simulators, simulators randomly crash.
Additionally, when I click "erase all contents and settings for the simulator, sometimes it happens very fast (~20 seconds) and sometimes it takes hours and fails to complete. For example, right now iPhone 13 15.5 simulator is stuck erasing. I launched Console tool to capture simulator's error output, and it's spamming this endlessly:
https://imgur.com/xPEBRvi
Almost everything plastered with:
**
CoreSimulatorBridge (Foundation)
**
Attempted to decode a collection type 'NSString' (subclass of 'NSObject') for key 'NS.keys'. 'NSString' requires its subclasses to be explicitly added to the allowed classes list but it is not present. Allowing this has been a source of security issues. Please ensure you meant this type to be in archives: 'NSString' (0x1da9e91d8) [/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.5.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/Foundation.framework]
and
*** -[NSKeyedUnarchiver validateAllowedClass:forKey:] allowed unarchiving safe plist type ''NSString' (0x1da9e91d8) [/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.5.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/Foundation.framework]' for key 'NS.keys', even though it was not explicitly included in the client allowed classes set: '{( "'NSDictionary' (0x1da9c5060) [/Library/Developer/CoreSimulator/Profiles/Runtimes/iOS 15.5.simruntime/Contents/Resources/RuntimeRoot/System/Library/Frameworks/CoreFoundation.framework]" )}'. This will be disallowed in the future.
Occasionally sprinkled in:
Unrecognized token received from com.apple.fileprovider.extension.push from apsd
I tried reinstalling XCode, I tried a clean install by looking up the [list of folders](Uninstall xcode 10 | Apple Developer Forums) online and manually deleting whatever of the following was present on my system:
_/Applications/Xcode.app
~/Library/Caches/com.apple.dt.Xcode
~/Library/Developer
~/Library/MobileDevice
~/Library/Preferences/com.apple.dt.Xcode.plist
/Library/Preferences/com.apple.dt.Xcode.plist
/System/Library/Receipts/com.apple.pkg.XcodeExtensionSupport.bom
/System/Library/Receipts/com.apple.pkg.XcodeExtensionSupport.plist
/System/Library/Receipts/com.apple.pkg.XcodeSystemResources.bom
/System/Library/Receipts/com.apple.pkg.XcodeSystemResources.plist
_
etc. (why doesn't Apple have uninstaller to do all this automatically for a complete clean uninstall??)
I tried deleting and reinstalling the simulators.
I tried different versions of Xcode (14.5.1, 15, 15.1). Nothing helps. I would appreciate any pointers on how to troubleshoot these simulator crashes and slow resets.
Thank you
Post
Replies
Boosts
Views
Activity
I get two error windows at the same time when I try to run UITests using a simulator in the newest XCode Version 14.1 (14B47b):
Could not attach to PID
Problem report
Could not attach to pid : “3297”
Domain: IDEDebugSessionErrorDomain
Code: 3
Failure Reason: tried to attach to process already being debugged
User Info: {
DVTErrorCreationDateKey = "2022-11-03 00:53:03 +0000";
DVTRadarComponentKey = 855031;
IDERunOperationFailingWorker = DBGLLDBLauncher;
RawUnderlyingErrorMessage = "tried to attach to process already being debugged";
}
--
Analytics Event: com.apple.dt.IDERunOperationWorkerFinished : {
"device_model" = "iPhone15,2";
"device_osBuild" = "16.1 (20B72)";
"device_platform" = "com.apple.platform.iphonesimulator";
"launchSession_schemeCommand" = Test;
"launchSession_state" = 1;
"launchSession_targetArch" = "x86_64";
"operation_duration_ms" = 37573;
"operation_errorCode" = 3;
"operation_errorDomain" = IDEDebugSessionErrorDomain;
"operation_errorWorker" = DBGLLDBLauncher;
"operation_name" = IDERunOperationWorkerGroup;
"param_consoleMode" = 0;
"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_MainThreadChecker_stopOnIssue" = 0;
"param_diag_MallocStackLogging_enableDuringAttach" = 0;
"param_diag_MallocStackLogging_enableForXPC" = 0;
"param_diag_allowLocationSimulation" = 1;
"param_diag_checker_tpc_enable" = 0;
"param_diag_gpu_frameCapture_enable" = 3;
"param_diag_gpu_shaderValidation_enable" = 0;
"param_diag_gpu_validation_enable" = 1;
"param_diag_memoryGraphOnResourceException" = 0;
"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_stopOnIssue" = 0;
"param_diag_showNonLocalizedStrings" = 0;
"param_diag_viewDebugging_enabled" = 1;
"param_diag_viewDebugging_insertDylibOnLaunch" = 0;
"param_install_style" = 2;
"param_launcher_UID" = 2;
"param_launcher_allowDeviceSensorReplayData" = 0;
"param_launcher_kind" = 0;
"param_launcher_style" = 0;
"param_launcher_substyle" = 64;
"param_runnable_appExtensionHostRunMode" = 0;
"param_runnable_productType" = "com.apple.product-type.application";
"param_runnable_type" = 1;
"param_testing_launchedForTesting" = 1;
"param_testing_suppressSimulatorApp" = 0;
"param_testing_usingCLI" = 0;
"sdk_canonicalName" = "iphonesimulator16.1";
"sdk_osVersion" = "16.1";
"sdk_variant" = iphonesimulator;
}
--
System Information
macOS Version 13.0 (Build 22A380)
Xcode 14.1 (21534.1) (Build 14B47b)
Timestamp: 2022-11-02T20:53:03-04:00
.
.
.
This has been happening consistently.
When I proceed to try and "Device" ==> "erase all contents and settings" on the Simulator, I get another error "Simulator quit unexpectedly":
Overal, my development experience on my M1 Max has been very miserable. I've been having major issues on two separate M1 Max machines with fresh OS installs.
I would appreciate
Xcode Version 15.0 beta 6 (15A5219j) stuck in the downloading iOS 17.0 state for days.
Any way to mitigate it?
Why does it blatantly ignore the preferences?