The simplest way to debug the main process is to simply insert logging statements wherever needed and have the application output logs of whatever is necessary.
For already built applications (or bugs that only appear in the packaged version of the application), you can view the Logs by going to Help > Show Logs in the 3-dot menu, which will open a file manager window showing the location of the log file.
If you’d like to make use of better debugging tools, you can use the Chrome Dev Tools or the debugger in VSCode by following the steps here: https://www.electronjs.org/docs/latest/tutorial/debugging-main-process
The renderer processes are controller by Chrome instances, so each of them will have their own Developer Tools instance.
You can access these instances by going to the View menu (under the 3-dot menu on Windows/Linux, and in the top bar on macOS) and selecting:
There are other
BrowserViews that are governed seperately from the main application wrapper, including:
main/teamDropdownView.tsfile. In the constructor, at the end, add:
// macOS/Linux export MM_DEBUG_MODALS=1 // Windows PowerShell $env:MM_DEBUG_MODALS = 1
main/viewManager.tsfile. In the function
showURLView, at the end, add:
Some issues are only reproducible on the Desktop App, though the code that is causing the issue may not live in the Desktop App.
Here are some ways of determining whether this is true:
isDesktopAppin the webapp.
If you have determined that the issue doesn’t apply to the Desktop App code base directly, you can file a ticket in the appropriate repository, such as the server or webapp repository.
If you are having trouble determining where the issue lies, feel free to post in the Developers: Desktop App on Mattermost Community, or you can file a ticket in the server repository and it will be triaged and transferred to the appropriate location.
Your feedback helps us improve the Mattermost developer documentation.
Have a feature request? Share it here.
Having issues? Join our Community server.