pd4d10/debugtron

Debug in-production Electron based app

Hi there 👋

debugtron's Issues

is there a way to test my own .swf loader on debugtron?

it works for artix launcher .swf loader, but when I open my own private server it dosen't work is there a way I can add the loader to the debugtron so I can debug it ?

I need the installation package for win-x86

I need to debug on 32-bit windows, Is there an x86 installation package?

how do you build this package?

i am trying to build from the git as i noticed the releases are quite old. after cloning i used pnpm install as i noticed the pnpm lock file. but after installing using pnpm install when i try to build the package either with pnpm package or make i get this error from electron-forge.

> [email protected] package /home/silver/game/debugtron
> electron-forge package
✖ Checking your system
An unhandled error has occurred inside Forge:
Command failed with a non-zero return code (1):
yarn --version
Usage Error: This project is configured to use pnpm

$ yarn ...
Error: Command failed with a non-zero return code (1):
yarn --version
Usage Error: This project is configured to use pnpm

$ yarn ...
    at ChildProcess.<anonymous> (/home/silver/game/debugtron/node_modules/.pnpm/@[email protected]/node_modules/@malept/cross-spawn-promise/dist/src/index.js:101:24)
    at ChildProcess.emit (node:events:527:28)
    at maybeClose (node:internal/child_process:1090:16)
    at ChildProcess._handle.onexit (node:internal/child_process:302:5)
 ELIFECYCLE  Command failed with exit code 1.

so i am wondering do i have to install with yarn first then run pnpm or am i missing something?

Visual Studio Installer directory is wrong

When running npm start this is the output I get, and no programs can be launched from Debugtron. For context, E:\debugtron\ is the debugtron repo path, and C:\Program Files (x86)\Microsoft Visual Studio\Installer\ is the Visual Studio Installer path.

[Error: ENOENT: no such file or directory, scandir 'E:\debugtron\"C:\Program Files (x86)\Microsoft Visual Studio\Installer"'] {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'scandir',
  path: 'E:\\debugtron\\"C:\\Program Files (x86)\\Microsoft Visual Studio\\Installer"'
}

Windows 10 version 2004 build 19041.329

Assertion failed! (Expression: cbData == sizeof(DWORD))

platform: Windows 64-bit
Version: 0.5.0

Reproduce
Upon launching the app, the user is greeted with two prompts like this:

Clicking ignore, and then it pops up again (and you click ignore again) seems to get pass this particular issue.

You can cause the issue again any time by clicking the Refresh button

Doesn't work for MSTeams?

Hi, when I try Debugton 0.5.0 on Microsoft Teams 1.4.00.4167 (64-bit), it does not connect.

Briefly it seems to try something, but then MSTeams pops to the foreground and is removed from the list

OS: Windows 10

[Feature request] Save manually imported (not found) apps for easy future use

Hello,

When apps are not found by Debugtron, but are successfully manually imported, it would be nice to be able to persist those in the list since they work anyway.

Thanks

Not working in Windows?

The loading indicator cycles forever, and no electron app is loaded into the list.

npm run start is OK ,but npm run publish will alert that can not find module simple-plist

Debugtron appears to hold open .asar file

I reported signalapp/Signal-Desktop#5426, but the issue turned out to be with Debugtron.

Basically, it looks like Debugtron is opening the Signal app.asar even though I've never used Debugtron with Signal. This interferes with Signal's ability to update. I understand that Debugtron wants to open this file in order to populate the installed apps list, but it should close the file once it's been read. The current behavior is quite counterintuitive, since I have no reason to think that simply having Debugtron open (without ever having it interact with Signal) would affect Signal's behavior.

Suggestion: Allow setting current directory and command line

I cannot attach this to the Daedalus wallet because it needs to run from a specific current directory. It would be great if there were a way to set the current directory (and maybe also command line, may be needed for some things). Also, the default for current directory should probably not be %localappdata%\Debugtron\app-0.5.0 but the directory in which the debuggee executable is located.

