linked resource permission denied

[Sonnilein]

Hi,

I have a problem in context of opening an Affinity Publisher file with linked resources. 

Opening a file via "open resent" the message "Linked resource permissions denied" appears.

Whatever I select, affinity crashes "unexpected".

Affinity publisher has full disk access in system settings and I am using the newest available sw version.

The listed folder is accessible within affinity, it's possible to open the listed file directly. But sadly not as linked resource.

I am using Affinity Publisher 1.10.5 running on Mac OS Mojave 10.14.6.

Do you please have an idea / hint for me to solve this issue ? Would really make me happy 🙂.

[v_kyr]

Welcome!

See related:

 

[Sonnilein]

Thanks for the hint, but I am not able to solve my problem.

When I open my existing apub-file (created last summer with older affinity version) I get this message:

Whatever I select Affinity crashes.

When I rename the sub-folder PNG to PNG_new and open the the apub-file,  affinity gives me the message that resources are missing.

Now I can relocate it with the Resource Manager, all linked resources are shown as "OK", with the new folder "PNG_new".  When I close affinity and re-open it, then again the message "resource permission denied" is shown (with new folder PNG_new).

When I use the "yes" button (instead of Resource Manager), then I can select the missing png-file and then I get again the message 

This message appears for all 150 included linked resources, even if I did the relocation (with "Yes" Button) only for the first png-file. It seems as if all 150 files are found (not missing), but permission is denied.

So whatever I try (for resource management, relocating relinking), the problem does not disappear.

 

 

[v_kyr]

3 hours ago, Sonnilein said:

When I open my existing APub-file (created last summer with older affinity version) I get this message:

Are the used APub versions (in the past and now actual) listed to be file format wise backwards compatible between the used versions?

Quote

Whatever I select Affinity crashes.

When I rename the sub-folder PNG to PNG_new and open the the apub-file,  affinity gives me the message that resources are missing.

But the file then opens without crashing APub?

Quote

When I close affinity and re-open it, then again the message "resource permission denied" is shown (with new folder PNG_new).

When just closing and reopening, or after performing first an "File > Save as..." under some different file name and then afterwards reopening that new saved/created file?

Further is your file access path shown there entirely on your local disk, or is it some network mounted path in "Documents/...")?

[Sonnilein]

Quote

Are the used APub versions (in the past and now actual) listed to be file format wise backwards compatible between the used versions?

Sorry, I can not answer this question. I don't know how to find out details about the file format. 

Quote

But the file then opens without crashing APub?

When I select "Ignore"-button (a lot of times, for each linked resource) affinity does not crash. Affinity opens the file with a lot of "linked resource sandbox errors". Then I can go into the Resource Manager and relink the resources. By this the sandbox errors disappear, "OK" is shown for every linking. Then I save the file, close Affinity and reopen the file. And again "Linked resource permission denied" appears.

When I select "Authorize folder" then Affinity crashes.

When I select "Authorize global" then Affinity crashes.

Quote

When just closing and reopening, or after performing first an "File > Save as..." under some different file name and then afterwards reopening that new saved/created file?

I tried both, behaviour is the same for both cases.

Quote

Further is your file access path shown there entirely on your local disk, or is it some network mounted path in "Documents/...")?

Entirely on my local disk.

 

[Sonnilein]

I just created a file version with reduced amount of linked resources (reduced to 5) to simplify the analysis. 

After opening I selected "ignore" for 4x and it looked like this:

I was wondering about the different handling for first resource with "OK" and the 4 others with sandbox err.

When I do the relinking then all 5 show "OK".

Saving (even under new name) and re-opening leads again to message "linked resource permission denied" after opening.

 

[thomaso]

If you purchased Affinity in the Apple App Store then you may have a Container folder for Serif or Affinity within your user library folder. Their is a known issue in macOS with possibly confused Container folders. Though this article is from 2013 it might be worth a trial for your macOS Mojave, 2018:

«Lastly, there's the possibility of faults in the program's sandbox container, which is a mirrored structure of your user account that is presented to the program. It is through this container that the program accesses your account's folder hierarchy, so if there is a problem with the container, then even if your account's permissions setup is perfectly fine, the program may report access errors, even after restarting and relaunching the program.

In this case, you will need to clear the program's container so it can be rebuilt from scratch, … »

https://www.cnet.com/tech/computing/fix-permissions-errors-for-sandboxed-applications-in-os-x/

 

[Sonnilein]

@thomaso: your hint was the solution !

Even if I did not really understand the sandbox-problem (I have never used the consol of my mac and could not find any "sandboxd," using the consol) the referenced article gave me the important hint: to relaunch the application (affinity publisher) and then to restart my mac.

This simple thing solved the access problems / sandbox errors. 

Now I can open my apub-file without any problems - that's great  - many thanks to you all for your time and patience !!!!

P.S.: Ich seh grad Du sitzt ja in Köln - dann hätte ich ja vielleicht noch Hoffnung gehabt, die "magische Konsole" mit Deiner Hilfe zu bedienen. Aber zum Glück bleibt mir die Konsolen-Benutzung erspart - vielen Dank für Deine Hilfe 🙂

 

 

[thomaso]

On 10/11/2022 at 9:26 PM, Sonnilein said:

to relaunch the application (affinity publisher) and then to restart my mac

That's it? Just a simple reboot – or a Safe Boot in between?
(actually I wonder that you haven't tried a reboot anyway before posting, with such an error message that sounds to touch general security of the mac)

Bist du denn auch in Köln?

[Sonnilein]

I did a reboot after very first steps (disk access settings, affinity update).

But I did not have the idea to delete affinity completely and re-install it with reboot.

Nö, ich bin nicht in Köln, bin in der Nähe von Wolfenbüttel.. Aber auf deutsch hätte ich mich evtl. mit dem ganzen Sandbox-Gedöns / Konsole auseinander gesetzt, wenn das Problem nicht so einfach zu lösen gewesen wär.

[thomaso]

On 10/11/2022 at 9:26 PM, Sonnilein said:

the referenced article gave me the important hint: to relaunch the application (affinity publisher) and then to restart my mac.

This simple thing solved the access problems / sandbox errors. 

So was the solution this simple thing of relaunch + restart? … or rather the process of deleting + reinstalling Affinity?

7 hours ago, Sonnilein said:

I did a reboot after very first steps (disk access settings, affinity update).

But I did not have the idea to delete affinity completely and re-install it with reboot.

If you deleted Affinity, did you delete just the .app file, – or all related folders within your user Library folder? … I am wondering because it sounds odd if a sandbox error can get fixed with a simple reboot or just an app-reinstallation because Apple's sandbox idea was to increase security within a mac.

(Oh, Wolfenbüttel, – das wäre ja nichtmal was für mal eben mit 9€-Ticket 😉

[Sonnilein]

This was the hint in the referenced article:

In deleted only the application-file, I did not touch the library-folder

 

(Wolfenbüttel ist immer eine Reise wert  da kommt der Jägermeister her .. manchmal begegnet man auch dem "Würger von Wolfenbüttel" .. außerdem spielt nebenan der BTSV jetzt wieder in der 2. Liga - ole ole )