Since the toolkit package supports visionOS that means I can't stop someone from running the unit tests against visionOS even though most of the tests use components that aren't supported yet for visionOS.
So if someone tries to run the unit tests against visionOS they will see build errors for components that unavailable for visionOS. This fixes those and the tests that can be run I left alone and they succeed.
I wish marking a test class as @available(visionOS, unavailable) would prevent that class from being run on visionOS but it does not so I just hide those test classes behind #if !os(visionOS).
Since the toolkit package supports visionOS that means I can't stop someone from running the unit tests against visionOS even though most of the tests use components that aren't supported yet for visionOS.
So if someone tries to run the unit tests against visionOS they will see build errors for components that unavailable for visionOS. This fixes those and the tests that can be run I left alone and they succeed.
I wish marking a test class as
@available(visionOS, unavailable)
would prevent that class from being run on visionOS but it does not so I just hide those test classes behind#if !os(visionOS)
.