Jump to content

Recommended Posts

I'm using build 305. I have a book layout project I'm working on – mainly text, about 20 images to date – that has been working beautifully to date. Very few problems at all. However, all of a sudden I cannot save the file without the application crashing. The problem seems to be restricted to the one file – previously saved versions and other projects are working okay. But on this one I can't even open the file, make a very minor change and save it again without a crash. I tried deleting the application and reinstalling a fresh download but the problem remains.

The file is currently 29.3MB and about 200 pages (though about 60 of those are still blank), which I wouldn't have thought was huge. 

Would really appreciate a fix to this asap. While I know we can't rely on the beta for production projects the app has been working so well to date that I've gone a fair way with this project with the intention of using it.

Share this post


Link to post
Share on other sites

Reminds me of a similar problem someone had in the past.

Do you have save history set for the document?

If yes, open the document and switch it off.

If no, can you upload the document or if private you can send it to the Devs/Support privately.


Due to the fact that Boris Johnson is now our Prime Minister, punctuation, spelling and grammar will never be worried about ever again.  We now have far bigger problems to be concerned about.

Share this post


Link to post
Share on other sites

Ended up going back to a slightly earlier version and rebuilding from there and it seemed to work, but now have struck the same problem after more work on the project. I will send it to support. Thanks for the tip on turning on the history save.

Share this post


Link to post
Share on other sites

I'd prefer not to upload the offending file publicly. Where can I send the file directly to the developers?

 

Share this post


Link to post
Share on other sites
2 hours ago, djb21au said:

I'd prefer not to upload the offending file publicly. Where can I send the file directly to the developers?

 

You'll have to wait for them to rise and shine for a new day, it was the middle of the night there when you asked your question.


MacBook Pro (13-inch, Mid 2012) Mac OS 10.12.6 || Mac Pro (Late 2013) Mac OS 10.14.5

Affinity Designer 1.7.2 | Affinity Photo 1.7.2 | Affinity Publisher 1.7.2 | Affinity Designer Beta 1.7.2.2 | Affinity Photo Beta 1.7.2.151 | Affinity Publisher Beta 1.7.2.458

Share this post


Link to post
Share on other sites

Yes, figured I was probably in the wrong time zone :)

Unfortunately I'm now having multiple and frequent crashes and really can't do any meaningful work on my project until (hopefully) the source of them is identified. For the record, attached is a crash report in case it helps the devs or anyone else.

APu crash report.rtf

Share this post


Link to post
Share on other sites

For the record, I ultimately worked around this (hopefully temporary) issue by building my project (a 250 page book) in three parts. I haven't had any issues with saving the resulting smaller files, leading me to conclude that the instability I experienced is related to larger files. This obviously required some extra effort with the table of contents and the need to export the files separately and then merge them, but no big deal – a small compromise for being able to use the beta. Bottom line is I've had a good experience with APu even in its beta version with very few glitches.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×