You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying to debug some issues with the current binary builds of the app, I've found that when things go wrong it's very hard to figure out what's up, since the developer console isn't available. This will also make it difficult for users to report certain issues helpfully.
One thing that would help a lot is if we could dump the browser console output (including and especially uncaught exceptions) to a log file.
Alternately, it looks like we can enable devtools in the release build; tauri-apps/tauri#3059 (comment) has instructions on how to do this.
Combining these two would be almost ideal, could then have users send log files when stuff goes awry, and easily debug things myself at the same time.
The text was updated successfully, but these errors were encountered:
While trying to debug some issues with the current binary builds of the app, I've found that when things go wrong it's very hard to figure out what's up, since the developer console isn't available. This will also make it difficult for users to report certain issues helpfully.
One thing that would help a lot is if we could dump the browser console output (including and especially uncaught exceptions) to a log file.
Alternately, it looks like we can enable devtools in the release build; tauri-apps/tauri#3059 (comment) has instructions on how to do this.
Combining these two would be almost ideal, could then have users send log files when stuff goes awry, and easily debug things myself at the same time.
The text was updated successfully, but these errors were encountered: