Open thomaaam opened 4 years ago
Issue-Label Bot is automatically applying the label bug
to this issue, with a confidence of 0.69. Please mark this comment with :thumbsup: or :thumbsdown: to give our bot feedback!
Links: app homepage, dashboard and code for this bot.
Hey.
Can you just try commenting out use_frameworks!
line from ios/Podfile
under your Flutter project?
And run once.
It appears to work as pod install
succeeds, but then flutter build ios
fails due to this error:
fatal error: 'qr_code_scanner/qr_code_scanner-Swift.h' file not found
It appears this pod is installed successfully with use_frameworks!
.
Also most of my pods are downgraded again as a result of commenting out use_frameworks!
is this issue fixed ? can we close this @thomaaam @m-zaink ?
Let me look into it more closely then. @thomaaam
Thanks for bringing out this issue.
@nateshmbhat do not close this issue yet. I'll pick up by the weekend and fix it.
Did you learn anything during the weekend, @m-zaink? 😄 Just tell me if you need something more from me. We are very eager to get this out on iOS, as we currently only support it on Android.
I am able to get this working on iOS now with this pubspec.yaml
configuration:
card_scanner:
git:
url: https://github.com/DeadBryam/card-scanner-flutter
ref: fix-static-framework
Thanks to this fix: #17
PS: Though I tested on an iPhone SE (1st generation), so the layout does not look perfect, but at least it works! This might even be a cosmetic issue that applies to the latest release as well.
When trying to build for production I yet again faced some issues. Thus what I said over here ☝️ does not do the trick after all 😞
Undefined symbols for architecture armv7:
"_OBJC_CLASS_$_MLKTextLine", referenced from:
objc-class-ref in card_scanner(ScanProcessor.o)
"_OBJC_CLASS_$_MLKTextBlock", referenced from:
objc-class-ref in card_scanner(ScanProcessor.o)
"_OBJC_CLASS_$_MLKTextRecognizer", referenced from:
objc-class-ref in card_scanner(CameraViewController.o)
"_OBJC_CLASS_$_MLKVisionImage", referenced from:
objc-class-ref in card_scanner(CameraViewController.o)
The reason is that MLKit does not support 32bit architectures anymore See here: https://developers.google.com/ml-kit/migration/ios
ML Kit does not support 32-bit architectures (i386 and armv7). ML Kit does support 64-bit architectures (x86_64 and arm64).
I am able to get this working on iOS now with this
pubspec.yaml
configuration:card_scanner: git: url: https://github.com/DeadBryam/card-scanner-flutter ref: fix-static-framework
Thanks to this fix: #17
PS: Though I tested on an iPhone SE (1st generation), so the layout does not look perfect, but at least it works! This might even be a cosmetic issue that applies to the latest release as well.
I have used this configuration on my iPhone XS and the layout could be better. And no recognition at all. I can only see the camera but nothing is recognized
We are also using version - ^0.2.0+3 and facing same issue, is there any solution for this ? If so, please let us know. [!] The 'Pods-Runner' target has transitive dependencies that include statically linked binaries: (GoogleUtilitiesComponents)
Hey, your package works beautifully on Android. However on iOS I am still unsuccessful to build with the latest version. Note that when I build with version
^0.0.4
it builds successfully.Here's what happens when I try to build
^0.1.0
:[!] The 'Pods-Runner' target has transitive dependencies that include statically linked binaries: (GoogleDataTransport, GoogleDataTransportCCTSupport, and GoogleUtilitiesComponents)
I did google this issue and found this trick:
However further down the road I then ran into these issues:
What is curious here is that when I use
^0.1.0
over^0.0.4
most the Firebase and Google pods are downgraded. Therefore I wonder if you use outdated Firebase/Google pods for version^0.1.0
?This is some changes to my
Podfile.lock
after upgrading to^0.1.0
:Note how most or all pods are downgraded?
Not sure how to proceed from this, but I still cannot use
card-scanner-flutter
for iOS until there is a resolution to this issue. It's the only viable card scanner for Flutter as far as I can find, so I hope you have some answers!