Nor did I have any problem in a playground, whether in Xcode or in Playgrounds (iPad). I know that the least I could do is to provide a minimal example, and much sooner than this,, but this very code is part of a 5000 LoC project that has more than one deadline this week. This isn't a case of OP-stopped-responding.

My problem persists. I can't start a local Xcode Server from the Xcode Preferences window. Failure (vanilla startup) I've tried both a user account created for the purpose and my admin account. The progress text reaches "Confiuring SSL Certificates…", suspends for a few seconds, then displays an alert with the same sort of content others report, apparently a printout of the NSError with human-readable id: Could not export API server SSL certificate: Error Domain=XCSSecurity Code=-1 "OpenSSL: Error decrypting key, followed by a stack dump of the source files and lines where the error was thrown. (Colorizing the plain text was not my idea.) xcscontrol As suggested on StackOverflow, I tried sudo xcscontrol --reset from the command line. It exited without error. No change. Another reply to that SO question suggested deleting /Library/Developer/XcodeServer/. After quitting Xcode, I did, then restarted Xcode. Same problem. Keychain xcsd I tried xcscontrol --initialize --build-service-user xcodeuser. This resulted in a dialog box asking for the password to a keychain named "xcsd". A user on that stackoverflow exchange reported finding that keychain in Keychain Access, it's not in mine. The System.keychain contains an "Identity Preference" named com.apple.dt.XCSBuilder, which expired in mid-2021. I'm not certain enough to try deleting it. Dead end. xcsd turns out to be a launch daemon embedded in Xcode.app. It embeds a load of JavaScript, much of it Node.js. It also embeds a bash script named create_keychains. It does create an xcsd keychain. It's just a few lines, but I'm not eager to fool with it — especially not knowing what's in $XCSSECURITY_PATH. TEST_PATH=/tmp/XCSTest mkdir -p $TEST_PATH echo "repositories" > $TEST_PATH/RepositoryKeychainSharedSecret "$XCSSECURITY_PATH" keychain-create -k "$TEST_PATH/Repositories.keychain" -m "$TEST_PATH/RepositoryKeychainSharedSecret" echo "xcsd" > $TEST_PATH/XCSDKeychainSharedSecret "$XCSSECURITY_PATH" keychain-create -k "$TEST_PATH/xcsd.keychain" -m "$TEST_PATH/XCSDKeychainSharedSecret" Configuration Xcode 13.2.1 (13C100) macOS 12.1 (21C52) Monterey MacBook Pro M1 (late 2020) 1 TB storage free memory pressure 50–60%, which seems typical CPU near-idle with short runs near-saturated xcode-select is pointed to /Applications/Xcode.app, which is the only instance of Xcode on the machine. (Gosh, maybe I ought to report this to Feedback.)

Oops, sorry: This has manifested on simulators for both iPhone 8 and iPhone 11, both running iOS 13.7.

Has anyone been of help to you since you posted? If so, I'd like to know the solution.I have the same problem. Installing the Xcode Integration add-on and activating it for my account didn't help.Taking the error message at its word, I investigated, I found that we're running Bitbucket Server 5.10, released nearly two years ago, and end-of-life in May. The current versions are 6.9 (Server) and 6.10 (Enterprise), released mid-December and mid-January respectively.So… what version of Bitbucket Server were you using? If you updated, did that resolve the problem?