P: Saving copy not saving over jpg file

Well James, I won’t throw an F bomb but I can’t say the frustration in the threads for these problems is out of line. I’ve worked on free mobile apps that users and lit my inbox up over the silliest of things, often user error and not always an apology after respectfully responding back but two differences: one, I always communicated back. As far as I know, nothing from Adobe in over a year on this. And two, at $636 a year for a program with such a simple problem to fix is ridiculous. Not sure why your software cost but paying monthly I do EXPECT it to work every month. Day one it should support a new operating system and not start its beta on that day. Don’t forget, they made this problem for themselves going subscription. Maybe they should take a note from Microsoft who is making Office switch back off subscription. 

As somebody who really wants to see this fixed, I would like to see more respectful communication.  I can appreciate your frustration.  I worked for years as a software engineer on a totally unrelated product.  I never found complaints with such strong expletives to be motivating.  There have been some responses, but not very adequate ones.

@8016240 Jaster Same issue with TIFF files. Had to make a last minute photo edit before sending off to print only to have the pre-edit photo remain while the post-edit photo sat in my assets folder as filename_copy.tif. So frustrating. Boss wasn't very happy (though not as upset as I was). It's unfortunate Adobe doesn't give a flying f**k. Been at least a year (and numerous updates) without a fix or even a response here or on adobe forums.

@Angel_Jackson Hahahahaha. Sorry Angel. Most likely Big Sur will be Bug Sure with respect to Adobe(and, frankly, with the new processors, every software package). We will get to enjoy ALL kinds of new things Adobe can't fix for months. Yeah, they both will be to blame, but that's not how Adobe will spin it.

I got all my hopes in Big Sur now, hoping we will go back to normal jpg overwrites since there are no issues in Mojave.

You may need to flatten all the way? If it still has one "layer" it won't replace. Like when Merging all the layers, it still has one floating layer... If you go to: Layer >> Flatten Image it should turn the only layer left to "Background" then the "save as" should replace without adding "copy" to the name. 

I really wish Adobe would just fix it. Good luck!

Same problem here on Catalina, photoshop 21.2.3. Photoshop will not overwrite a JPG, it adds "copy" to the filename which is annoying and slows down workflow, as I need to manually go to folder, delete previous copy and remove "copy" from the fie name. This never happened to me in previous Mac os. I am saving a lot of files daily.

"Export as" or "Quick export" workarounds work in my use case, but they are not ideal. "Export as" loads slower than "save as" while if I change "quick export jpg" then I can't quick export one layer as png which I often do. For the love of god Adobe, please fix this!

Thats not the case. I have tried the 'pain in the ass minefield' of manually flattening the psd myself first, the issue comes in when I 'save as' over the preexisting jpg.
Still creates a copy of the jpeg. 

PS will overwrite (replace) with FLATTENED files, so if you flatten the PSD file, THEN "save as", the JPG will be replaced. Total pain in the ass and dancing on the minefield of losing your layered file, but maybe faster than the "go to & rename" work around. Latest PS update yesterday: 21.2.3, STILL does not fix this issue. Thanks 2020. 

Welcome the Photoshop Dysfunctional Family where we all have the same issue for the past year and no signs of it being fixed.