Create a workspace and copy the full project in it. Then use xCode as an editor.

From your screenshot the binary were uploaded only 2 (88 days expires ) or 4 (86 days expires) days ago. So it can not be waiting for more 7 days ❓

if You write in swift 4 it will be compatible with swift 5. So except if you want to use some specific swift 5 feature (as if let xxx short syntax) so you can use swift 4.

Did you checked in Settings / Confidentiality and Security / Files and Folders or Full disk access ?

Did you tried to remove derives data ? You can nor see if XCode is trying to build/start fir preview by Clocking in the circle ⭕️ on top of window : it show the list of process that XCode is doing (indexing, comp for preview, starting simulator…) tou can also try to change the selected output on the preview tab in the bottom when it enable it (sometime you can choose : currently i did not managed to understand when)

It seems that it happens when choosing "Mac Catalyst" but not when choosing "Mac (Design for iPad)". That may be a workaround.

Another thing to check for CarPlay Simulator is the MacOS Firewall . It is specified in some help that the CarPlay simulator must be enabled in it. By default incoming connections are disabled for all apps. You must add the CarPlay Simulator in the authorised apps.

It is more a problem between you and your client. Who will be the owner if the app ? What will happen when your contract with your client ends ? Also pay attention that you will be required by Apple to certify that you have the right to use client data.

Not sure but you should add some print in your code to see when all your closures execute as you seem to always change queue even when you already are in the same queue. You may do the fetch on main queue or block it from other thread.

Only the developper can send you an invitation code via email or send a TestFlight external test link. Note : better ask the question in English

If you use the same bundle identifier and same profile it may be possible. But if the functionality of the version 2 is not the same as version 1 , AppStore review may be a challenge.

Your layout seems quite unusual in the sense that you put a slider in the middle of nothing. There is seems to have no placement constraint other than obsolete positioning. (may be i am wrong) As show by Claude31 , you should define logical subviews (buttons view, tile view, header view, ...) Then you define how are these subviews arrange in line or column. If you need more complex positionning, you may use a large ZStack and set each subviews to a specific place. Or use en overlay to put the slider in the middle of the global view.

The best would for you to define a TintColor in assets that have a colour value for light mode and another colour value for dark mode

You can still use the binding with getter and setter but not using the short syntax with just the function names : (this could help you if you need to use bindings with getter and setter) VStack { Image(systemName: "globe") .imageScale(.large) .foregroundStyle(.tint) Text("Hello, world!") Toggle("change it", isOn: Binding(get: { getValue() }, set: { newValue in setValue(newValue) })) } .padding() } private func getValue() -> Bool { isOn } private func setValue(_ value: Bool) { isOn = value }