Copilot code application stopped working

[facepalmdesign]

Select Topic Area

Question

Copilot Feature Area

Visual Studio

Body

The Apply button in Github Copilot chat suddenly stopped working today. Response generation works great but when I click the Apply button to overwrite my code with the suggestions, it switches to the Ask Copilot dropdown without making any changes. This happens in both Ask and Agent mode.

Here is an example, where I asked Copilot to remove all comments and it properly generated a new .cs without comments. When I clicked Apply, instead of making the suggestions, it just opened the Ask Copilot dropdown menu. The logs say MappingCompletedNoEdits despite having changes between the two codes.

The issue started today. I updated Visual Studio 2022 to 17.4.4 after the problem occurred, but it didn't help. Tried signing out/in of GitHub, also removing/adding Copilot through the installer's Modify menu - I'm using the plugin part of the Game Development Workload. None of these solved the problem.

Any advice as to what could be the problem?

Here are my settings, in case there is something fishy here:

[forsbergjohan]

I also have this issue

[forsbergjohan]

Have you made a ticket for it?

https://support.github.com

[facepalmdesign]

Have you made a ticket for it?

https://support.github.com

No. Not sure if it's a bug or something went wrong on my end. But it seems worthy of reporting so I'll do it.

[TMaxwell8]

Same issue, worked perfectly fine last night, now not working.

[MoodinAhmed1]

did anyone find a solution]

[facepalmdesign]

The issue went as it came, it works like before. I'll close the thread when someone else confirms it.

[KatsaounisThanasis]

FYI

[Lusan-sapkota]

I'm facing the same issues recently. In my case, VS Code often crashes or freezes while applying code blocks, and occasionally it even force-exits entirely. Lately, GitHub Copilot sometimes doesn’t apply the block at all even when the suggestion looks correct.

This definitely feels like a performance regression, and I’ve noticed it aligns with some degraded status updates on the GitHub Status page. Hopefully, it's something they're actively working on.