-
Notifications
You must be signed in to change notification settings - Fork 361
Closed as duplicate of#6848
Closed as duplicate of#6848
Copy link
Description
Summary
When devtools is attached to a Flutter application running in a custom embedder, limited functionality is available.
Steps to reproduce
- Launch the demo GLFW embedder. In the console, the VM URL will be output, for example
The Dart VM service is listening on http://127.0.0.1:38217/ajHHm0ZNdFs=/ - Following the documentation in Using-the-Dart-Development-Service-(DDS)-and-Flutter-DevTools-with-a-custom-Flutter-Engine-Embedding, run the dart development service as follows, passing the above URI:
$ dart development-service --serve-devtools --vm-service-uri=http://127.0.0.1:38217/ajHHm0ZNdFs=/
{"state":"started","ddsUri":"http://127.0.0.1:38961/p_UkyRqO53E=/","devToolsUri":"http://127.0.0.1:38961/p_UkyRqO53E=/devtools/?uri=ws://127.0.0.1:38961/p_UkyRqO53E=/ws","dtd":{"uri":"ws://127.0.0.1:36099/vkodRgwXROU="}}
- Open the
devToolsUriin a browser
Expected result
(Image from same application run in the Linux Desktop embedder)
Devtools launches in a browser and is fully usable
Actual result
Devtools launches but displayed information is incorrect and most functionality is not available.
- Flutter Inspector and Debugger tabs are not present.
Flutter DevTools tab:
- Connected app type is incorrect. Reports Flutter native (profile build), is actually a debug build
Performance tab:
Non functional - just a spinning wheel (an error ParallelWaitError: Exception: No Flutter Views to query: {type: FlutterViewList, views: []} appears in the web developer console log`
See also
Metadata
Metadata
Assignees
Labels
No labels