Open tolgraven opened 5 months ago
Hello.
Hm, it looks like it wants to start the camera but as it gets transferred to login screen something hangs as the camera code has to run on main thread and as far as I know camera feed gets automatically stopped if preview is in the background. I haven't directly tested this scenario. As the whole initialisation happens quite fast, especially on iOS, I would recommend that you set CameraEnabled to false as default and only set it to true when the login page gets closed.
CameraEnabled is false. I meant that the scanner view is loaded/in the component tree on a page straight on boot, not that it's running!
I suppose we'd have to move it out of XAML and throw it in manually later on instead? Or do you have any other ideas for how to solve it at lib level?
We're running a version of 1.2.4 with some local bugfixes. Seeing all the work you've done since then we wanted to try going back to using the Nuget, 1.5.0, but having some issues.
When trying to run on a real iPhone, so as to be able to actually test it, the debugger never manages to connect, app is killed before then by some watchdog timeout (as revealed not in console but crashlog). Same when running without a debugger attached. BarcodeScanning.Native is the definite culprit.
Relevant would be that we have a (not yet running) scanner on the very first page that appears, our default shell tab. The login screen and splash animation appear on top of this, trading some startup slowness for quicker response later.
Why would the initialization be that much slower on the newer version?
Thanks again for the awesome lib!