Unable to fuse DEBUG

Bug Reports
1

Fuse version 0.37.0 (build 12978)
Windows 10

Following statement is not starting debugger

fuse preview . -DDEBUG_V8

file
file813×266

2

Hi!

That doesn’t start a debugger. You need to attach an external debugger, e.g. Visual Studio Code.

3

I tried following the video.

I don’t get the message that debugger is started at 5858. [video 2:47]
Also I tried “Attach to Process” where it gave following error.

file
tEJT5KkOeaMW-image-1494718682789.png1005×68

Following is my launch.json file

file
OJe4OGBnPrit-image-1494718831479.png890×460

Also telnet shows port is closed

file
cx4YKjho2Oqc-image-1494718964476.png754×21

Am I missing anything?

4

Are others able to debug after upgrading to 0.37 ?

5

There seems to be a [known] issue that affects the capability of preview to open up to debugger. You’ll get notified when there are some news on this.

6

Glad to hear this is a known bug. Was going crazy following along with the video, trying to get Preview to debug.

7

More problems: since debugging with Preview is apparently broken, I thought I’d try debugging my actual device (Pixel XL).

Following the video, I forward port 5858 using adb. I then ran

uno build --target=android --run -DDEBUG_V8

The app started on my phone, and now appeared to correctly halt at my javascript “debugger” line.

However, back in Visual Studio Code, when I click “Attach”, I get an error:
Cannot connect to runtime process (reason: read ECONNRESET).

I can see it connect in my terminal: after clicking Attach it says “Connection to a debugger agent established” for a brief second, but then the ECONNRESET error appears in VS Code and the terminal goes back to “Waiting for a debugger agent to connect on port 5858…”.

My launch.json file looks like this:

{
    "version": "0.2.0",
    "configurations": [
        {
            "type": "node",
            "request": "attach",
            "name": "Attach",
            "port": 5858,
        },
        {
            "name": "Launch",
            "type": "node",
            "request": "launch",
            "program": "${file}"
        }
    ]
}
8

Hey robosaurus,

I’m sorry to hear that you’re having trouble getting the debugger to work. It seems that recent versions of Visual Studio Code are incompatible with the Android debugger. There are two things you could try that work for me at least:

  • Use Visual Studio Code 1.9 (January 2017)
  • Build for .NET with Uno (uno build --target=dotnet --run -DDEBUG_V8)

I’ve created another internal issue to look into the problem with debugging on Android with the latest VSC.

9

Olle Fredriksson wrote:

“Build for .NET with Uno (uno build --target=dotnet --run -DDEBUG_V8)”

I can confirm that debugging works on .NET target using VS Code 1.12.2.

I didn’t even know Fuse could compile to .NET! Thought it was only Android & iOS. Very cool.

10

Hey again,

The Fuse 1.0.1 pre-release, available at https://www.fusetools.com/downloads/channel/qa, now allows you to pass defines to the preview command again, so it should now work to start Fuse with fuse preview . -DDEBUG_V8. We still haven’t found out why the Android debugging doesn’t work with later versions of VSC, but at least there are workarounds.

Thanks for your report!