Unhandled error detected in the injected client.js script.

[emmanuelcohenlaroque]

Since upgrading, I run into the following issue when debugging on Chrome device:

Unhandled error detected in the injected client.js script.

You can disable this script in webdev by passing --no-injected-client if it
is preventing your app from loading, but note that this will also prevent
all debugging and hot reload/restart functionality from working.

The original error is below, please file an issue at
https://github.com/dart-lang/webdev/issues/new and attach this output:

NoSuchMethodError: method not found: 'get$digestsPath' (J.getInterceptor$x(...).get$digestsPath is not a function)
TypeError: J.getInterceptor$x(...).get$digestsPath is not a function
    at Object.get$digestsPath$x (http://0.0.0.0:8080/dwds/src/injected/client.js:3507:43)
    at http://0.0.0.0:8080/dwds/src/injected/client.js:22732:60
    at _wrapJsFunctionForAsync_closure.$protected (http://0.0.0.0:8080/dwds/src/injected/client.js:3802:15)
    at _wrapJsFunctionForAsync_closure.call$2 (http://0.0.0.0:8080/dwds/src/injected/client.js:10996:12)
    at Object._asyncStartSync (http://0.0.0.0:8080/dwds/src/injected/client.js:3766:20)
    at RequireRestarter._getDigests$0 (http://0.0.0.0:8080/dwds/src/injected/client.js:22744:16)
    at http://0.0.0.0:8080/dwds/src/injected/client.js:22759:48
    at _wrapJsFunctionForAsync_closure.$protected (http://0.0.0.0:8080/dwds/src/injected/client.js:3802:15)
    at _wrapJsFunctionForAsync_closure.call$2 (http://0.0.0.0:8080/dwds/src/injected/client.js:10996:12)
    at Object._asyncStartSync (http://0.0.0.0:8080/dwds/src/injected/client.js:3766:20)
    at RequireRestarter._initialize$0 (http://0.0.0.0:8080/dwds/src/injected/client.js:22767:16)
    at http://0.0.0.0:8080/dwds/src/injected/client.js:8572:45
    at _wrapJsFunctionForAsync_closure.$protected (http://0.0.0.0:8080/dwds/src/injected/client.js:3802:15)
    at _wrapJsFunctionForAsync_closure.call$2 (http://0.0.0.0:8080/dwds/src/injected/client.js:10996:12)
    at Object._asyncStartSync (http://0.0.0.0:8080/dwds/src/injected/client.js:3766:20)
    at Object.RequireRestarter_create (http://0.0.0.0:8080/dwds/src/injected/client.js:8584:16)
    at http://0.0.0.0:8080/dwds/src/injected/client.js:22319:38
    at _wrapJsFunctionForAsync_closure.$protected (http://0.0.0.0:8080/dwds/src/injected/client.js:3802:15)
    at _wrapJsFunctionForAsync_closure.call$2 (http://0.0.0.0:8080/dwds/src/injected/client.js:10996:12)
    at _awaitOnObject_closure.call$1 (http://0.0.0.0:8080/dwds/src/injected/client.js:10982:32)
    at StaticClosure._rootRunUnary [as call$2$5] (http://0.0.0.0:8080/dwds/src/injected/client.js:4130:18)
    at _CustomZone.runUnary$2$2 (http://0.0.0.0:8080/dwds/src/injected/client.js:12301:39)
    at _Future__propagateToListeners_handleValueCallback.call$0 (http://0.0.0.0:8080/dwds/src/injected/client.js:11362:51)
    at Object._Future__propagateToListeners (http://0.0.0.0:8080/dwds/src/injected/client.js:3914:93)
    at _Future._complete$1 (http://0.0.0.0:8080/dwds/src/injected/client.js:11186:11)
    at Object._cancelAndValue (http://0.0.0.0:8080/dwds/src/injected/client.js:4069:16)
    at Stream_first_closure0.call$1 (http://0.0.0.0:8080/dwds/src/injected/client.js:11454:9)
    at _EventStreamSubscription_onData_closure.call$1 (http://0.0.0.0:8080/dwds/src/injected/client.js:17309:30)
    at StaticClosure._rootRunUnary [as call$2$5] (http://0.0.0.0:8080/dwds/src/injected/client.js:4136:16)
    at _CustomZone.runUnary$2$2 (http://0.0.0.0:8080/dwds/src/injected/client.js:12301:39)
    at _CustomZone.runUnaryGuarded$1$2 (http://0.0.0.0:8080/dwds/src/injected/client.js:12233:14)
    at _CustomZone_bindUnaryCallbackGuarded_closure.call$1 (http://0.0.0.0:8080/dwds/src/injected/client.js:12436:25)
    at invokeClosure (http://0.0.0.0:8080/dwds/src/injected/client.js:1204:26)
    at EventSource.<anonymous> (http://0.0.0.0:8080/dwds/src/injected/client.js:1223:18)

 • Flutter version 1.22.0 at /home/ecl/localdevs/flutter
    • Framework revision 7c6f9dd239 (8 weeks ago), 2020-08-09 10:31:03 -0400
    • Engine revision 6d86e67f04
    • Dart version 2.10.0 (build 2.10.0-4.0.dev 0341576448)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at /home/ecl/Android/Sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: /opt/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Android Studio (version 4.0)
    • Android Studio at /opt/android-studio
    • Flutter plugin version 48.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.49.3)
    • VS Code at /usr/share/code
    • Flutter extension version 3.15.0

[✓] Connected device (2 available)
    • Web Server (web) • web-server • web-javascript • Flutter Tools
    • Chrome (web)     • chrome     • web-javascript • Google Chrome 86.0.4240.75

• No issues found!

[grouma]

@ecl66 since upgrading what exactly?

cc @jonahwilliams

[grouma]

@Markzipan I believe you resolved this issue in the SDK. Does the user simply need to upgrade?

[Markzipan]

The previous fix should've been cherry-picked into Dart 2.9.3. It's possible that a recent Chrome update changed some of our API expectations, as this kind of error implicates just a handful of special JS classes. @ecl66 and @Tobi696, do you both have an app or simple repro you can provide?

[Tobi696]

It seems to be a problem with Chrome's API as it works in Microsoft Edge.

[Tobi696]

@Markzipan I cannot give you access to my real project, but I just created a new project with flutter create and tested debugging on chrome and I get the same error. You can view the generated code here: Tobi696/chrome_api_test

[grouma]

@sigmundch is this related to dart-lang/sdk#43193

[marcckku]

It seems to be a problem with Chrome's API as it works in Microsoft Edge.
Tobi696 It is true!! it works both with Microsoft Edge and with Opera .. but with Chrome nothing !!

[sigmundch]

Yes, I do think this is highly related to the other issue.

MemoryInfo caused trouble early on (during load time) and when we tested things out back then in Chrome 87 canary, we didn't see other issues. It's likely missed other similar scenarios. It's possible that they come up later when code in the app start running, which would explain why we missed it.

We also recently saw an issue with navigator.getGamepads which involves a similar underlying change from the browser: dart-lang/sdk#43750

@Markzipan is working on fixing this.

[Markzipan]

I can repro this issue on revision 7c6f9dd239 but not at head of master. I can confirm that this issue is due to the aforementioned MemoryInfo problem, so can you try upgrading flutter and rerunning @ecl66? This is odd - I thought that bug was patched earlier, but the compiled SDK doesn't appear to have the patch.