I had a similar issue with SwiftUI but I was calling the image correctly I was declaring the statusItem inside of didFinishLaunching as there were some bugs The solution was the declare the statusItem as an optional out side didFInishLaunching

I read your app store fiasco, It sucks how much power App store reviewers have. Has it gotten better over the years? Also, I can't answer your question but I have a related question please answer it https://developer.apple.com/forums/thread/681371

https://developer.apple.com/documentation/cloudkit/determining_if_cloudkit_is_right_for_your_app TLDR - CoreData + CK is great for a single user to sync across his devices, it's incredibly easy you can practically ignore the CK part CK only if you want features where the user shares his data with others via his private DB, manage local caches, etc. This is harder.

LazyHStack instead of HStack solved the clipping problem.

Yeah got the same issue in 13.2.1

Man this sucks!! Like async await is supposed to make life easier or worse?