Navaron Bracke

@pmathew92 It turns out that the original guidance for mocking JS interop types is a bit outdated. I managed to fix a first test case, by taking the existing interop...

I am referring to the web tests when running with JS interop extension types, not any of the native tests (iOS or MacOS).

@pmathew92 I cannot seem to update the mocks locally? None of the existing mocks actually mock _extension types_ for the web tests, so I think that this just doesn't work...

@pmathew92 Did you run the web tests with `flutter test test/web/auth0_flutter_web_test.dart --platform=chrome` when implementing WASM ? Because that doesn't work without updated mocks.

I did manage to fix the mocks locally, seems to be an issue with build_runner / mockito. Had to do it manually though. I still have a different issue now,...

Tests passed locally now. 

@pmathew92 PTAL. I updated the JS interop to call dartify/jsify directly and moved the polyfill for JSArray to the correct file. As for the `appState` argument, I think that that...

Any ideas why the code coverage check is failing? The indirect diff seems to be unrelated to this PR?

Thanks for getting this landed!

The black screen with (i) icon is the default error builder for the `MobileScanner` widget. What error details (message + stacktrace) do you get in the `MobileScannerException` ? (you can...