Dependencies of extension (which are rapidly developing as I see) needed to be updated because:
vm_service version range is too restrictive and dependency resolution failed:
Because every version of integration_test from sdk depends on vm_service 14.2.1 and provider_devtools_extension depends on vm_service >=11.9.0 <14.0.0, integration_test from sdk is forbidden.
So, because provider_devtools_extension depends on integration_test from sdk, version solving failed.
devtools_app_shared is outdated a bit and breaks tests. (Link)
...And couple other issues I experienced during updating:
Seems like this deprecation broke somehow backward compatibility and now it's plugin's responsibility to check connection, at least in "development" (with simulated_chrome_environment option)
I will provide my fork with all these updates a little bit later in this issue since it's kinda horrible at the moment and can not be merged in any way. But it could be handy with reproducing next issue, which is most problematic I think.
Because of obligatory update of vm_service to 14.2.1 and up, core logic of instance_providers.dart breaks with a lot of null-related issues (because there is a lot of force-unwraps).
If comment all _parseFields and just use empty lists, there are no exceptions. But no useful info in devtools too, of course, since no fields obtained from VM.
Run example app (provider/packages/provider/example). You will get log like this:
...
A Dart VM Service on Chrome is available at: http://127.0.0.1:53606/jatJWHd2X30=
The Flutter DevTools debugger and profiler on Chrome is available at:
http://127.0.0.1:9101?uri=http://127.0.0.1:53606/jatJWHd2X30=
...
Obtain VM address from this log (in this case – http://127.0.0.1:53606/jatJWHd2X30=)
Run extension example with --dart-define=use_simulated_environment=true as described here
Connect to Dart VM from step 2 in upper-right corner (Dart VM service connection)
Describe the bug Hi!
I was interested in proceeding work on #868 to improve DevTools extension.
Here is my dev environment:
Dependencies of extension (which are rapidly developing as I see) needed to be updated because:
devtools_app_sharedis outdated a bit and breaks tests. (Link)...And couple other issues I experienced during updating:
simulated_chrome_environmentoption)I will provide my fork with all these updates a little bit later in this issue since it's kinda horrible at the moment and can not be merged in any way. But it could be handy with reproducing next issue, which is most problematic I think.
Because of obligatory update of
vm_serviceto14.2.1and up, core logic of instance_providers.dart breaks with a lot of null-related issues (because there is a lot of force-unwraps). If comment all_parseFieldsand just use empty lists, there are no exceptions. But no useful info in devtools too, of course, since no fields obtained from VM.To Reproduce
null-exceptions, Linkprovider/packages/provider/example). You will get log like this:Obtain VM address from this log (in this case –
http://127.0.0.1:53606/jatJWHd2X30=)--dart-define=use_simulated_environment=trueas described hereDart VM service connection)LogstabExpected behavior
I was expecting instance_providers.dart to work with updated
vm_serviceand updated VM service protocol