Locating missing resource sometimes fails to relocate all instances

[garrettm30]

When I open a file that has a missing resource, and that missing resource is placed multiple times, if I select the option to relocate the resource, it fixes some of the instances but not all.

I have prepared a pair of demonstration files used in the recipe and video below:

Relink Problem.zip

Recipe

1. Open replace-linked-problem.aftemplate that I provided.
2. At the “Missing Resource(s)” notice, click Yes.
3. Select the provided renamed_file.afpub and click Open.
4. Wait a moment for preflight to update, then consult the preflight errors.

Result: There are several errors of missing resources, but the exact number is different each time. The same file was placed 9 times. Some of the instances of the linked file are fine, while some instances of the same file are still missing.

Demonstration

Environment

This was tested on a 2019 27″ iMac, 3.7 GHz 6-core i5, 24 GB RAM, macOS Ventura 13.6.

Publisher 2.3.0 was used in the demo video, though I know the issue dates back at least as far as 2.1.1. I have an automated workflow that this has affected that used to work properly, but it started to have this issue continuously sometime in the earlier versions of Affinity 2.

[walt.farrell]

First, I'm surprised this works at all.

I have always understood "Yes" in that dialog as allowing you to tell Publisher where the file of that name is located (similar to Update), not to change to using an entirely different file (similar to Replace).

However, I can see that it does allow the user to provide a replacement file of a different name, so thanks for mentioning that

And I can confirm that it works inconsistently, on both Windows and macOS. Good sample files.

[Hangman]

I have to say, I was likewise initially slightly surprised that selecting 'Yes' and choosing an alternative file effectively acts as 'Replace'...

I've tested this with both .afpub and .afdesign template files and I see the same random results with both, they almost but not quite mirror each other in their randomness which leads me to think this may be a memory loading or cache issue, however, having said that, I believe this is perhaps more a Resource Manager error because regardless of what both Resource Manager and subsequently Preflight are showing both the Layers Panel and the files listed in Resource Manager show that the files themselves have been correctly updated (despite the random missing status in Resource Manager).

If the files listed as Missing hadn't been correctly updated then they would appear pixelated on the page but they're not so I think this is simply a case of Resource Manager, vis-à-vis Preflight reporting incorrectly...

[Bit Disappointed]

You're making a bell ring. I often link to other items and I've experienced strange things, but have been too busy to go in-depth and look for a pattern. 

But it sounds very familiar. Also on the iPad Pro.

[Dan C]

Hi garrettm30,

Thanks for your detailed and clear recipe + video. I've been able to reproduce this and have reported this as a bug to be looked into.

Lee

[Affinity Info Bot]

The issue "Locating missing resource on file load incorrectly reports them as missing in pre-flight check." (REF: AF-1471) has been fixed by the developers in internal build "2.4.0.2213".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.

[garrettm30]

I am writing to confirm that the issue appears to be resolved when I follow my original recipe when using Publisher beta 2.4.0 build 2222 on macOS 13.6.