Please fill out as many of the following questions as possible so we can help you promptly! If you don’t know how to answer or it does not apply, feel free to remove it or leave it blank.
Builder public api key
635b8bec3edf4ae29171530e339c0888
Detailed steps to reproduce the bug
Simply working on code in the code editor, and the “sync from main” button does not work. Tried a number of times over 20 minutes to no avail.
Thanks for the help!
Hi @WanderingWizard,
Thanks for reaching out.
Just to clarify, you’re trying to use Fusion for Swift mobile development. In this case, there won’t (and shouldn’t) be a dev server running for this setup.
Also, please note that Fusion doesn’t currently support SwiftUI. However, you can leverage our Figma to Code feature to help with this. You can find more details in our documentation here:
Figma to Code: Builder CLI
If you have any questions or need further help, feel free to reach out!
Best regards,
Thanks for the reply @Rahulj08
Yes, that’s correct, and I am loving the Figma to Code feature. It would be nice however to have more XCode integration and syncing, instead of copying and pasting. It would also still be nice to have a sync feature as I am using Figma to Code. After copying the code in XCode and editing and tweaking on my own, doing other frontend work, whatever - it’s a hell of a lot easier to sync from GitHub than copy everything back.
Interestingly, you can sort of work around this by attaching a directory containing any simple web files (just an .html file might be all you need - I reused an old project). Then, upon start up, it will spin up the web server for that simple site and you have access to the sync feature (as long as all in one github repo). Putting this here in case anyone else wants to leverage the sync-back when using Figma-to-Code.
Could you clarify more what you mean by it doesn’t support SwiftUI? Will this be a future feature? Thanks!
Thanks for your suggestion!
I wanted to let you know that this has been submitted as a feature request to our product team on your behalf. We truly appreciate your feedback.
And why it doesn’t support Swift Ui because:
Unlike web applications, which can be run inside iframes, SwiftUI apps require their own tooling and environment to run properly. At this time, we only support web applications.
To clarify regarding future support—there are currently no concrete plans or timelines for supporting SwiftUI, but we’ll be sure to share any updates if that changes.
If there’s anything else you’d like to share or if you have further questions, feel free to reach out anytime.
Best regards,