The problem was and is that the specialfolder stuff works until it doesn’t. I had one user last week doing a test where specialfolder.applications was not there in one execution of the test and there the next.
Hahahahahha… thanks, Sam, for making me laugh. It’s great the specialfolder.ApplicationData works. But that doesn’t help for the broken Specialfolder.applications. And if Michel uses a Mutex then he is out of luck anyways.
[quote=457070:@Emile Schwarz]Copy YOUR application and run the two of them
Unless, Catalina refuse to make application(s) copie(s) [/quote]
There will always be ways for users to mess up. They probably also neglect to change tires on their car, and set their house on fire with hazardous electricity wiring. Pity. I am not shedding a tear for loonies.
I ust recall that Firefox reject the load of a second Firefox application with a message.
This can happens when the application already run and you drop a document on the Dock icon (and that icon points to a different application).
This can happens when you have an external hard disk. It can be pure hazard (not done to annoy the application creator).
From the problems we are seeing it looks like Apple have further broken FSRef based APIs in macOS 10.15. As soon as you start putting files into the temporary folder weird stuff happens.
Another application cannot access your temporary files if it has a different bundle ID.
If you copy a file into the temporary folder and it has extended attributes applied you cannot access it properly.
No error. So it would seem the user can access that folder, but not a program.
The plot thickens…[/quote]
For us, access isn’t 100% broken as our application can perform basic file IO actions to the temporary folder.
The tests we performed during the Catalina beta seems to indicate a strange integration between FSRef based APIs and the temporary folder. Some (maybe all) of these issues disappear when you use newer file system APIs (ie: built using Xojo 2019r2).
We currently have 3 open cases with Apple going back to August with two of them not receiving a response so I am not very hopeful that this will be addressed.
What makes this worse is that Xojo left it to the very last minute to update the macOS APIs being used for FolderItem and rolling that muchly needed improvement into the same release as a major change (v2 API) making it difficult for users to respond quickly.