flutter_qr_mobile_vision
flutter_qr_mobile_vision copied to clipboard
Scanning is not working on Android while upgrading to 4.0.1
When I upgraded to latest 4.0.1, scanning stops working on Android device and on iOS device its working fine. Scanning was working perfectly when I was using 3.0.1 version.
Attached log file
hmm interesting, thanks for the report. I might not have time to look into this until the weekend, so until then it might be worth staying on 3.0.0.
I hacked a quick fix for this issue that can be seen here.
Just a case of moving where we close the image. There's a lot of image/frame 'close' handing logic in that class. Not sure whether all of it is now necessary, but left it alone and walked backwards slowly 😉
I have the same issue, but only on devices running the Android 13. Like my Pixel 6 Pro.
Sorry, I've been completely swamped. No promises but I'm going to try to look into this soon. And yeah the image/frame logic is somewhat atrocious haha
same
Same here
I have the same issue :<
Same issue
Same issue
Same issue
any update on this issue?
I hacked a quick fix for this issue that can be seen here.
Just a case of moving where we close the image. There's a lot of image/frame 'close' handing logic in that class. Not sure whether all of it is now necessary, but left it alone and walked backwards slowly 😉
@SoftWyer Not sure of the implications but for my specific use case (Xiaomi Redmi 8 and 9) it seems to work. Thank you!
I also had to add this to [email protected]
build.gradle
file to be able to build with your patch:
android {
// ...
compileOptions {
sourceCompatibility JavaVersion.VERSION_1_8
targetCompatibility JavaVersion.VERSION_1_8
}
// ...
}
otherwise I would get an error:
lambda expressions not supported at this language level
We have the same issue on v4.0.1. I'm currently using the fork below as a workaround, but this is far from ideal. I hope this issue can be resolved in this library :)
qr_mobile_vision:
git:
url: https://github.com/ADDInformatique/flutter_qr_mobile_vision
ref: master
Sorry for the ... long... delay on this. I'm putting on a version today which should fix that issue.
I can confirm this issue has been resolved in v4.1.0 👍
Thank you @rmtmckenzie!