P: Saving copy not saving over jpg file

I submitted this bug to Adobe and "Adobe is aware of this problem and are working to fix it" 

That hasn't happened yet.

The work around: don't save the path layer and work only on the work layer.

So, yay?
I still have to add "copy" to my file names so the links don't break.

Now I experience another bug - drawing path is no more working after you drowe your first path. Every next path creates only dots, not connected by lines. Adobe is such crap company! Why they release new versions each month (and even more often), when these are filled with new and new bugs!!! I don't want to update my software so often, rather they should do one a year, properly beta tested. They are using their paying customers as beta testers! Shame on Adobe!

Let's take a breath here and reflect on the fact that Adobe, which is making millions with its software-rental rip-off, can't figure out how to save a file.

And a lot of you are still paying them.

Thanks @andrew_croft ... I understand that Apple may have created difficulties for Adobe - but in all honesty there's no excuse. Adobe has a subscription based business model now. Most of that money goes towards 3D software and the core community, graphics and photographers, are left hanging on basic issues. This is a seperate issue but we are asked to pay the same amount as the areas where most of the development is going. the least we can ask Adobe to do is to allow us to save a file without " copy".

I don't really care if I'm on MacSur or Catalina or Snow Leopard. Saving is pretty basic.

OK - I'm going to go out on a limb here - as many other have done so in the past...

This has NOTHING to do with a layered file. Nothing at all. I can change ANY file, layers or no layers and "Save As" and it will create a copy.

This likely has to do with Apple's new "Disk Access" permissions, introduced with Catatlina, I believe, do not recall if earlier because I think I avoided a few OSes because they were crap. Only to land on Catalina, which was even crappier, then to jump to Big Sur which is pure hell.

We strive to stay current. I am old enough to remember the horrible death of type houses, because I went into a lot of production houses and trained their staff on this new thing - DTP - starting in 1988. But with us striving to remain current - current OS - always having the latest Adobe Creative Suite - we are also living on the bleeding edge of technology.

I do not intend to die out quietly like an old typesetter. I am going kicking and screaming because both Apple and Adobe are just not getting it right now.

Anyone care to start a thread on type management - or the complete non-existence of - in Big Sur? 28GB of craptastic junk foreign fonts and absolutely no way to remove them.

Even an Apple support person told me bold-faced - just disable them with FontBook. I waited on the phone while they coughed and sputtered through the rest of their futile explanation - hitting a brick wall as they tried.

I need a hug.

@james_gray_6321432 I just talked to Adobe support and it appears that Adobe needs the file to be in 8bit and flattened  in order to save without copy. I explained this isn't a workable solution because photoshop is actually requesting me to run the risk to loose all data in a working file. He will raise this with engineering and gave me a ticket number. 

In the meantime I am using Apple Automator to rename the files by finding " copy" in the filenames and replacing it with "" and then moving it to a different export folder.

I have an update and confirmation from Adobe that Adobe Photoshop needs the file to be flattened and in 8bit before it can save the file as abc.jpg rather than abc copy.jpg. 

I mentioned to the support staff that this is a major flaw and very risky because what Adobe is requesting me to do is actually run the risk of loosing data by destroying / flattening all layers before I can save a file without the word copy. I explained that PSD files are often working files and should only be flattened once the final file was delivered to the client. I also mentioned that this is a fundamental issue and should be treated with great priority. Saving files and how Photoshop behaves when doing so isn't about a 'feature' but about professional needs. I also mentioned that actions do not accept "Export as" as an alternative making the automation process petty clumsy. 

He said that he will raise this with engineering and gave me a ticket number. I will keep the community updated.

In the meantime I have a workaround which could be beneficial for Mac users. I export my JPG's / PNG files into a working folder which Apple Automator automatically renames and then moves to a final folder. Attached is the workflow for anyone who is interested.

I cannot be sure, but I think the OS has everything to do with the issue.

*kleer_keret_tali It isn't working for me. 22.3.1 on Catalina. Not sure if the Operating System has anything to do with it but 22.3.1 didn't change a thing for me.  

I'm on PS 22.3.1 release. MacOS BigSur 11.2.3

I'm now allowed to check and UNCHECK the SAVE A COPY box when performing a SAVE AS.

Finally!

Every time I got a communique from Adobe or a survey or had a program crash and a report generated, I responded be asking for this crap issue to be fixed. Been doing it for years.