Mandatory Apple Vision Pro OS Upgrade to Seed 5

[OwlchemyDawson]

Apple is requiring all Apple Vision Pro DevKit holders to upgrade their device to Seed 5 by the end of the day on Friday, November 10th. When will Unity support Seed 5?

[victor_unity943]

I am running with seed 5, fully immersive app, 2022.3.10f1. Seems to work about as well as seed 4.

[JackMichaelson]

We’ve been running against seed 5 all week ourselves too.

[OwlchemyDawson]

Fantastic news!

I was afraid after the update that things were going to head south since the older application builds wouldn’t even launch; however, I was pretty much expecting that. Unfortunately, since I can produce device builds with 0.5.0 I am a bit stuck at the moment.

[Alex_StudioDrydock]

Seed 5 has no SDK change and so it also works with PolySpatial 0.4.3 if you’re still on that.

[OwlchemyDawson]

For my current build issue, I only have the XR plugin package for this particular project as it is a VR game. I moved up to 0.5.0, but the same build issue when targeting the device SDK occurs for both 0.4.3 and 0.5.0.

Xcode Project Build Fails After 0.4.3 com.unity.xr.visionos

After upgrading to com.unity.xr.visionos package version 0.4.3, Unity successfully produces an Xcode project but the project build fails with the error below. com.unity.xr.visionos/Runtime/VisionOSNativeBridge.mm:63:5: error: use of undeclared identifier 'ar_session_set_data_provider_state_change_handler'; did you mean 'ar_session_set_data_provider_state_change_handler_with_queue'? ar_session_set_data_provider_state_change_handler(session, nullptr, ^(ar_data_providers_t data_providers, …

(Originally posted to wrong thread)

[puddle_mike]

I’m still a little nervous about pulling the trigger on this - Is anyone running on seed 5 with the legacy Metal renderer for fully immersive apps (i.e no PolySpatial)?

@OwlchemyDawson We are on 0.5.0 now with a similar setup to you. I don’t think I encountered that error, but did at some point have some linker errors until I did a fresh export of the Xcode project (i.e using “Replace”) AND cleared my Library folder. I know you had to do something funky using a local copy of com.unity.xr.visionos, which we did NOT end up needing - so maybe that’s related?

[OwlchemyDawson]

Thanks, @puddle_mike. The build issue seems to be something specific to my project as I can get an AVP VR updated Unity 3D Core template project to build targeting the device SDK without issue. I am working on trying to figure out the difference as time permits.

I have tried a fresh Xcode export a number of times with no luck though. I haven’t cleared my Library folder yet though.

[JackMichaelson]

Yes, we’ve spent a week running with this in both full and mixed reality.

[OwlchemyDawson]

Yeah, no idea how I got my project into this broken state but I finally bit the bullet, deleted the Library folder and reimported. Magically that resolved the issue and I am now able to build to device again.