P: Saving copy not saving over jpg file

[FeedbackCommunityMember]

working on Catalina OS. saving file extension works now but does not save over jpg when saving it creates a copy which is annoying and time consuming to fix

[SendyFiala]

With version 22.3. (March 2021) Adobe says it is fixed:

Fixed issues in Adobe Photoshop

But it is not!

Such a shame...

[2stepbay]

@Sendy Fiala I haven't updated yet. Will do so later. Is the save behavior the same as previously reported? If so, I wonder what Adobe thinks it fixed.

[SendyFiala]

yes, it is exactly the same behaviour. I'm on Mac OS Big Sur. Some says that this is problem related to Mac operating system, but it isn't. Other apps don't do it. Even other apps within Adobe CC don't do it. Even Photoshop don't do it if you use Quick Export function (set up in Preferences, Export tab - you can change the filetype to JPEG). As I wrote elsewhere, Adobe is erratically patching their bugs, bringing the new ones along with each update. They should take their time, fix all bugs, carefully do beta testing and bring update two times a year max. Their behaviour results in situation, when proffesionals are scared of every single update.

[mig15]

Adobe are so hopeless. IT IS NOT FIXED!!!!!!!

[helenec76070263]

It drives me so crazy!!!

[MK178]

It's not just Photoshop, it's Illustrator, and Dreamweaver

[FeedbackCommunityMember]

Still not fixed on 22.3.0

Now my simple question is: when will it be fixed?

Seriously please.

[FeedbackCommunityMember]

PS: i'm going to ask for a refund on this.

Please do that too, we have to raise our voice.

[Treehouse5C82]

I'll say it again... 
Broadcast that comment on Adobe's Twitter feed, maybe that will

get their attention?

[dgrainger]

Some people think that spraying graffiti on Hymnals is a form of communication.  To the civilized part of the world it is simply destructive behavior.

[JasonHughes7819]

Dgrainger back with more of his false equivalences & value judgements 🙄

[dgrainger]

@jh_b8ih8qyak6flq  You must be one of those that think it appropriate!

[JasonHughes7819]

Wrong. Do you ever tired of being on that high horse?

[HelloHaggis]

Hey gang. I hope I speak for everyone else subscribed to this thread (all 181 of us) but the back and forth bickering between individuals isn't helping anyone. Numerous times when I see this start up I ALMOST unsubscribe from this post and I wouldn't be surprised if others have. I stay subscribed for that ONE DAY when Adobe finally makes this a priority and we can mark this fixed and go about our lives. Sure we are all annoyed nearly a year and a half later but man, gotta say I appreciate the radio silence here when there is no news to report. If an update comes out and its still broke, news worthy but as a community here, if we can try not to chirp each other, the rest of us hanging out on the sidelines would appreciate it. Thank you!

[JasonHughes7819]

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. 

[alland.byallo]

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.

[FeedbackCommunityMember]

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!!!

[JohanElzenga]

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

[MK178]

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

[chazcronOMS]

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?

[MK178]

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. 

[MK178]

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

[mrbobdobolina]

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.

[SendyFiala]

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

[sebaguila@gmail.com]

Did your files have layers?