feat(plugin): add option to use a Xcode project for iOS#9843
Conversation
There was a problem hiding this comment.
Do we need to template xcuserdata?
There was a problem hiding this comment.
I'm not sure @pewsheen I only generated a new Xcode Swift static library project and moved here :D
There was a problem hiding this comment.
I think this can probably be removed - let me double check
There was a problem hiding this comment.
deleted, nice catch!
There was a problem hiding this comment.
I think it's safe to remove the xcuserdata folder. It'll regenerate a new one next time we build or open it with Xcode. Another reason is it's based on the user name on Mac I guess, so it might recreate it anyway.
There was a problem hiding this comment.
i did delete it but i just forgot to actually comment on this review
There was a problem hiding this comment.
Seems forgot to delete this one 👀
tooling/cli/templates/plugin/ios-xcode/tauri-plugin-{{ plugin_name }}.xcodeproj/project.xcworkspace/xcuserdata/lucas.xcuserdatad/UserInterfaceState.xcuserstate
|
Everything looks good! I don't have the write access to approve the review, maybe @amrbashir can help approve it again 😅 |
3 participants
Currently plugin authors are forced to use SwiftPM for their iOS library. This PR adds support to a plain Xcode project (also using Swift under the hood) that is compiled using
xcodebuild. This solves some SwiftPM limitations e.g. not being able to use dependencies that relies on XCFrameworks and other quirks such as firebase, GoogleSignIn-iOS, etc.