peukerjonathan

Which release are you using? If you are using a "-play-services" release it is possible that the device you are attempting to scan on did not properly download the dependency...

> ``` > pod repo update > pod update GTMSessionFetcher/Core > ``` > > solved it for me. However, the problem for me was firebase_auth not firebase_storage. If this does...

I am getting the same issue on v1.1.1 and 2.0.0 - but only on iOS as far as I can tell. On Android everything seems to be fine. Tried to...

I managed to build with 3.0.0-beta.1 (flutter upgrade did the trick) The error is now reverted. Instead of getting `flutter: MobileScanner: Called start() while already started!` (along with the described...

Hello there! Any thoughts on this? I would be more than happy to help to resolve this issue. Unfortunately at the moment I have no idea how to do so....

As far as I found out now the message `flutter: MobileScanner: Called stop() while already stopped!` originates from the file `mobile_scanner-3.0.0-beta.1/ios/Classes/SwiftMobileScannerPlugin.swift` This messages is triggered when the `stop` method is...

That sounds amazing, thanks for the feedback!

I also noticed this "issue". A possible approach for me is to buffer the scanned result. Only when I receive the same result 5 times in a row I pass...

Unfortunately I have to disagree. :( I just updated to the new version (3.0.0-beta.2) and tested on my app using an iPhone 13. The problem unfortunately was still there. However...

I also ran in this problem with TAN method 923 on an account from "Sparkasse Pforzheim Calw" (PZHSDE66XXX) But there is something I noticed, maybe this helps in resolving this...