Publisher beta - closing down

[cctheatre]

I am using the latest version on windows and when I open a specific file the whole program closes down - I can open an A5 2 page document but when I try to open one with about 30 pages it just closes down

[JFisher]

Hi cctheatre,

Could you provide the file so I can take a look? You can upload it here. 

[cctheatre]

35 minutes ago, JFisher said:

Hi cctheatre,

Could you provide the file so I can take a look? You can upload it here. 

Done - Thank you

[cctheatre]

Any luck with identifying the problem?

On 2/15/2019 at 11:54 AM, cctheatre said:

Done - Thank you

 

[JFisher]

Sorry for the delay getting back to you @cctheatre

Your file has been passed over to our developers for further investigation. 

[Franky Drappier]

Windows 10 Pro Beta version 249.Experiencing quite a few crashes (program shutting down), especially when switching pages or scrolling through the document. 

This happened with a 32 page document but also with a 12 page document. Both documents contain a lot of pictures - Embedded in the 32 page, Linked in the 12 page.

[cctheatre]

On 2/26/2019 at 2:30 PM, JFisher said:

Sorry for the delay getting back to you @cctheatre

Your file has been passed over to our developers for further investigation. 

Hi - any idea how long it takes to get back to someone? It's been 3 and half weeks...

[Move Along People]

-

[cctheatre]

7 minutes ago, haakoo said:

Did you update to the latest beta version?
Maybe it will work as intended and make sure to reset the program (ctrl+ clicking the program icon)

Hi - yes I tried it yesterday and today and just tried the ctrl+ too but still the same

[cctheatre]

Hi Affinity - not heard back re this - any luck finding the reason it keeps crashing when I open the file? I'm using windows and have updated the software - makes me reluctant to try new files until this is sorted

[Jon P]

Hi cctheatre,

Apologies we never got back to you.

The file was logged and was slightly corrupted (due to a previous bug), we believe the bugs that lead to this happening are all dealt with now, so if you were to start a new file I would be very surprised if you encounter this issue again (if you do, we would love to know what steps you took with the file before it started happening).

I've asked the developers if they can fix the file and get it back to you, but it might take a bit of time to do this (if it is possible), i'll let you know.

Apologies for the inconvenience.

Thanks