P: Saving copy not saving over jpg file

This is the most confusing part to me, because it means that whatever the issue *is* it can be "solved" by using a specific name... which means it *technically works* (the best kind of works) but yet doesn't actually work.

I would pay money to talk to an Adobe Dev to get some BTS info on this one.

Hi All,

I just updated today to 22.1.1 and I discover the most stupid behavior. The bug is still there, but if your original psd file is name something like "yourfile copy.psd", and then you overwrite the jpg render it has no problem. So basically what I'm saying is, if you add the word copy with a space to your file you can work as normal. The most bizarre workaround, not sure if this happens to anybody else.

This is of course not a solution, but at least I don't have to change the file name every time I render a .jpg

@4470847_wells "overwrite a file which is already open" ?

That explanation they gave doesn't make sense to me, it was working for as long as I can remember, years, until around late 2019, and all my other applications can do this simple task.

The files I try to replace are not open, they are sitting idle in a folder. The layered file is open and I try to save and replace other existing files in a folder and those are not locked. I can replace over an existing .pdf, .doc, .xls, .jpg, .png, and so on, using another application but not with Photoshop.

Lol I know you're quoting what they tried to explain, maybe they were just shooting ideas? Whatever that was, that isn't what's going on and it got my attention. My cheap and free software can do this and Pshop developers are baffled.

Well said, @andrew_croft . Some great suggestions and insight.

And thanks for the PDF tip! ha =ha. I have a vendor point-of-contact who insists on sending locked files initially, having to return them, get their art guy to unlock them, and send them back. Every. Single. Time. I'll give this a try first next time and save myself a few face palms. 🙂

@andrew_croft 

Lots of information!  I have wondered for quite a while why I do not experience this and other problems, using a Windows machine. Thanks for the insights. BW, a number of Adobe Employees do, in fact, monitor this forum; their responses to this and other issues in other threads are all over the place.

The issue definitely stems from Apple's new security and Full Disk Access settings with Catalina and continues with Big Sur. BTW - don't upgrade to BS until they fix a lot of bugs - no more font management - sizing windows is complete crap - long way to go to make it a viable OS.

Clearly Apple instituted the disk access pref to create an elevated level of security - good for us overall - but clearly Adobe was caught unaware and is incapable of responding with any viable solution. Adobe is supposed to get advanced OS development packages to go over any necessary updates to make their apps compatible with new OS releases. They didn't, and now it isn't.

Don't call their support - they consider this a new "feature". It is not.

Neither Apple nor Adobe gives a rat's ass about this.

Apple is too busy creating all kinds of new emojis for their phone-based OS. Just wait another year or so when your multi-thousands dollars MacBookPro works more like a phone than a viable working tool. Apple's new M1 chip will do just that. Just you wait!

Apple and Adobe have been at each other's throats over Flash for a decade.

Apple allows you to "PRINT" a locked PDF with their Preview app to create an unlocked version, completely undermining the security of Adobe's PDF format. This is horrifying but again, neither Apple nor Adobe seem to give a rat's ass, otherwise Adobe would have figured a way to prevent this. It's been like this for um, four years? Five? So don't think your locked PDFs are truly secure. They are not.

This is just another in a long line of craptastic manoeuvres between Apple and Adobe and we're caught in the middle.

Add to this - and just need to clarify again - ADOBE DOES NOT MONITOR THIS FORUM. They created "community forums" so that we, the user, do what their support is supposed to do - solve problems with their software.

So what I did do over the holidays when I had some downtime was to start a support chat, ask to speak to a tech, and then walked them through an issue in Illustrator - the scaling/reflection tool bug that introduced weird numbers, negative numbers into the dialogue box, making the live preview useless. I was paid for my time in a credit on my subscription. I'm certainly not going to assist Adobe for free.

Suggest we all do the same.

Interesting. It could be that Adobe are washing their hands of it blaming Mac OS! They really need to be solving the issue and work with apple on the problem. As Philip said, it'd be good to know the technical reason why this is happening. They must know!!?

I tried it on my Windows VM and it works flawlessly. I created a psd file with multiple layers. Saved as a jpg and then changed the color of one of the layers and saved a new jpg and it saved right on top with no issues. All with a multi-layered file... 

I have some friends who use PS on Windows and when I have complained about this in the past they seem to not know what I'm talking about, but I should ask again.

I did ask some developers to speculate on this on the MacRumors forum. A few devs agreed that this sounds like a situation where the program is trying to overwrite a file which is already open (or locked for editing) so it makes sense that a copy is created... Which normally means saving a copy, deleting the old one, and renaming the new one, (so that no work is lost in the event of a power failure, system crash, etc.) 

However, I don't know if that fully explains why "it just works" when appending " copy" to the filename.

Personally, I'd be fascinated by a technical explanation for why this happens, but Adobe seems pretty quite on this.

Great question! Would be very interested to hear from Windows users also (if not already covered in this long-running thread).