Trying to root cause the issue here because this is driving me nuts. From the Console, filtering on process:xcode any:watch, I see the following message which looks suspect: DVTFoundation 2024-04-26 13:44:28.277226 -0700 <Missing Description> DVTDeviceOperation: Started throttledReconnect: { "device_identifier" = "00008301-REDACTED"; "device_isCoreDevice" = 1; "device_model" = "Watch6,18"; "device_osBuild" = "10.5 (21T5560d)"; "device_platform" = "com.apple.platform.watchos"; "device_thinningType" = "Watch6,18"; "dvt_coredevice_version" = "355.26"; "dvt_mobiledevice_version" = "1643.100.58"; "operation_name" = throttledReconnect; } DVTFoundation 2024-04-26 13:45:34.978991 -0700 <Missing Description> DVTDeviceOperation: Started connect: { "device_identifier" = "00008301-REDACTED"; "device_isCoreDevice" = 1; "device_model" = "Watch6,18"; "device_osBuild" = "10.5 (21T5560d)"; "device_platform" = "com.apple.platform.watchos"; "device_thinningType" = "Watch6,18"; "dvt_coredevice_version" = "355.26"; "dvt_mobiledevice_version" = "1643.100.58"; "operation_name" = connect; } Xcode And then later on: DVTFoundation 2024-04-26 13:45:45.808840 -0700 <Missing Description> DVTDeviceOperation: Ended connect: { "device_identifier" = "00008301-REDACTED"; "device_isCoreDevice" = 1; "device_model" = "Watch6,18"; "device_osBuild" = "10.5 (21T5560d)"; "device_platform" = "com.apple.platform.watchos"; "device_thinningType" = "Watch6,18"; "dvt_coredevice_version" = "355.26"; "dvt_mobiledevice_version" = "1643.100.58"; "operation_duration_ms" = 10829; "operation_errorCode" = "-25"; "operation_errorDomain" = "com.apple.dt.deviceprep"; "operation_name" = connect; }

Also just noticed, perhaps with the latest versions of Xcode and iOS, that watchOS connectivity of my Apple Watch Ultra has completely ceased to function. My app's widgets no longer update and I'm unable to pull logs off of the watch to diagnose the issue. My computer sees the watch and allows me to select it as a target deployment device, but when attempting to deploy I get stuck "Waiting to connect" or "Waiting to reconnect".

I've submitted FB13756074 to report this. If you would like to file a dupe, here's content to make it easy: WatchOS logging profile is no longer valid https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=watchos is no longer valid. See attached error that occurs when attempting to install the profile onto my Apple Watch. It seems that without this I’m unable to get any logs off of my Apple Watch, which is making testing/development quite difficult.

Also been running into this a lot over the past few months. Sometimes it's blazingly fast (<1-2 seconds), right now it's been more than a minute and the app is only ~20% "installed" based on the progress circle on the app icon.

One thing that seems to help is, both before and after you generate a new offset stroke, click the "Convert selected points to smooth" button one very anchor point that's meant to be smooth. This often results in a slight tuning of the anchor points, which causes offset strokes to be less error prone and more likely to stay up-to-date across file saves/loads

Adding a "me too" here. Illustrator doesn't seem to handle floating point math particularly well, as you can edit an svg, save that svg, close the svg and reopen it, then just toggle a layer visibility on and off again, save again, and the svg's paths will all have magically changed. The result: a previously working SVG will no longer be exportable into SF Symbols due to some random new points added to a random subset of curves :( I've yet to find a reasonable solution to this yet sadly, but I suspect it has to do with how floating point math and path computing is handled in SVG editors.

FWIW I was able to get past this by manually disabling the flags that Xcode Cloud adds. Add this file to the root of your repo at the following path: ci_scripts/ci_post_clone.sh defaults delete com.apple.dt.Xcode IDEPackageOnlyUseVersionsFromResolvedFile defaults delete com.apple.dt.Xcode IDEDisableAutomaticPackageResolution

FB13167926

Also just noticed this and not seeing an obvious way to fix it sadly :( Will try to make a repro case and add it to another radar.

fwiw I'm still running into this problem today with watchOS 9.1. HTTPCookieStorage.shared.cookies only appears to get set on non-redirected requests. This makes multi-redirect login/auth flows fail, because the cookie handshakes don't occur across redirects.