Desktop App Crashes with “Cannot read properties of undefined (reading ‘isDestroyed’)” on Quit or Relaunch

Marco Kundt

Updated July 08, 2026 11:03

Desktop App Crashes with "Cannot read properties of undefined (reading 'isDestroyed')" on Quit or Relaunch

Applies to: Mattermost Desktop App v6.2.2 and later; not fixed by any released version

Symptoms: The Desktop App crashes with a TypeError referencing isDestroyed during app quit, relaunch, or when a server connection fails to load.

🛑 Problem

The Desktop App crashes with an unhandled TypeError in its internal load-retry logic. When a page load fails and the app retries, it checks whether the browser view has been torn down - but that guard does not null-check the underlying view. If the view was already torn down (during quit or a retry race after a failed connection), the check throws instead of returning safely. This is a Desktop App defect, not OS-specific.

Symptoms

Users or administrators experiencing this issue will see:

TypeError: Cannot read properties of undefined (reading 'isDestroyed')
    at x.isDestroyed (/Applications/Mattermost.app/Contents/Resources/app.asar/index.js:2:340321)
    at x.loadRetry (/Applications/Mattermost.app/Contents/Resources/app.asar/index.js:2:341394)
    at /Applications/Mattermost.app/Contents/Resources/app.asar/index.js:2:337896

Additional symptoms:

The crash recurs across multiple relaunches and is not resolved by upgrading from a release candidate to the corresponding stable build; the affected code is identical between the two.
The crash is not limited to a specific OS or OS version, including beta releases.
The crash occurs more often when the app's initial connection to your Mattermost server fails to load, since that failure is what drives the retry path.

✅ Solution

No released Desktop App version fixes this defect yet. The steps below reduce how often you hit the underlying load-failure/retry race; they do not eliminate the defect.

Delete the Mattermost configuration folder

Deleting the local configuration folder removes corrupted state that can trigger repeated load failures and drive the retry race. The app recreates the folder on next launch.

Quit the Desktop App completely before deleting any files.

Windows: %APPDATA%\Mattermost (i.e., C:\Users\<username>\AppData\Roaming\Mattermost)
macOS (installer): ~/Library/Application Support/Mattermost
macOS (App Store): ~/Library/Containers/Mattermost.Desktop/Data/Library/Application Support/Mattermost
Linux: ~/.config/Mattermost

⚠️ Important: This removes your saved server list and app settings. You will need to re-add your Mattermost server URL after the app relaunches.

Re-add your server

After deleting the configuration folder, all saved settings and server entries are removed. When the app relaunches, add your Mattermost server URL again.

⚠️ Important: Avoid quitting the app while it is still loading; quitting during an in-progress page load is one of the conditions that triggers this crash.

Collect logs if the crash persists

If the crash continues after the steps above, collect the Desktop App logs before contacting support so the crash can be correlated with your specific load conditions.

~/Library/Application Support/Mattermost/logs/

Additional Resources

Related to

desktop app