Me too. I can only get two responses. This one if I run the app on a simulator or "May contain unsafe content" in a playground macro. Getting the feeling that Foundation Models must not really be used by anyone based on the lack of search results.

That led to an App Store Connect warning stating the opposite. App Store Connect Warning Potential Loss of Keychain Access. The previous version of software has an application-identifier value of ['WW2V9Q82B8.com.macplugins.rot13.rot13-intent'] and the new version of software being submitted has an application-identifier of ['WFNDASXC9R.com.macplugins.rot13.rot13-intent']. This will result in a loss of keychain access.

I removed and revoked the signing certificate that was there and had Xcode make new ones (after rereading the docs again). Now I was able to run from Xcode and get it installed. Guess I over think things. As always, thanks for the help!

That development one for me is A9U365295Y. There was a distribution certificate in there with WFNDASXC9R in the common name. I revoked it on Monday to see if that would help as well as clear out all the expired ones. Today I totally removed it, downloaded the old version to the phone and tried again. Same error with the same values. Is there any way to get the identifiers in sync, or is automatic signing forever broken for all my apps now?

Team ID is WFNDASXC9R Xcode keeps using WW2V9Q82B8 What sticks in my mind is that when I started using Apple to host my email domain, I changed the email address somehow with my developer account? It's just that the ID seems the same since these apps have been untouched since long before that. It's funny how the really strange problems end up with you! Thanks!

I'm just doing straight up Xcode with automatically managed signing. I'm getting upgrade errors because the team ID that Xcode has is different from the one showing on the developer portal. The one on the device is right, but the one Xcode is using has the wrong team member ID, so I'm confused.

Some progress. Either waiting a couple of minutes or using the cable for the phone got it to show on Xcode. Hopefully the Transport Error thing will pass now.

At least you can see it! I'm starting to think they are discouraging Apple Watch App development at this point.

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. 

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.

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.

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

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")

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. ☺️

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) }