[feat] add visionOS support

[eugenehp]

Describe the problem

Add support for Apple Vision Pro

Describe the solution you'd like

same as iOS

Alternatives considered

Working on better support in Tao

Additional context

Current PRs submitted:

• feat: Added visionOS support for Apple Vision Pro wry#1286
• feat: Added visionOS support for Apple Vision Pro SSheldon/rust-objc#123
• feat: Added visionOS support for Apple Vision Pro SSheldon/rust-block#20
• feat: Added visionOS support for Apple Vision Pro cargo-mobile2#340
• feat: Added visionOS support for Apple Vision Pro Brendonovich/swift-rs#63
• feat: Added visionOS support for Apple Vision Pro oconnor663/os_pipe.rs#32
• feat: Added visionOS support for Apple Vision Pro Byron/open-rs#99
• Add Apple visionOS support rust-lang/socket2#503
• Add Apple visionOS support briansmith/ring#2032

[eugenehp]

objc is least likely to merge the PR, so what would be a good course of action here? patch or put a objc2 under Tauri?

[FabianLars]

objc is least likely to merge the PR, so what would be a good course of action here? patch or put a objc2 under Tauri?

@pewsheen is working on porting wry to objc2 already but it's a lot of work.

[eugenehp]

Nice! There's also objc2 by @madsmtm but it doesn't have full API parity with the original objc as far as I know.

So for the time being, what would be the appropriate way to patch this in Tauri (Wry and Tao) @FabianLars

[FabianLars]

tbh I'd probably wait and see if we can get wry ported in time, especially considering that we're still waiting for other projects than objc. Devs that want to use it earlier can use cargo's patch feature to overwrite the crates.io version with your forks.

[eugenehp]

Sounds good. That's what we're using right now – patches. Thinking maybe to put some temporary crates on crates.io to make things easier later, if no news on merging/porting main repos.

[madsmtm]

Linking the issue in Wry for tracking the migration to objc2: tauri-apps/wry#1239

Nice! There's also objc2 by @madsmtm but it doesn't have full API parity with the original objc as far as I know.

Could you expand on what it's missing compared to objc? It's originally a fork of that project, so it should have full feature-parity (and more, ofc ;) ).

[eugenehp]

Oh, perfect, I missed that one. Commented there, in case I can help speed things up.