Closed LeoBound closed 1 year ago
Are you using docker? If yes, does this issue help you?
Unfortunately not - I'm running it on some embedded hardware where I added meta-flutter to the yocto build process.
Sorry, I can't debug any further as I don't know your environment. Are you using flutter-elinux? How did you create /path/to/bundle
?
The bundle was created with flutter build bundle
with the standard flutter tool.
After these errors the application does run as expected - there is just no way to debug it.
Could you let me know what details you need to know about the environment? It's a custom board with an iMX6.
Thanks
Are you trying to attach your flutter app from your host PC or just launching it on arm64 devices?
After these errors the application does run as expected - there is just no way to debug it.
I think that the settings related to the network/port of the device you are using are affecting the error. But no one can advise without repro steps, commands, and whole logs.
Do you know where could I find more verbose logs?
The logs in my first post are the output of flutter-client -f -b /path/to/bundle
. Does flutter-client or the flutter engine output any other logs, I couldn't find any in /var/logs.
My steps were:
XDG_RUNTIME_DIR=/tmp/-runtime-dir flutter-client -f -b /tmp/${appName}
I'm using dropbear for SSH access instead of OpenSSH, could this be why?
Add the device with flutter custom-devices with the flutter SDK (3.0.5)
Why are you using the official flutter SDK? Could you try using flutter-elinux once?
Closing as no update for a while.
Hi,
I've built the debug wayland recipes using meta-flutter and can run flutter apps in debug mode. Whenever I start a flutter app (by using
flutter-client -b /path/to/bundle
) I get the following errorand subsequently I am unable to attach the debugger. This also fails when using flutter custom-devices on a host machine to try and debug (same error).
Why would this be, is there a way to see a more verbose log?
Thanks