How can you enable debugging for main process - for a built app.?
See original GitHub issueI’ve been using this boilerplate for 2 projects so far, lately i am running into errors in main process only in the built app.
when running npm run dev it works fine.
My question is: how can i enabled debugging for main process on a built app.
Update: For now i am just logging to file to debug - but there should be a real solution.
Issue Analytics
- State:
- Created 5 years ago
- Comments:10 (1 by maintainers)
Top Results From Across the Web
Debug your app - Android Developers
Enable debugging · Enable debugging on your device: If you're using the emulator, this is enabled by default. But for a connected device,...
Read more >Enable debugging for ASP.NET apps - Visual Studio (Windows)
Publish in debug mode using the file system · For ASP.NET, select Local IIS, select the website you created for the app, and...
Read more >Enabling USB Debugging on an Android Device - Embarcadero
On the device, go to Settings > About <device>. Tap the Build number seven times to make Settings > Developer options available. Then...
Read more >What Is USB Debugging Mode on Android? How to Enable It
USB Debugging allows an Android device to communicate with a computer ... Android has a built-in printing function, so when writing an app, ......
Read more >Debugging an Electron Application - Manning
With these two configuration files in place, you can click on the left margin of any line in your main process to set...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

@yanivkalfa I added
@sentry/electronto myapp/package.jsonfile - it had to be this one or I’d receive errors from the rootpackage.jsonfile.Then in my
main.dev.jsandindex.jsfiles, have something like this as close to the top of each file as possible, so that it can catch exceptions as early on as possible:Obviously updating the
dsnvalue with your own.Then if exceptions happen, they appear in the Sentry web app.
Have you tried:
DEBUG_PROD=true npm run packageIt works for me, and gives you the Chromium developer console. This is documented in the README.