Thanks. It's good to know that others have the same issues. The problem I see is that some prompts work and others don't, so maybe the engineers working on this didn't notice the problem yet. I filed a bug report from the Feedback app. You should do the same just in case.

Unfortunately, Google Drive domain is not allowed in this forum and I can't attach a zip file to a new comment, so there is no way I can share a test project. But the code I posted before is the only thing in the project so any engineer should be able to add it to a new project and see the issues. The issues are always related to the instructions and the prompt, so depending on what you ask, you are going to see one issue or another. I'm going to file a bug report and upload the project there.

Oh, this is a small test project already. All the code is what you see in the conversation, there is nothing else. But I have created a new project with the same code, just in case. Should I create a zip file with this project and attach it to a new message in this conversation? Or should I upload the zip file to something like Google Drive and provide the link?

Thanks. I didn't post the code because it was performing a basic request. I just added the code to the message with the entire view. Let me know if you see something wrong. I'm using all the latest 27 versions (Xcode, iOS and macOS). I removed the instructions, disabled tools, and try many different prompts and instructions, and always get weird behavior. Most of the time, the response includes the JSON code, and when it doesn't, it includes the model's thinking process (see image).

By the way, if I use the prompt and instructions you suggested, the model still complains about not having the right tool. (although it doesn't show the JSON code anymore) Here is the response: "I don't have access to tools that provide descriptions of unicorns. However, unicorns are mythical creatures often described as horse-like with a single spiral horn on their forehead, symbolizing purity and magic in folklore and fantasy."

Thanks for the response, but this doesn't change the app's accent color. For example, if you create a Slider view, it still appears blue (the standard accent color). Creating a new Color set called AccentColor just creates a custom color, it doesn't affect the app's accent color.

Thanks. That's all the info I needed it. Just a recommendation. I watched the What's new in Xcode video, and they don't mention anything about this or other important changes in Xcode, like the need to create your own Assets Catalog file, for example. Those changes should be the first thing to mention in a video like that.

Yes, the current workflow is awful and extremely annoying. But even if the panes are opened correctly, you are still having the conversation on a pane, which means you can easily click on a file an replace it, or close it by accident, or just arrange it in the way you like for Xcode to remove everything when you close the project. Putting the conversation with the agent in a pane makes the agent central to the project, when the agent should be a collaborator, something from the side to help you.

I agree. The new interface is a mess and it takes so much real-estate. Also, the Coding Assistant panel becomes useless. It doesn't make any sense to even be there just to list old conversations when you can get them from other places. Pretty bad design if you ask me.

Hi. I just opened a Playground file in Xcode and I have all the same options available, including all the agents and local models in the chat section. Check Xcode/Settings/Intelligence to make sure what you need is installed and enabled and you will find them on the Navigation Panel when you press the Coding Assistant button and start a new conversation from there.

Thanks. It looks like opening a new panel is the way to go. One alternative is what you mentioned, the other is to manually open the panel from the + button on the toolbar, and the third one is to press Shift + Option and click on the conversation button. Still, it is a fragile layout that can be changed by just clicking on the wrong file at the wrong moment. But at least I have a way to work, thanks for the recommendation.

Awful decision.

I'm going to file my own bug report on Monday because I'm having these problems since iOS 18 Beta 1 and they haven't done anything to fix it. Thanks for the info.

Yes. The value of the relationship is available in the second device, it just doesn't appear on the rows, as you can see in the picture. The system doesn't update the views when they are inside a ForEach loop. I used notifications to force the update but it is not a good solution because this also happens locally, not just with CloudKit. I found a way to fix it by applying the id() modifier to ForEach. It forces the system to update the content of the ForEach every time a new value is available.

That shouldn't be necessary. SwiftData was designed to automatically save the context. Unfortunately, they changed something and now we have to do it manually. Maybe when they release the final version of iOS 18 this is fixed.