You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is not something that needs immediate attention, but something to keep in mind for the Future.
In Flutter 3.24, Flutter has started the process of moving ios plugins from cocoapods to Swift Package manager.
Given that Unity (plugins) uses cocoapods, I don't know if we can actually make this change. But staying on cocoapods might cause compatibility issues in future Flutter versions.
Today, Flutter uses CocoaPods to manage native iOS or macOS dependencies.
Flutter 3.24 adds early support for Swift Package Manager. This brings several benefits, including:
Access to the Swift package ecosystem. Flutter plugins will be able to leverage the growing ecosystem of Swift packages!
Simplifies Flutter installation. Swift Package Manager is bundled with Xcode. In the future, you won’t need to install Ruby and CocoaPods to use Flutter for Apple’s platforms.
Flutter plugins should support both Swift Package Manager and CocoaPods until further notice.
Swift Package Manager adoption will be gradual. Plugins that don't support CocoaPods won't be usable by projects that haven't migrated to Swift Package Manager yet. Plugins that don't support Swift Package Manager can cause problems for projects that have migrated.
The text was updated successfully, but these errors were encountered:
Thanks for the heads-up. Forgive me but I'm not really familiar with build systems on iOS, so my questions may sound dumb.
What do you mean by 'Unity uses cocoapods'? What is it that makes it a 'cocoapods' thing? (I can't see a Podfile in the exported example project). Or to put it another way, what is it specifically that might mean we are not able to migrate the plugin to support Swift Package Manager? Thanks!
To be honest, I haven't used SPM before and haven't really looked into the details yet.
But I remember some unity plugins requiring pod install to work, and I believe those would have to support SPM too.
Maybe everything simply works after following the upgrade guide. But with the constant pain of innocent changes in Unity/Flutter/Xcode causing issues when combining them, it just wouldn't surprise me that things will break.
Description
This is not something that needs immediate attention, but something to keep in mind for the Future.
In Flutter 3.24, Flutter has started the process of moving ios plugins from cocoapods to Swift Package manager.
Given that Unity (plugins) uses cocoapods, I don't know if we can actually make this change. But staying on cocoapods might cause compatibility issues in future Flutter versions.
From whats new in Flutter 3.24
From how-to-add-swift-package-manager-support-to-an-existing-flutter-plugin
The text was updated successfully, but these errors were encountered: