Hello,
These were file's attributes that were blocking the writing (noticed by an @
with an ‘ls’).
They had to be removed with a "sudo xattr -c ..." (deleting only the
com.apple.quarantine was not enough)
HTH !
> Le 15 mai 2022 à 17:30, Ludovic THEBAULT a
> écrit :
>
>
>
>> Le 12 mai
On 5/12/2022 2:25 PM, Richard Gaskin via use-livecode wrote:
Bob Sneidar wrote:
> I don't think the latest Apple operating systems allow the writing
> to the App Support folder, even if you have explicit write
> permissions.
Where are we supposed to write application support files if not to
Bob Sneidar wrote:
> I don't think the latest Apple operating systems allow the writing
> to the App Support folder, even if you have explicit write
> permissions.
Where are we supposed to write application support files if not to
Application Support?
First they demanded control of the file
On 5/12/22 1:01 PM, Klaus major-k via use-livecode wrote:
on the Mac we have write permissions here -> specialFolderPath("preferences")
Works on Monterey as well and is "out of sight" of the user. ;-)
Am 12.05.2022 um 19:56 schrieb Bob Sneidar via
use-livecode:
Sandboxing. I don't think the
Bonsoir Ludovic,
on the Mac we have write permissions here -> specialFolderPath("preferences")
Works on Monterey as well and is "out of sight" of the user. ;-)
> Am 12.05.2022 um 19:56 schrieb Bob Sneidar via use-livecode
> :
>
> Sandboxing. I don't think the latest Apple operating systems
Sandboxing. I don't think the latest Apple operating systems allow the writing
to the App Support folder, even if you have explicit write permissions. It's
better if you put the file into her documents folder somewhere. To answer the
question you are about to ask, it's likely that her old Mac
Hello All,
I've made an macOS app for my sister that use an sqlite database located in the
application support folder (~/library/Application Support/myApp/base.db)
Since she replaced her old mac with an iMac M1, the app cannot write on the
database. I've checked the permissions on
