Seems to be a bug in the iOS16 SDK for DatePicker. you can safely ignore it. I can't remember what it was but there is a compiler flag u can set so it reduces the error message down to one line to clean up your console. you can probably find it with a google/stackoverflow/forum search

Start by doing a search on google for swift tutorials and start with an introductory tutorial. If you aren't much of a self learner then enrolling in a programming, IT or computer science course at your local educational institution is another starting point. it sounds like you don't have any background in programming, so yes it will take a significant investment of time. 6-12 months at least if you are serious about it, maybe more.

If you want a syncing solution you can use core data+CloudKit. This will allow your users to use the data offline. The sharing intergration using core data with CloudKit isn’t quite there - it exists but I don’t think anyone has been able to get it to work. But you can share directly with the CloudKit apis and write your own integration with Core data. This is how most people do it. you can also store your data on an external server and access it directly. This will need an internet connection unless u write your own syncing.

same issue when tapping on NavigaitonLink. using new swiftui syntax but not using the programmatic way. 100% CPU freeze.

I didn't think Xcode supported java? I thought it was only C, and apple languages - Objective C, Swift, SwiftUI no?

add .id(UUID()) on the NavigationLink fixes it for me in some cases. I think it's a bug in swiftUI. and I'm sure that there are more appropriate ways of assigning the id, but if u ensure the id is unique then it will fix the freeze in some cases. still doesn't fix it for everything.

I've found that in some cases setting .id(UUID()) on the navigationLink fixes the problem, but it doesn't work all the time.

yes. they give u sample code to setup the stack in swift without using swiftui

this still happens in iOS17 final

I get same issue.

other people having same issue: https://developer.apple.com/forums/thread/737724 and https://developer.apple.com/forums/thread/737724

you are probably having thread contention. they could be blocking each other. it is possible to overwhelm the system with too many threads. sometimes u get better utilisation with less threads. really u only want as many as you have cpu cores running at the same time otherwise they interrupt each other. u can look at the concurrency tool in instruments for some hints.

This still happens in iOS17. anyone know a solution or a workaround? We cant be resetting the environment in production.

this is beta software. downgrade and go back to iOS17

I think NSBundle file:///System/Library/PrivateFrameworks/MetalTools.framework/ principal class is nil because all fallbacks have failed is a bug. I get the same warning with iOS18 final but it doesn't crash. I guess they will fix it next release