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
The Discord room lines up. A server's and the DMs' lists end above the call and user panel, not under it; the "N new messages" bar sits above the conversation instead of over its first message; Friends' list keeps its width beside Active Now on a narrower window; a voice channel's count stays clear of its icons; the header search, a Jam invite, an embed and a voice chat's side panel fit their boxes at 1000 to 1920 px and large text. A geometry audit of the room ran in the dev preview, not in the installed app. Checked in code only.
Crash reports are on by default, with no switch. When Exo hits an error, or you copy an error's log, it sends one short report to Exo's service. It holds Exo's version, your Windows build (numbers only), the error's type and a log excerpt of up to 8 KB, with paths, links, names, ids and tokens taken out on your PC first. No IP address or account is stored, and reports are deleted after 30 days. Settings › General no longer has the Send crash reports switch or its preview; Settings › About says in one line what is sent. Checked in code only.
Unhandled crashes wait for the next start. An unhandled crash (an error that closes or breaks Exo) is saved on your PC in a pending report file and sent once, on the next start, under the same daily limits and scrubbing as every other report. Copying a log is unchanged. Checked in code only.
Freezes are reported too. When Exo's window stops answering for more than 5 seconds while it is on screen, a report of the freeze goes to Exo's service the same way. Checked in code only.
Failures are reported. A WebView2 browser that exits, Discord's connection or voice failing five times in a row, Exo Capture exiting with an error, a store launch or install failing, and an update failing each send one report. Checked in code only.
Reports are limited. A PC sends at most one report of the same error and cause per UTC day, and five reports per UTC day in all. The count is kept in a local file with hashed keys only. Checked in code only.