juliansteenbakker / mobile_scanner

A universal scanner for Flutter based on MLKit. Uses CameraX on Android and AVFoundation on iOS.
BSD 3-Clause "New" or "Revised" License
818 stars 476 forks source link

GoogleDataTransport version conflict with firebase_crashlytics #1165

Open IncM opened 2 weeks ago

IncM commented 2 weeks ago

After update firebase_* packages ios build was broken.

Pod error log ```log [!] CocoaPods could not find compatible versions for pod "GoogleDataTransport": In Podfile: firebase_crashlytics (from '.symlinks/plugins/firebase_crashlytics/ios') was resolved to 4.1.0, which depends on Firebase/Crashlytics (= 11.0.0) was resolved to 11.0.0, which depends on FirebaseCrashlytics (~> 11.0.0) was resolved to 11.0.0, which depends on GoogleDataTransport (~> 10.0) mobile_scanner (from '.symlinks/plugins/mobile_scanner/ios') was resolved to 5.2.1, which depends on GoogleMLKit/BarcodeScanning (~> 6.0.0) was resolved to 6.0.0, which depends on MLKitBarcodeScanning (~> 5.0.0) was resolved to 5.0.0, which depends on MLKitCommon (~> 11.0) was resolved to 11.0.0, which depends on GoogleDataTransport (< 10.0, >= 9.4.1) ```
navaronbracke commented 2 weeks ago

We already depend on the latest version of GoogleMLKit/BarcodeScanning. You will have to raise an issue on their issue tracker to request an update.

See https://developers.google.com/ml-kit/release-notes#ios-api-latest-versions and https://github.com/juliansteenbakker/mobile_scanner/blob/master/ios/mobile_scanner.podspec#L18C17-L18C44

For context, we had a similar issue here https://github.com/juliansteenbakker/mobile_scanner/issues/335#issuecomment-1286346905 and that user also raised an issue on their issue tracker. Until that is addressed, I cannot update our dependency to fix this, unfortunately.

garrettApproachableGeek commented 2 weeks ago

I have opened an issue with GoogleMLKit for this issue: https://issuetracker.google.com/issues/362452861

navaronbracke commented 2 weeks ago

I have opened an issue with GoogleMLKit for this issue: https://issuetracker.google.com/issues/362452861

Thanks!

Ben1980 commented 2 weeks ago

Again priority P4 on googles side... :-(

krupikivan commented 2 weeks ago

Same conflict with firebase_messaging

SlavisDEV commented 2 weeks ago

+1

hnvn commented 2 weeks ago

+1

IncM commented 2 weeks ago

For a temporary fix I set old versions firebase_* packages. I use versions before fix

bump all iOS deployment targets to iOS 13 ahead of Firebase iOS SDK v11 breaking change (#12872). (de0cea2c)

For example

  firebase_core: ^2.32.0
  firebase_crashlytics: ^3.5.7
  firebase_messaging: ^14.9.4
  firebase_performance: ^0.9.4+7
HappyMakadiyaS commented 2 weeks ago

For now this works for me... Override Firebase SDK Version in podfile

$FirebaseSDKVersion = '10.29.0'

Mo0Khaled commented 2 weeks ago

Any updates?

navaronbracke commented 2 weeks ago

@Mo0Khaled I cannot provide any updates, since MLKit is not developed by us, but by Google.

Ben1980 commented 1 week ago

63 requests and still just P4 on googles side 🤦‍♂️🤨

DaigoWakabayashi commented 4 days ago

+1 on https://github.com/juliansteenbakker/mobile_scanner/issues/1165#issuecomment-2313227415

cyrilcolinet commented 3 days ago

They’re too busy trying to kill Flutter themselves by creating new cross-platform "frameworks" instead of updating the current libraries to keep Flutter alive… 😢

PS: It’s a joke, and I’m still waiting for that update too.

navaronbracke commented 3 days ago

The Flutter team is not the same team as the MLKit team, though. But yes, the fact that it is closed source also prevents us from landing fixes ourselves. I'm actively exploring dropping support for MLKit on iOS (in favor of Apple's own Vision API). That should eliminate dependency issues on iOS entirely.