P: Saving copy not saving over jpg file

I have 22.3.0. On Big Sur. It is not fixed.

I have updated to 22.3.0 and the bug has not been fixed. 

Steps to reproduce:

1. Open new document. Make an edit.
2. Save As... (jpeg)
3. Add a layer to the document.
4. Modify the layer (with lines or text or whatever)
5. Save As... (jpeg)
6. choose the same filename.
7. Click Save
8. Click "Overwrite"
9. Look to see Untitled-1.jpg and Untitled-1 copy.jpg on desktop.

2stepbay. Have you updated Photoshop to 22.3.0 yet? for me the bug seems to be fixed. 

Charles, you can't save a layered .jpg under any circumstances.  We're talking when you have a current .jpg saved, made modifications, then do a "save as" to replace the current file. Photoshop will save the file name with "copy" even though you get the "... already exists. Do you want to replace it?" message.  

Now upon saying that. I did upgrade my Photoshop to 22.3.0, saved out 4 different files and at least for me the bug has been fixed. 

Oh, OK. Most of us have been there before, believing it has finally been solved. I’m guessing you didn’t try to save as a layered file over an existing JPEG file. Because, if you do, it will add “copy” and not replace it. THIS is why so many of us are fed up with Adobe for not fixing this in a year and a half. Especially because Photoshop runs natively on a Silicon Mac now. Anyone who reads this thread tested this on one yet?

This option is working for me. Thank you!!!

I don't work for Adobe, but I do know they are working on a fix. That's all I can say.

Being one of the earlier posters regarding this infuriating issue, I find it incredible that Adobe is apparently ignoring the issue. What else can we assume, since Adobe hasn't provided any information as to why this happens, or if they are even considering fixing it. It is easily the single most annoying and time-wasting feature of what is a great program. Wipe this spot of mud off Photoshop, Adobe!!!

agreed. really quite over the random notes about NOT a solution haha 
i can't believe they just keep rollin out the updates (more frequently than i remember with the last few versions) and still not a mention of this issue. did they really just kinda abandon this to focus on big sur/M macs or something? seems it.

I actually agree w u 100%. But I am tired of Dgrainger popping up making useless posts that take pointed jabs at ppl whenever anyone suggests blasting Adobe’s Twitter feed.

His false equivalences have ranged from divisively political to conspiratorial to rhetoric like his last comment, equating it to vandalism of religious objects. We get it, he doesn’t agree w/ “harassing” Adobe till we get action. But I’m over letting his useless inflammatory commentary slide.