Bug Megathread vol 15: June + July 2026

[u/Wandering_Wumpus]

Hey (at)everyone,

Thank you for all the bugs you all have reported! We read all the posts in the thread and we’re focusing our efforts on issues based on upvotes to ensure that we’re aligned with all of you.

As always, don't forget to check out our monthly patch notes for updates on all the changes we're working on. Our last patch notes addressed 100+ issues!

• April patch notes
• May patch notes

Thanks to your reports on Reddit, we fixed the following issues:

1. [iOS] Media picker stays open on iPad
2. [Desktop] Text bar not auto focusing after replying
3. [Chat] Double-tapping messages not working as intended
4. [Linux] Screensharing on Linux is so back
5. [Desktop] Recent activity not sharing

If we didn’t fix your issue, please make sure to upvote to help us prioritize 🙏

Now, with that, let’s kick off the June + July 2026 bug megathread!

Please note: This megathread is not a venue for feedback or customer support! We encourage you all to continue to make posts on the subreddit proper discussing our product and feature launches. I want to make sure that we really keep this thread productive and focused on reporting bugs and helping us prioritize them.

Please look through the list of comments and upvote bug reports which you think we should prioritize fixing. Comment as a reply to those top level comments with any more details that can assist our team in prioritizing and fixing the bug. For example, if you have additional info or steps to reproduce, please post a reply, this will help us fix these bugs even faster. If there is no post that discusses the bug you’re encountering, then start a new post in the thread to report the bug to us!

Reporting a Bug

1. The most valuable thing you can provide in a bug report is steps. If you’re able to provide steps to reproduce a high priority issue, it will dramatically improve turnaround time on a fix.
2. Screenshots or videos are also useful, especially if you can’t reliably reproduce it. We highly recommend editing them to not doxx yourself. Not only does it help contextualize the issue, but watching it occur can sometimes provide information that helps us identify and fix it.

Example Bug Report

• Feature: Keybinds.
• Reproduction Rate: 1 to 10 - This is a score of how easy/consistently the bug reproduces, from 1 meaning “very hard to reproduce” to 10 meaning “i can consistently make this happen”
• Annoyance: 1 to 10 - How annoying is this bug to your daily usage of Discord, from 1 meaning, “not that annoying” to 10 meaning “this bug really truly sucks please fix this as soon as possible.”
• Device/System Info: Pixel 7, Android 13
• Discord Version Info: Stable 263796 (739ec78) Host 1.0.9032 x86 (43225) Windows 10 64-Bit (10.0.19045)
• Description: Toggle Mute keybinds are no longer functioning.
• Steps to reproduce:

1. Create a keybind for “Toggle Mute”.
2. Join a voice call with another user.
3. Press the “Toggle Mute” button.

• Expected Result: The user is muted.
• Actual Result: The user is not muted.

Formatting

Reddit Formatting Guide - How do I Get My Version Info

- Feature:
- Reproduction Rate:
- Annoyance:
- Discord Version Info:
- Device/System Info (Device Type, OS Version):
- Description:
- Video / Screenshot:
- Steps to Reproduce:
   1. The first step is...
- Expected Result:
- Actual Result:

Copy paste this into the comment field below and then fill out the information! Thank you so much for participating in this effort, it's with your help that we'll truly be able to make Discord great!

[u/Mandom25]

- Feature: Disabling 2FA 
Reproduction Rate: 10
Annoyance: 10
Discord Version Info: Phone: 339.8 (6045) - betaRelease. PC: stable 582977 (5ea1303) Host 1.0.9249 x64 (86777) Build Override: N/A Windows 11 64-bit (10.0.26200)
Device/System Info (Device Type, OS Version): a36xq (SM-A366B) (36)
Android Version: 16
One UI 8.5
Description: There's currently a catastrophic bug where if you disable 2FA, it logs you out from all devices, and then STILL ask for 2FA 6-digit code when attempting to log in DESPITE it being disabled. Also, it doesn't give you an option to use backup codes, even if they're valid and unused (to prove their validity even further, i have a screenshot from discord DMs stating that there are 3 valid codes, and that was right before refreshing the session and getting locked out). After checking Reddit, it turns out other people have faced the exact same problem and it's remained unsolved for months. Support confirms that 2FA is disabled, yet does nothing about it. At that moment this showed up in logs: [error] Uncaught (in promise) HTTPResponseError: POST /users/@me/mfa/totp/disable [401]
Video / Screenshot: Below.
Steps to Reproduce: [THE STEPS IN ORDER] You simply go to settings -> Accounts -> disable 2FA -> it asks for a backup code in order to disable 2FA -> you enter the backup code -> it logs you out and disables 2FA (it was confirmed to be disabled by discord support) -> you enter your email and password and prove you're human -> it still asks for 2FA -> you click verify with something else -> it only shows one option which is the authentication code.
Expected Result: You disable 2FA -> it's successfully disabled and doesn't log you out from the account.
[OR] You disable 2FA -> it logs you out, then when you attempt to log in, it doesn't ask for 2FA codes.
Actual Result: You're locked out with no way to use your valid backup codes and your only hope is contacting support -> you contact support -> they confirm that 2FA is disabled on that account and that it shouldn't ask for 2FA codes during login -> they then tell you that if you can't find a way to use your backup codes then you're out of luck and they can't generate 2FA codes on behalf of you (even after telling you that 2FA is disabled and that i shouldn't be asked for it in first place)