Big problem with Publisher

[notabene34]

Hello, We again have a very big problem with the affinity publisher crash when opening a document. We attach the file in question as well as the crash report. For information we are working on macOsX 13.0.1 with an iMac M1, 2001 We save this file to a folder shared on Dropbox with our customer. However, when our client makes even minimal changes to the file, we can no longer open it. Our customer is working on a MacBook Pro running macOsx Catalina 10.15.7 Fortunately, the file in question is not too complicated to redo, but what about a very important file of several hundred pages??? We had already had a problem with the inability to open a file and Affinity publisher who told us that this file had been created with a later version when this was not the case. We don't know if this bug has been fixed. We are increasingly in doubt about the reliability of this program and it reminds us of very bad memories about some versions of QuarkExpress that crashed several times a day. (the oldest will understand what we mean! ...) Can someone open this file? Does anyone have an idea about this bug? Thank you for your help.

06- Quelque chose sauvegarde.afpub report crash affinity publisher.rtf

[notabene34]

sorry our Mac is à iMac M1, 2021

[notabene34]

And Sorry is is not the good file, here is the good file

05- Quelque chose.afpub

[MikeTO]

Hi @notabene34 I tried to open this on my M1 Pro with Ventura 13.2 and got the same results as you - Affinity immediately crashed.

Sometimes if a document gives a warning about the document being corrupted you can create a new document and add pages from the corrupted file to recover the document, but this one doesn't give any chance to open it. 😞 

[Catshill]

It opens on my Windows 10 system. I've saved it and uploaded it.

06- Quelque chose sauvegarde V2.afpub

[notabene34]

ok but it's the wrong files. try to open the second file : 05-quelque chose.afpub

[notabene34]

Thank you for your feedback which will surely allow us to move forward on this bug.Wee also managed to open the file with the IPAD version.

[notabene34]

File reopened with ipad version and resaved still can't open afterwards with Mac version

[notabene34]

here is the report crash when opening the iPad version on Mac version

report crash version IPAD affinity publisher.rtf

[Old Bruce]

I am going to guess it is down to one of the missing fonts that show up on my Mac.

I replaced the Helvetica Neue LT Std with the Mac OS supplied Helvetica Neue. There could well be a conflict if you have both the Neue LT Std and the Mac version on the same machine. I have no idea of what Desyrel is so I used Arial.

here is the Mac version of the fonts saved as

saved as 06- Quelque chose sauvegarde V2.afpub

[notabene34]

Please try to open 05-Quelque chose.afpub

[Twolane]

I was able to open your 05-quelque chose no problem with 2.04 on a laptop. Some fonts were missing, but to be expected.

[Komatös]

On the first page there is an empty layer (calque1). I have deleted this layer. Maybe this is the culprit.

05- Quelque chose with deleted calque1.afpub

[Old Bruce]

2 hours ago, notabene34 said:

Please try to open 05-Quelque chose.afpub

Okay, that file crashes immediately. Doesn't seem to matter how I try to open it. Or using the Add Pages from File... I even tried using Publisher version 1 and all I saw there was the "File includes features from a later version of Publisher" notice.

[notabene34]

Il y a 2 heures, Twolane a déclaré :

J'ai pu ouvrir votre 05-quelque a choisi aucun problème avec 2.04 sur un ordinateur portable. Certaines polices manquaient, mais il fallait s'y attendre.

Oui évidemment les polices manquantes sont inévitables. C'est un bug qui fait vraiment peur... Que dire si mon fichier faisait plusieurs centaines de pages et plusieurs semaines de travail.... sans oublier le client que je perdrais sûrement à cause des délais....

[notabene34]

2 hours ago, Twolane said:

I was able to open your 05-quelque chose no problem with 2.04 on a laptop. Some fonts were missing, but to be expected.

Très étonnant ce bug....

[notabene34]

2 hours ago, N.P.M. said:

Loads normal on a wee old laptop.
Perhaps the used idml file is corrupted
And preflight throws several missing resource messages.
Also the Adobe Caslon Pro are adobe fonts and are probably activated through adobe cloud and not installed versions 

Hello what's the IDLM ? it's for inDesign isn' it ? no for publisher

[walt.farrell]

7 minutes ago, notabene34 said:

Hello what's the IDLM ? it's for inDesign isn' it ? no for publisher

Publisher can import IDML files, but sometimes if you start with an IDML file there are unexpected issues with it. These may be due to errors in the import process, or differences in how some things are handled between InDesign and Publisher.

[notabene34]

1 hour ago, walt.farrell said:

Publisher can import IDML files, but sometimes if you start with an IDML file there are unexpected issues with it. These may be due to errors in the import process, or differences in how some things are handled between InDesign and Publisher.

NO, this files is an original publisher.

[Callum]

I have logged this file with our developers to be investigated further. I'll let you know if I have any updates.

[Callum]

This appears to have been caused by resources within the file being linked to a DropBox location. I have attached a fixed version of your file please could you try opening it for me?

05- Quelque chose-noresource.afpub

[notabene34]

Hello and thank you
indeed the "noresource" version works correctly. But there are no more pictures on the cover
Can you preemptively explain the bug more clearly? Will I be notified of a publisher release that fixes this bug? And finally, is the problem only related to Dropbox, or can it also occur with a file stored on Icloud? What is curious if it is related to Dropox is that the buggy file opens with the Ipad version.

[Affinity Info Bot]

The cause of the issue "Attached file crashes Publisher on open" (REF: AFB-7285) has now been fixed by the developers.
This fix is included in build 2.1.0.1709 (or later) which is already available as a customer beta and will be included in the next 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.