@bergersilvio, I meant in your SwiftUI code use only @Published properties don't use something like DATA.depots.dataPoints use DATA.dataPoints instead. Good luck

@bergersilvio DataService needs to be a class for it be an @ObservableObject. Can you try storing dataPoints directly inside DataService and ensure it is @Published? I feel that should help. If that doesn't work if it is ok with you could commit your code (or take a backup) then comment out all unnecessary portions till you can come down to a minimum reproducible code. Commenting out will help you isolate the issue. Then you could create a simple POC so that others can test.

is this on macOS? On macOS I am facing issues as well with widget previews, iOS widget previews are ok. Use the following modifier ..previewContext(WidgetPreviewContext(family: .systemSmall))

I was asked to get in touch with https://developer.apple.com/contact/, I was quite busy with other work that I couldn't contact them. You could contact them. If you happen to find a solution post it

Please read my suggestion below for Apple to come up with a property wrapper to mark SwiftUI preview structs. Hopefully it gets fixed. Currently there is a lot of code with #if DEBUG <…> #endif

If you want it to run on the main thread, why don't you mark it as @MainActor (Swift Concurrency)?

@xcor could you post the workaround code, I tried setting it nil but didn't seem to work for me, not sure I am missing something

@BabyJ Xcode Beta 2 release notes doesn't contain any mention of NavigationSplitView and yet it still occurs in Xcode Beta 2. Was the above quote taken from Xcode Beta 1? Just wondering if we should file feedback.

Sorry I was so lost, that I didn't realise that the rectangular title bar was the new standard, I thought it had appeared because of me executing the command .. :D

Xcode Cloud is a CI (Continuous Integration) / CD (Continuous Delivery) tool, basically you can build and ship builds conveniently (to both beta testers and push it to App Store). It has nothing to do with the simulator, it will create these builds so that beta testers / App Store. I think you are confusing Xcode Cloud with testing

Nice find!! will help a lot of others!!

I feel it would be best to create a feedback via the Feedback Assistant app, you can create feedbacks for tutorials / websites / documentation. I think @Claude31 would know better what option to choose. Your feedback would help others who are learning swift

Thanks a ton!! Saved my day!!

For me I accessed it via the direct Github URL in the search box, it asked me if I wanted to trust it, after clicking on "Trust" it seemed to add it. Definitely a bug though.

Thank you so much!!! Wish this was documented somewhere, this is the correct answer. Note: When you are use using coredata however it is slightly different for the mac, follow https://developer.apple.com/documentation/bundleresources/entitlements/com_apple_security_application-groups