Hi @JackRose666, I only saw your question now. I don’t know why the clear and dark modes don’t work in your case. Have you tried to clean the build folder? I’ve noticed that Xcode heavily caches the app icon between builds, so changes might only show up after a „Clean Build Folder“.

Thanks for testing and finding a way to solve this issue. Disabling the blur (or reducing the amount of blur) on layers close to the edge of the canvas helped! 👍

The problem is not that I’m not getting asked to download the simulators. I got initially after download, but it failed. And when downloading it in Xcode settings it continues to fail. Both in β6 and β7. I’ve now downloaded Xcode β5 again and it works. I can’t upload new TestFlights because of this, but at least I can continue developing. And btw, I’ve already filed a feedback as linked in the original post 😉 No response yet, though …

I’ve already tried re-downloading Xcode multiple times. Tried it from xcodereleases.com again and same issue. Once initiating the SDK download it’s stuck a while at the „registering download“ step and then always fails with the error mentioned in the OG post.

I’m using Xcode 26 beta 4 here and it still shows the glass icon on iOS 18 after following those instructions and both naming it "AppIcon". Even after removing the app from my test device and cleaning the build folder. Anyone else having this issue?

From my testing it works as expected using a .stringsdict file. I could not get it to work properly with the newer .xcstrings file, even when properly marking the generated string as „Vary by Plural.“ As Apple is using it in their own example as well, I guess we have to use the .stringsdict. I’ve simply created a separate one just for the AppEntity typeDisplayRepresentations.

Thanks for the response! I’ve filed a feedback with that feature request – if anyone else wants to join with a duplicate: FB16260592

Ups, I totally mixed that up! 😅 Thanks for the hint! Seems like the only viable option that is supported is then to convert to a Double and back for the intents.

I’ve changed the data model in my MigrationPlan, so I don’t think you need to keep the models in sync. Works for me to keep the Core Data model at the old state before switching and migrating to SwiftData. 🤔 Yeah true, that’s weird that the „old“ .sqlite files won’t automatically get transferred. Seems like a bug to me. Thanks for the hints for enabling iCloud! Will keep an eye on that once I get to that, but sounds like I’m already at a good base.

What a bummer that this isn’t supported yet. 😢 I’ve created a feedback now. Please create duplicates and link to this one to show Apple we need this. My feedback number is: FB15094698

Also, you are mentioning that after the configuration I’ll need to move the newly created .store database and rename it to .sqlite and use this from now on. But how do I do that specifically? I guess in the MigrationStage’s didMigrate? Can you help me how to perform this in code with an example? … if that is even necessary considering my comment above. Maybe there is a better way to make the migration find my old store file and then use the default app group location from then on?

Hey, thanks a lot for your detailed response! 🙏 Yes, the migration from Core Data to SwiftData itself works successfully for me. In my case I don’t want to keep the .sqlite name extension … it’s rather that the migration didn’t find the old Core Data for migration and simply created a new database. So how do I get the migration to 1) find my old „Something.sqlite“ Core Data database, 2) then move it to the App Group 3) so that I can then use it for my Widget and enable it for CloudKit?

This is a bit old now and I already managed to get it to work (see my answer below). Though, as yours was basically the same, I’m accepting yours as answer – thanks! My example code shows an alternative way, when the Core Data model was named differently before via NSPersistentContainer(name: "Model").

I was recommended by Apple (in my filed Feedback) that for the Toggle() you have to place .buttonStyle(.borderless) before the .toggleStyle(.button).

Is there a workaround for a Toggle inside a SwiftUI toolbar? I tried using an additional buttonStyle, but that alters the design of the toolbar and doesn’t show the Tip on macOS anyway …