More on that post-integration trigger. Without the direct clone I noticed that the directory has a partially cloned repository in it. Seems to have either given up part way through the clone or was shutoff by GitHub partially through. Here's the source control log: Jun 24 23:41:34  [26422] : Will attempt to update checkout cache for bot Jun 24 23:41:34  [26422] : Xcode Source Control Blueprint was valid. Jun 24 23:41:34  [26422] : About to update/checkout: https://github.com/endresjd/NewListFeatures (null) into (null)  Jun 24 23:41:34  [26422] : Could not load cached workspace: Error Domain=XCSIntegrationService Code=2 "The repositories have changed since the last integration. Falling back to a clean checkout." UserInfo={NSLocalizedDescription=The repositories have changed since the last integration. Falling back to a clean checkout.} Jun 24 23:41:34  [26422] : An error occurred updating existing checkout: Error Domain=XCSIntegrationService Code=2 "The repositories have changed since the last integration. Falling back to a clean checkout." UserInfo={NSLocalizedDescription=The repositories have changed since the last integration. Falling back to a clean checkout.} Jun 24 23:41:35  [26422] : 10.00% Compressing objects: 100% done Jun 24 23:41:35  [26422] : Error occurred loading revisioned blueprint from workspace: Error Domain=com.apple.dt.SourceControlErrorDomain Code=-300 "The remote repository could not be accessed." UserInfo={com.apple.dt.sourcecontrol.UnderlyingErrorString=, NSLocalizedDescription=The remote repository could not be accessed., NSLocalizedRecoverySuggestion=Make sure a valid repository exists at the specified location and that the correct credentials have been supplied.}

Sorry about the formatting. It insists on removing any line endings. #sigh. Just no quality in things anymore.

It was a bug in Xcode that surfaced in the next beta's release notes. Beta 3 got around this problem, but bots still never finish for random reasons.

I wondering how you run the fix-permissions scripts from a bot. So far Xcode Server is having a 100% failure rate for me. Different errors at different times. Gotta say I love the 1" maximum feedback area in the bot results too. Best you can do is make it smaller. So much vertical whitespace. It's like being on Stack Overflow and having to constantly scroll left and right to read something while you see huge margins on the left and right. I'm thinking that that alone shows the amount of love this isn't getting, so I'm going to give up on it.

There's a "Rebuild..." button. The "..." used to mean it will ask for more info, so I was thinking that might help. Instead it just started a new build without asking anything. I wonder if setting CI_BUILD_NUMBER in the Environment section can bump it up?

FWIW, I’m using an Intel Mac and it’s failing. Thanks @danlloydjones for a workaround.

The actual error I get from App Store Connect is not permitted. 🙄

Me too, but a simple app using Swift Playgrounds on iPad. I sent a message to support about this describing what I was doing, and a copy of the error and got the response: “We're unable to determine the nature of your request. Please reply to this email with clarification”. This was the error I get back in email: ITMS-90334: Invalid Code Signature Identifier - The identifier 'Johnboxgame-numbers_and_letters_that_forums_thinks_are_offensive' in your code signature for 'Johnboxgame' must match its Bundle Identifier 'Johnboxgame' WIth the iPad app there’s not really much I can control as far as what goes in the bundle, and it’s worked in the past.

I kept the #Preview macro by changing it to this, but with warnings about losing global actor 'MainActor': #Preview { @MainActor in ContentView() .frame(minWidth: 500, minHeight: 500) .modelContainer(previewContainer) }

For me, in Xcode 15.0.1 I can see info messages but not debug ones. I guess for Xcode, that's where the debug ones would be the most useful to me. If it matters for this, I'm trying to use it with code generated by a macro, and the client playground file can't use os.log, so I'm using swift-log. Still, can't see debug level messages or a way to turn them on. The trouble here is that my first search hit ended up at Quinn. That usually means I'm out of luck. ☺️

OK. Fine. RTFM. You have to set the log level in the logger to something that includes the level you want to show. var logger = Logger(label: "Client") logger.logLevel = .trace logger.info("logger.info") logger.debug("logger.debug")

The only thing that brings things to normal for me is to quit the simulator app and Xcode. Then relaunch. Still getting it with Xcode 15.0.1. I don't really see the Poster process, just SpringBoard and diagnosed

What I think is interesting, is that the divider seems to be based off of Text elements. It will stretch from the right edge of the screen to the leading edge of the left-most Text element. So if the row begins with, say, a Circle, it won't cover that. Remove the circle and have the text go further left, the divider follows. (In this case the view I have with the Circle is used as the label for the NavigationLink). I would have expected the length of the divider to always be the same, and am not sure if what I'm seeing is correct or not.

Was hoping to look at logs to: See what's mega draining the battery again Get it working in Xcode again Even tried this sysdiagnose thing. That says the profile you can download is no longer valid.

If you wait long enough you will get this error, but you can't respond to that request. If it shows, after you restart your watch and enter your code, it still doesn't connect. If you don't restart, then you will never get prompted.