I just added the code to the conversation. It is just performing a simple request, but I had to use instructions because otherwise the model was refusing to respond.

Two weeks working with agents in Xcode 27 and I want to kill myself. I have to constantly open and rearrange panels, move panels around, move tabs around, files are opened by mistake in the wrong panel, to start a new conversation I have to make sure I have the right panel selected, otherwise I have to move it from one panel to the other. This is the most annoying interface Xcode ever had. As soon as I finish the current project I'm moving back to Xcode 26. I hope that won't cause any troubles, but this is a nightmare. I filed two bugs already, but I'm sure nothing is going to change. Sad how they ruined a perfect interface.

Just in case someone needs help with this, I was able to make it work. I had to delete the key and the project in aistudio and create a new key and a new project. It looks like the old project was getting flagged or blocked for some reason.

OK. I had to edit my reply because I found an issue. After a while, the agent gives me the error that I don't have enough funds in my API key. I realized that the "Default" option in Gemini is misleading. It sets the agent to work with a paid model. So you have to set a free Flash model first. The problem is that even after that, the agent doesn't respond. I tried all the Flash options, restarting Xcode, signing out and adding the key again, and nothing works. No matter the model I choose, the agent never answers and always gives me the error "JSON 500, not enough funds".

I found a way to do it by adding a new panel and disabling artifacts in the conversation tab, but it is a fragile layout that you can change by accident at any time. Not good, but at least I can work.

This has been happening for at least three years now. The only solution I found so far was killing the coreaudiod process. You can also do it from the Activity Monitor app.

This issue has been resolved today. The new Beta 4 version of iOS 18.1 finally works on old devices as well.

SwiftData still have serious issues, specially when working with CloudKit (iOS 18 Beta). One of the issues I was able to identified is that the views do not update when relationships change. You can see all the values in an object except the values in the relationships (they are nil), but if I force an update on the view, the values show up. I hope they come up with a solution before release, otherwise SwiftData will be completely useless.

I checked and get the same error. The only issue I found with your code is that you declared the property with @State but you should have declared it with @Bindable. But I tried and keep getting the error. It has to be a bug. The only solution was to manage the selection from a @State property (@State private var envProfile: String?)

In Beta 7, all the properties need a default value or be optional. @Model public class Product { public var id:UUID = UUID() public var name: String = "" //relationship public var category:Category? public init(name: String){ self.name = name }

It is a bug. In Beta 3 it was possible to embed the preview code in MainActor.assumeIsolated { }, but this patch no longer works in Beta 4. They are now recommending to run the SwiftData apps in the simulator or a device until they fix the bug.

Same problem. I couldn't find any solution. The macro uses PredicateExpressions enumerations to build the predicate. The enumeration includes a lot of methods but none seems to work for case insensitive searches. I hope they fix this soon or SwiftData becomes completely useless for most cases.

Not sure if it is related, but none of the examples about SwiftData work anymore in Beta 3. They are all broken. I'm getting the error "unsafeMutableAddressor of self" all the time. Maybe it was released ahead of schedule?

The most elegant solution I've found is to extract the view and pass the model to a @Bindable property. @Observable final class View1Model { var text: String = "" } struct View1: View { @State var viewModel = View1Model() var body: some View { View2() .environment(viewModel) } } struct View2: View { @Environment(View1Model.self) var viewModel var body: some View { View3(viewModel: viewModel) } } struct View3: View { @Bindable var viewModel: ViewModel var body: some View { TextField("Text", text: $viewModel.text) } }

I've found the same issue. Deselection still doesn't work in Beta 4. I'm worry.