Request for Swift Package Manager support

[yujinqiu]

[stepan-votava]

Is there any news with SPM support? We have problems on M1 macs

[kristohear]

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]

We need SPM support !

[AngryDuckFTW]

+1 for SPM

[kristohear]

@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.

[yujinqiu]

1 year has passed and M1 Pro/Max have released, but SPM is still on the way. :-(

[fukemy]

does it support now?>>

[bcdj]

Due to necessary internal infra is still being developed, we cannot add the SPM support yet.

[alexis-ag]

+1

[bcdj]

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?

[Frankatvend]

+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.

[codeslaw]

@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

[garriguv]

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.

[lee-jongwoo]

@bcdj
Here's some information I hope will help:

1. App currently in development; No user base available
2. The CocoaPods version of ML Kit is available. pod install works, but the compiler throws a bunch of errors when building for simulator. I'll attach them below.
3. 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: