-
Notifications
You must be signed in to change notification settings - Fork 44
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to configure DDS and DevTools for special target device #251
Comments
Please ensure that you have set forwardPort and disable all proxy settings. See https://github.com/sony/flutter-elinux/wiki/Remote-target-devices#flutter_custom_devicesjson-example |
I have no any proxy configured now.
I connect with my target board over Ethernet Port
Look at my logs:
PortForward already corrected. |
Regarding to your trial on Rpi, i just confused about why did your target board already installed "Dart DevTools" and it will be activated automatically while executing flutter app. or after It is being executed on Host??? |
Practice done already, with below notes: I need to attach "--debug-url" manually after application started Target Device:
Host PC:
Ex: in my case is
Practice on Flutter-eLinux release 3.9.13. Thank you! @HidenoriMatsubayashi I am not sure why did my environment haven't started Devtools automatically as your practiced |
You should use I'm not sure what your issue is here... |
I've confirmed that flutter-elinux version: 3.19.4
|
Ya i mean is we able to connect for debugging on target already after we attach debugger manuallly
I just concerned is why did it is not started automatically on our environment. |
Please try the followings to break down the issue.
|
I'll close this issue as there is no additional update/comment. |
Re-opening. |
Pasting what i had in the other issue Looked through a bit of the other issues but haven't been able to resolve what I am seeing.
The discovery uri never shows up in the regular log. But if i run with -v
Going to that url I get this.
Other info, I am cross building from x64 to arm64 using custom sdk and yocto. |
I used that url from the verbose log and did the same process with running the
|
Typo: {$devicePort} |
Good catch, but that is also how i have it in my custom devices. Working between different devices |
When attempting to connect to the VM service URI output by the Flutter engine in the context of a custom embedder, users may encounter the following error:
This VM does not have a registered Dart Development Service (DDS) instance and is not currently serving Dart DevTools.
Platform:
Flutter elinux release 3.13.0
Flutter target devices:
Step to Reproduce:
Result on Web-browser: debug and profile modes are the same result
The text was updated successfully, but these errors were encountered: