[crash when opening a file created with an older version of Publisher.]

6 hours ago, Dan C said:

Do let us know how you get on here!

The beta did the trick beautifully! Was able to open the file and get what I needed from it. Thanks, @Dan C!

[crash when opening a file created with an older version of Publisher.]

Hi, folks!

I believe I'm having the same issue @arginus reported – my system generates a crash report and when I opt to relaunch the app, I see a terminal window show up and it prints the same text:

2021-09-20 20:39:24.961 Affinity Publisher[26583:12545989] CoreText note: Client requested name ".SFNS-RegularItalic", it will get Times-Roman rather than the intended font. All system UI font access should be through proper APIs such as CTFontCreateUIFontForLanguage() or +[NSFont systemFontOfSize:].
2021-09-20 20:39:24.961 Affinity Publisher[26583:12545989] CoreText note: Set a breakpoint on CTFontLogSystemFontNameRequest to debug.
2021-09-20 20:39:29.070 Affinity Publisher[26583:12545989] *** WARNING: Method convertPointToBase: in class NSView is deprecated on 10.7 and later. It should not be used in new applications.

If I then try to open the old file I'm trying to access, the system prints a segfault and quits again (prints `Segmentation fault: 11` on the terminal)...

@Dan C mentioned re-linking the files and then saving in v1.10 should fix the problem; but I seem to be missing something here. Since the app crashes, I cannot relink with the resource manager. Arguably, if I remembered the paths and filenames I had (assuming they changed), then I might be able to put the files back – but I don't have this information.

Is there some other way I am overlooking, such that I can fix this locally? Say, to force the system to break the links if needed and continue to open the file? Do I need to roll back my version of Publisher to address this, then re-update my installation?

If not, it sounds like I might just have to  wait till the next update/beta...

Thanks in advance!