mlkit
mlkit copied to clipboard
googlesamples
Request for Swift Package Manager support
While Firebase is getting closer and closer to have full SPM support, is there any estimates on this one? It's a huge blocker for M1 macbooks.
@nilsnilsnils @AngryDuckFTW there is a topic here https://issuetracker.google.com/issues/174418229 , about MLKit SPM support, I think this repository is not checked as actively as this issuetracker topic there.
1 year has passed and M1 Pro/Max have released, but SPM is still on the way. :-(
Due to necessary internal infra is still being developed, we cannot add the SPM support yet.
Hi everyone (@yujinqiu @stepan-votava @kristohear @nilsnilsnils @AngryDuckFTW @fukemy @alexis-ag): To help us gauge the importance of supporting Swift Package Manager, could you share the size of your user base? And if you can also provide an App Store link to your app, that would be helpful too. In addition, are you able to use Cocoapods version of ML Kit in place of Swift Package Manager when building your app? Will the lack of Swift Package Manager support block your development entirely?
+1. We intentionally moved away from Cocoapods to SPM two years ago in our project, I'm sad to hear that this great lib doesn't support SPM while looking for candidates.
@bcdj SPM is the currently recommended, and future-dominant method of managing dependencies. It's first-party and relatively mature. It seems inevitable that MLKit will need to migrate, and by waiting you discourage adoption in new projects (mixing dep. management is messy and occasionally quite frustrating)
So non-blocking, but high-misery.
Current userbase: 50-100k mau, SPM app https://greg.app/ Previous userbase: Tinder, 50-100m mau, recently (2021) migrated SPM app
Not supporting SPM and M1 machines is preventing us from adopting this package in our app. We'll likely work with other partners to provide the capability we're missing.
Obviously this is free so I understand if it's not a priority, but we'd love to use it.
The usage would be for internal, non-public facing apps. So low userbase, but business critical.
@bcdj Here's some information I hope will help:
- App currently in development; No user base available
- The CocoaPods version of ML Kit is available.
pod installworks, but the compiler throws a bunch of errors when building for simulator. I'll attach them below. - Building works when building for a real device, so it doesn't block development entirely. But this is still a major flaw since everything needs to be run on the device. Xcode features including Live Preview do not work.
Apple Silicon is the future of all macs. Many developers are migrating to M1 macs thanks to their performance and power efficiency. Now that the transition to Apple Silicon is almost done, ML Kit will have to migrate to SPM soon.
These are the errors:
Can you please tell me if you have a timeline or roadmap to release xcframework for this great library? Our team is waiting for you. If you need help, then let me know.
I have successfully created MLKit's XCFramework using CocoaPods build artifacts and resolved the dependencies. https://github.com/d-date/google-mlkit-swiftpm
However, I am unable to run it on iOS devices due to Dynamic Framework or code signing issues. If anyone has a solution, please send me a pull request.
For MLKit team, please distribute your frameworks in ARM Mac (M1/M2) first to include arm64 iphonesimulator as Firebase team (@paulb777) done.
However, I am unable to run it on iOS devices due to Dynamic Framework or code signing issues. If anyone has a solution, please send me a pull request.
Resolved! Now you can use MLKit in SwiftPM!
Unfortunately, I found some missing internal APIs. If you know about it, please let me know where is located. https://github.com/d-date/google-mlkit-swiftpm/issues/16
Unfortunately, I found some missing internal APIs. If you know about it, please let me know where is located. d-date/google-mlkit-swiftpm#16
Resolved: https://github.com/d-date/google-mlkit-swiftpm/issues/16#issuecomment-1274210156
Unfortunately this won't be planned in the future release.
So google plan is.... just not planning on supporting devs with a modern arm macbook... sounds like a good plan. What a joke.
I'm unable to move Firebase to SPM because Google's MLKit doesn't support it. Here's an article that describes how to move to Apple's ML libraries instead to fix the problem:
https://medium.com/@fredadda/ios-strategies-to-transition-to-swift-package-manager-7d954c8abd36
If this doesn't get resolved soon, I will also drop Google's MLKit.
Cocoapods is deprecated, so if MLKit is to continue on iOS, it really needs to support SPM. SPM now has everything you need, including full ObjC support, binary support, resource support etc. I recently converted my legacy objc framework, and it all worked out.
