Kyle Ye

OpenSwiftUI 0.17.0 release: - Add Xcode Preview support - Add Text rendering - Add OpenSwiftUI xcframework support - Update framework logo See full release notes: github.com/OpenSwiftUIPro… #OpenSwiftUI #OSUI

First thanks for your PR @pepicrft , but I have hit some problem using the tuist setup. Trying to ping you both via PM and GH issue. Would you mind have a check on it to follow up? Before it got resolved, I'll use plain SPM xcodeproj integration then using #838.

Preparing a xcframework release of OpenSwiftUI so that everyone can give it a try more easily,

@nathantannar4 @absolute__tk _UIHostingView is also a private API as opposed to NSHostingView and still have some side effect when embedding a SwiftUI View eg. safeArea.

@KyleSwifter @absolute__tk Interesting! What about just using _UIHostingView? I use that when I don’t need a controller.

SwiftUI has a hidden CAHostingLayer API — host your SwiftUI views directly in a CALayer. Currently used internally by UIKit/AppKit and WebKit. Available since iOS 18 / macOS 15. I wrote a guide on how to access it without Apple's internal SDK 👇 gist.github.com/Kyle-Ye/8a7f12…

@NathanBLawrence Those are private API and should not be shipped on prod of course.

@KyleSwifter If you’re just messing around, have fun! But careful with software you ship to others using these, even more than usual.

@absolute__tk See how WebKit uses it in WKMaterialHostingSupport.swift — they host SwiftUI Material views as sublayers without any intermediate view controller. github.com/WebKit/WebKit/…

@absolute__tk It's essential when embedding SwiftUI content inside UIKit/AppKit — you don't want an extra hosting controller sitting inside your view hierarchy. A lightweight CALayer integrates much more naturally.

Also worth noting — OpenSwiftUI provides this API too. If you're using OpenSwiftUI, you can use CAHostingLayer directly via _spi import OpenSwiftUI without the extra swiftinterface workaround. See #831 and #832 for more detail.

@mahyarm8 @oskargroth @sids7 A simpler way to understand this is to just read the OpenSwiftUI source code (or run and debug it lively). I went through this manually a few years ago. #L433-L484" target="_blank" rel="nofollow noopener">github.com/OpenSwiftUIPro… It used to take a lot of effort to piece this together — now AI can walk through 80% of it in minutes.

@oskargroth @sids7 Can it figure out how and when the graph library in swiftui determines when to regenerate view structs and call various stateobject initializers?

Codex's ability to reverse engineer private macOS frameworks is uncanny. Just added an HDR toggle to DisplayBuddy - so many users asked for this!

Inspired by @_julianschiavo's recent work, I started reworking OpenSwiftUI's Xcode Preview support. It's now working on OSUI via a lightweight shim layer + some tweaks around XCODE_RUNNING_FOR_PREVIEWS 🎉

github.com/pointfreeco/sw… Add swift-testing Attachment for snapshot testing. Upstream has not supported it and I fallback to use my fork instead.

@mich_thedev github.com/OpenSwiftUIPro…

@KyleSwifter What could this be? A swift framework?

Finally got basic Text rendering working on OpenSwiftUI 🎉

@_julianschiavo @renegademtl > what are you trying to do? May Preview work for OSUI. > `nm` the private framework Besides that, sometimes we may also need to enable library evolution to align with the private framework's ABI if we want to pass in some data or conform to some protocol from it.

@KyleSwifter @renegademtl Interesting, what are you trying to do? ABI/API issues should be solvable by asking AI/Codex to `nm` the private framework and solve swiftinterface issues

Fun fact: you can just tell Codex to go figure out how to use a private framework you need on macOS. It is insanely good at dumping symbols and making its own `.swiftinterface` for the framework, which you can then link against when compiling.

@_julianschiavo @renegademtl Got it. But in my case, the crash does not seem to be entitlement related permission but some strange framework ABI issue. My current implement is something like the following. Anyway I'll give the new PreviewsPlatform a look when I have time.

@KyleSwifter @renegademtl For previews? Anything through Mach/xpc is blocked (gated) unfortunately, inaccessible without disabling SIP from what I can tell. I feel like there has to be a way to hack this from the sim side (using SIM_CHILD_DYLD_INJECT_LIBRARY) but I haven’t figured it out yet :(

@perezstudioio For other details: you will know it after you clone the repo and run it. 😊

@perezstudioio It is API compatible with SwiftUI. 1. via shaft(skia) backend: a cross platform DSL on all supported platform(Currently only support macOS and has not been merged yet) 2. via CA/RB backend on Darwin: Debug SUI & AG issue with OSUI & OAG source code. Not recommended for prod.

@_julianschiavo @renegademtl Trying to add #Preview support for OpenSwiftUI before and failed due to some strange Xcode preview framework related crash 💥. Would you mind sharing more information on this private framework? 😉

@renegademtl Things that go thru XPC are gated. CoreSim methods aren’t

Yeah. I used to do this manually (craft fake header and swiftinterface to compose xcframework and export as private SDK). LLM can really speed up this process. Here is some skills and scripts I use ⬇️ github.com/OpenSwiftUIPro…