10 C
London
Saturday, September 28, 2024

ios – VS-Code Flutter debug does not work if I do not compile with Xcode immediately earlier than


For some purpose, working my Flutter app by way of VS-Code does not work anymore, until I compile the App by way of Xcode immediately earlier than it. I get this error:

Error

Couldn't acquire entry to a number of requested file system assets as a result of
CoreDevice was unable to create bookmark knowledge.

Particulars

Couldn't acquire entry to a number of requested file system assets as a result of CoreDevice was unable to create bookmark knowledge.
Area: com.apple.dt.CoreDeviceError
Code: 1005
Consumer Information: {
    DVTErrorCreationDateKey = "2023-09-22 19:02:54 +0000";
    IDERunOperationFailingWorker = IDEInstallCoreDeviceWorker;
    NSURL = "file:///Customers/anon/Library/Developer/Xcode/DerivedData/Runner-abohmwqifnxvoqgcnhfjfotgyrud/Construct/Merchandise/Launch-iphoneos/Runner.app";
}
--
The file couldn’t be opened as a result of it doesn’t exist.
Area: NSCocoaErrorDomain
Code: 260
Failure Motive: The file doesn’t exist.
--

Occasion Metadata: com.apple.dt.IDERunOperationWorkerFinished : {
    "device_isCoreDevice" = 1;
    "device_model" = "iPhone15,2";
    "device_osBuild" = "17.0.1 (21A340)";
    "device_platform" = "com.apple.platform.iphoneos";
    "dvt_coredevice_version" = "348.1";
    "dvt_mobiledevice_version" = "1643.2.4";
    "launchSession_schemeCommand" = Run;
    "launchSession_state" = 1;
    "launchSession_targetArch" = arm64;
    "operation_duration_ms" = 3;
    "operation_errorCode" = 260;
    "operation_errorDomain" = "com.apple.dt.CoreDeviceError.1005.NSCocoaErrorDomain";
    "operation_errorWorker" = IDEInstallCoreDeviceWorker;
    "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.iphoneos";
    "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_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" = 1;
    "param_install_style" = 0;
    "param_launcher_UID" = 2;
    "param_launcher_allowDeviceSensorReplayData" = 0;
    "param_launcher_kind" = 0;
    "param_launcher_style" = 99;
    "param_launcher_substyle" = 8192;
    "param_runnable_appExtensionHostRunMode" = 0;
    "param_runnable_productType" = "com.apple.product-type.utility";
    "param_structuredConsoleMode" = 1;
    "param_testing_launchedForTesting" = 0;
    "param_testing_suppressSimulatorApp" = 0;
    "param_testing_usingCLI" = 0;
    "sdk_canonicalName" = "iphoneos17.0";
    "sdk_osVersion" = "17.0";
    "sdk_variant" = iphoneos;
}
--


System Data

macOS Model 14.0 (Construct 23A339)
Xcode 15.0 (22265) (Construct 15A240d)
Timestamp: 2023-09-22T21:02:54+02:00

This occurs each time if I did not compile the app with Xcode earlier than it. For instance if compile the App with Xcode, I can run it by way of VS-Code, but when I terminate the App and attempt to launch it by way of Xcode once more, I get this error once more, and compiling with Xcode once more fixes it.

I’ve the latest model of Flutter, reinstalled Xcode (+ Deleted each related file) and the Flutter extension, and no customized run config and I did not modify the settings for the Flutter extension.

What may very well be inflicting this?

Latest news
Related news

LEAVE A REPLY

Please enter your comment!
Please enter your name here