Same here. Big Sur 14.4 Safari 14.1.1 iPhone 12 Pro Max I can only see the console, sources, and audit. And if I try to run sth in the console, it won't work. I am trying to debug a web view running inside a Unity app, which worked perfectly before upgrading to BigSur 14.4.

Same here. The whole web inspector is completely broken since Big Sur 11.4. Even the tabs that are visible just won't work. At least if I try to debug a web view on my iPhone remotely. Apple, please fix this ASAP! It's unusable.

Did anyone find a solution? It's ****** that you have to push the app to the store first. How should you test it's working, then?

Same problem here, on an Intel MBP. And this does not only happen on every new build, but every time I press "Play", even if no changes have been made. So annoying.

I had to enable Bitcode on all targets of the Pods project. That's pretty annoying.

I'm facing this problem since 2021, as documented here: https://forum.unity.com/threads/app-crashes-when-started-from-testflight-and-closed-again.1090744/ I later found out that it occurs in App Store builds as well, but it is muted, so the user won't see it. Disabling all the code in applicationWillTerminate() seems to be a pretty weird workaround, since there are a lot of clean up routines being called here. Did anybody bring this to Unity's attention yet? Must be a clear bug in Unity's own code.

This is a super important feature for us as well. Would love to see a definitive answer.

I was wondering the same when trying to run my Unity-based iOS app on the Vision Pro Simulator. Did you find out when Xcode actually shows it as a run destination?

I still don't get it. Will it be possible to capture photos or record videos (of the real world) on the device?

Did you find any solution to this? I'm also facing the problem and thought it was related to me updating my Mac to macOS Sonoma. Before, everything worked fine.

I totally agree. I have a macBook 2019 here, which is just fine. The only "reason" to update would be visionOS development, which is ridiculous. Even worse, I just noticed that Apple also killed visionOS support on macOS Sonoma under Intel, even if you use the old Xcode 15 beta 2. Did not see any notice about this before upgrading the OS. I installed macOS Ventura on a separate drive now, just to be able to continue working. It's a shame.

Bump. I also tried to install XCode 15.1 beta 1, which is the recommended version for Unity's PolySpatial 0.6.2, but the download throws an HTTP 400 error.

We applied on the day the application form went online and haven't heard back yet. From the Unity forums I learned that only a very exclusive set of companies got granted access. And they even have to put on window lids to prevent anyone from seeing what they're doing. I learned this when I asked the community if anyone had tried out the glasses outdoors yet.

Update: You can now use the most recent Xcode 15.1 beta 3 with PolySpatial 0.6.2. The Unity docs are outdated.

Besides Apple requiring a Silicon Mac, there is also one caveat that I did not find anywhere in the documentation: You had to set the supported platform in the build settings to "visionossimulator". But this seems to have changed now, and it's just visionos. However, if you come from Unity, they still export "xros" or "xrsimulator" and also do not mention this detail anywhere in their docs. It took me ages to find this out.