Stepping into Dart SDK sources in Flutter results in sources downloaded from the VM instead of used from disk #5164
Description
Some integration tests are failing because when we step into SDK sources, we don't get back a path for the stack frames:
This happens with current master (21d996929bb96facd791d650d1ad35e6024d44ae) but only for flutter-tester ("args": [ "-d", "flutter-tester" ]). Using the Windows device things are fine:
This is possibly a Flutter issue, but needs some more investigation to see what the difference in traffic is over the VM Service.