Jump to content
You must now use your email address to sign in [click for more info] ×

MacOS - "can't open / save file permission problem"


Recommended Posts

I've contacted Serif Support over this.  Doesn't matter - Designer or Photo - Exact same problem.

It's been posted elsewhere.

Someone suggested that to get eyes on it, post a new topic. So, I am.

Support told me that it was a naming problem.  That underscores in the File names could cause the problem.

I added that NO OTHER PROGRAM I'M using has this problem, ONLY Affinity Programs.

So, the problem has resurfaced.  To be clear, it was working fine with underscores.  Then it STOPPED.

And now it's ALL I get.

So, to be fair to the suggestion, I renamed the file in a location with NO underscores:

A64100E4-3F2C-4EC3-84BE-145A9862A9AE_1_201_a.jpeg.3e312c57c742d54455e12347e119f0d3.jpeg

You might notice, NO underscores up above.  Failure to load - permissions problem.

It loads fine in other applications.  Again, JUST Affinity applications give me this headache.

If it's underscores at all, one might think they wouldn't save or load with underscores, but, they
HAVE.  

So, I'm not sure that's the problem.
 

If it's a MacOS problem, why would it not matter on ANY other program EXCEPT Affinity?

Odd, ya think?

 

Link to comment
Share on other sites

Perhaps this FAQ article will help:

 

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.3

Link to comment
Share on other sites

I looked:
 

"If you suspect that you're having this issue, open the Console app and then open the Affinity app and look for any errors similar to:

  • Sandbox: Affinity Designe(1637) deny(1) file-read-data /Users/{Username}/Desktop/Font Cache/{Fontname}.ttf"

Closed and reopened Photo. Tried saving a file.  Same error Message.  Checked Logs. Nothing.

Edited by fjunk
Link to comment
Share on other sites

1 hour ago, fjunk said:

If this were an error specific to fonts, would it occur across all applications or just specific to Affinity?

Depending on how your other apps use fonts it could be specific to Affinity.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.3

Link to comment
Share on other sites

58 minutes ago, fjunk said:

Even more odd.  I can't open or save.  I can open in another program, copy it, and paste via File from Clipboard.

Why would that even work if open or save doesn't?

Because File > New from Clipboard doesn't involve accessing files. So, if the sandboxing or permissions setup is affecting only Affinity, the scenario you describe could work that way.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.3

Link to comment
Share on other sites

54 minutes ago, fjunk said:

I can also drag and drop to / from assets.

I can also copy paste from Photo back to the originating program.

Neither of those involves opening additional files. And neither involves accessing any files that macOS might prevent a sandboxed application from accessing.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.3

Link to comment
Share on other sites

13 minutes ago, walt.farrell said:

Neither of those involves opening additional files. And neither involves accessing any files that macOS might prevent a sandboxed application from accessing.

 

14 minutes ago, walt.farrell said:

Because File > New from Clipboard doesn't involve accessing files. So, if the sandboxing or permissions setup is affecting only Affinity, the scenario you describe could work that way.

I closed and reopened Photo after setting up a new Asset Category and dragging some assets pulled over from Clipboard into the new Category.

The new Category was still there when I reopened Photo.  

It's yet another trick I use when files won't save.  Short of copying and pasting, which flattens all the changes.  At least saving as an asset retains the Affinity format.

Them still being there on reopening says they're being saved somewhere.

Same for "Restore"  /  "Recover" on a blunt shutdown.

Edited by fjunk
Link to comment
Share on other sites

1 minute ago, fjunk said:

Them still being there on reopening says they're being saved somewhere.

Yes. In a file that Affinity already has open, in an area of the filesystem associated specifically with that Affinity application and therefore (I assume) allowed by the sandboxing code.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro, version 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro, version 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
iPad:  iPad Pro M1, 12.9": iPadOS 17.3, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sonoma 14.3

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.