Will not open on a mac

Mac does not recognize developer and will not open

something errors with npm run make

When I download the source code and makeit, I encounter the following error. How to deal with it?
An unhandled rejection has occurred inside Forge: Error: The main entry point to your app was not found. Make sure "D:\code\electron\debugtron\.vite\build\main.js" exists and does not get ignored by your ignore option at validateElectronApp (D:\code\electron\debugtron\node_modules\@electron\packager\dist\common.js:104:15) at async WindowsApp.buildApp (D:\code\electron\debugtron\node_modules\@electron\packager\dist\platform.js:123:9) at async WindowsApp.initialize (D:\code\electron\debugtron\node_modules\@electron\packager\dist\platform.js:117:13) at async WindowsApp.create (D:\code\electron\debugtron\node_modules\@electron\packager\dist\win32.js:110:9) at async Promise.all (index 0) at async packager (D:\code\electron\debugtron\node_modules\@electron\packager\dist\packager.js:237:22)

App’s stuck and dragging Electron app over causes JS error

The app is stuck with the spinner.

Dragging the installed app over causes JS error:

Using Macbook Pro with macOS 10.14.6 (18G103).

Debugtron version 0.4.0.

Let me know if I can help debugging this or I am doing something wrong.

Add custom arguments to the debugged app

Is there a way to pass custom arguments the the debugged Electron app ? I tried with a shortcut (lnk) and I cannot see options in the UI or config file.

Edit: the only way I found for the moment is to modify the file https://github.com/pd4d10/debugtron/blob/main/src/main/actions.ts with, for example:

    const sp = spawn(
      app.exePath,
      [
        `--myarg=myvalue`,
        `--inspect=${nodePort}`, `--remote-debugging-port=${windowPort}`
      ],
      {
        cwd: process.platform === 'win32' ? path.dirname(app.exePath) : '/',
      }
    )

Then build with npm install && npm run start

Thanks!

Is there a way to block debugtron from opening a production electron app?

Great application, makes it really easy to test builds with no dev tools. While this is great for developers, as an app owner, I wanted to know if there's a way to restrict this app or the mechanisms this app relies on from being able to do what it does.

I know it's weird to ask in an issue that your app working as expected is the issue but really wanted to hear your thoughts on this.

Thanks

Handle executable running in the background

For example VSCode

After /usr/bin/code command executed, the current process will quit and the VSCode processes will be running in the background.

Linux support

I tried to install and run debugtron on linux, but with no luck.
Here is the backtrace:

debugtron /opt/github-desktop/github-desktop
internal/validators.js:125
    throw new ERR_INVALID_ARG_TYPE(name, 'string', value);
    ^

TypeError [ERR_INVALID_ARG_TYPE]: The "file" argument must be of type string. Received type undefined
    at validateString (internal/validators.js:125:11)
    at normalizeSpawnArguments (child_process.js:416:3)
    at spawn (child_process.js:555:16)
    at startDebugging (/usr/lib/node_modules/debugtron/lib/index.js:76:14)
    at Command.program.version.arguments.action.appPath (/usr/lib/node_modules/debugtron/lib/cli.js:11:7)
    at Command.listener (/usr/lib/node_modules/commander/index.js:315:8)
    at Command.emit (events.js:193:13)
    at Command.parseArgs (/usr/lib/node_modules/commander/index.js:653:12)
    at Command.parse (/usr/lib/node_modules/commander/index.js:474:21)
    at Object.<anonymous> (/usr/lib/node_modules/debugtron/lib/cli.js:17:4)

Keep process logs open after app dies

This should be a pretty obvious feature - there should be a way to keep the log output of a debugged app open after it exits.
Currently, it seems that the panel with the log output and thread list simply disappears, without a way to view the log messages when the app exits.

Doesn't work for DigiExam - - - Needs admin

The js of the application digiexam is obfuscated and needs admin to run. Is there a way to fix this?