Add visionOS support (#433) (#443) #465
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
b3170c3 to
8326cf1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description:
This PR introduces initial support for visionOS in a basic form.
Comment
As outlined in #433 (comment) the main challenge is the absence of
UIScreenon visionOS. Since the concept of a "screen" in visionOS is ambiguous — potentially infinitely large or nonexistent — I have opted for.zero. This approach aligns with other APIs (eg. amplify-swift visionOS example ) and provides a practical solution for serialization.Testing
Currently, the project’s test setup is configured for iOS only. To enable visionOS testing, I have made modifications in a separate branch: oberbeck@a8d3547
(Note: I updated Nimble to v13, as v12 does not support visionOS.)