Bug 1. Based on your original code the async request function is not using any form of a wait or suspension point to signal when the dataTask call completes. You should consider fixing that. If request returns void then continuation.resume(returning: ()) will also work informing the caller of the request function that the suspension point can resume from the current await request call.

I'm not Apple nor a Lawyer.

The product has been built and in use for many years now.

I’m not doing anything special other than trying to launch Xcode and it opens sometimes and other times it doesn’t on my intel cpu. So somewhere during launch on the intel the wrong architecture is being automatically selected.

For support on any Unity plugins go to the unity developer forums and post your issues there and unity or the unity 3rd party developer can fix it for you. The plugins used in unity are in no way supported by Apple. Or contact the developer of the unity plugin.

Read the documentation.

Something like this will never fly for privacy reasons. Also, don't compare Apples to Robots. One is more organic than the other.

Desktops and mobile devices do not use the same colour profiles.

See the use cases on how and when it should be used.https://github.com/apple/swift-evolution/blob/main/proposals/0335-existential-any.md

Let me take a look and get back to you ...

I was never given any option to convert to a single target watch app the extra target just went away. No reversions of any kind were attempted. So somewhere in the Xcode.project schema, as you have mentioned, there is a reference to a WKExtension or something.

The app no longer runs after launching on any of the destinations - sim & phone. An Xcode alert with the verbiage provided above is shown instead.

You just can't do what you're thinking

Thank you Kyra