IIRC they changed the Mac API’s they used under the hood for files fairly recently… If that is the case, was it after 2019 r1.1?
BTW if you use API 1 code in the current version, does that work? If it was an unwed teh hood API crag would expect that to a fact API 1 code as well as in most coast I think the API calls they use are likely the same…
So if the API 1 code works in the current version, it would alley be an API 2 implementation bug, if not it’s likely due to a Mac API change.
It worked in 2019r1.1 using API 1. It doesn’t work in 2020r2 using either API 1 or API 2. I haven’t used any of the interim versions. You are probably correct that it’s a change with the internal OS APIs being used. I’m busy putting a demo app project together, since that seems to be the trick to get stuff verified.
One of things I noticed is that newer Mac OS API tend to be less “Mac” like and more Windows like… The not being able to rename something in use is a very Windows like behavior, that as a long time Mac user, has always annoyed me.
Oh well I guess the kids working at Apple grew up using PC’s!
I distribute some software on flash drives. It involves copying and verifying files and renaming the flash drive volume appropriately. This is all done via a Xojo program. I could do the renaming manually, but knowing me, I will forget.