Lennypenny Posted January 19, 2022 Posted January 19, 2022 Hi! Everytime I close Publisher I get the error 'Affinity Publisher stopped unexpectedly', whilst Publisher just closes fine (I closed it manually) and al files are saved and such. When you guys need a crash report, let me know! Quote
Dan C Posted January 20, 2022 Posted January 20, 2022 Hi @Lennypenny, Thanks for your report, this is certainly a strange issue! Can you please confirm for me: What version of Publisher is installed? What version of macOS are you running? Does this happen every time you close the app, or only certain times? Do you close all documents before closing the app, or are you also closing documents in the same process? 20 hours ago, Lennypenny said: When you guys need a crash report, let me know! Crash reports would certainly be useful please If you create a new, blank document then close the app shortly after, do you see the same crash? What about if you open an existing document, but make no changes and then close the app - does this still crash? Many thanks in advance! Quote
Lennypenny Posted January 21, 2022 Author Posted January 21, 2022 22 hours ago, Dan C said: Hi @Lennypenny, Thanks for your report, this is certainly a strange issue! Can you please confirm for me: What version of Publisher is installed? What version of macOS are you running? Does this happen every time you close the app, or only certain times? Do you close all documents before closing the app, or are you also closing documents in the same process? Crash reports would certainly be useful please If you create a new, blank document then close the app shortly after, do you see the same crash? What about if you open an existing document, but make no changes and then close the app - does this still crash? Many thanks in advance! Hi Dan C, Can I send you guys the crash report via PM? Don't feel comfortable sharing the report online, lot of information in there. The error only pops up when I have a document open in Publisher, and then close Publisher. When Publisher is 'empty', it closes just fine. Using Publisher 1.10.4 on a Apple M1 Pro MacBook, MacOS 12.0.1. Quote
Dan C Posted January 21, 2022 Posted January 21, 2022 I certainly understand, you can upload the crash log to the below link (which only Affinity staff can access. Can you also please provide a sample of an .afpub file that you would have open at the time of the crash? - https://www.dropbox.com/request/RfZRtOJWEomiXiqgPuVT Once uploaded, please reply here to let me know Quote
Lennypenny Posted January 24, 2022 Author Posted January 24, 2022 On 1/21/2022 at 6:06 PM, Dan C said: I certainly understand, you can upload the crash log to the below link (which only Affinity staff can access. Can you also please provide a sample of an .afpub file that you would have open at the time of the crash? - https://www.dropbox.com/request/RfZRtOJWEomiXiqgPuVT Once uploaded, please reply here to let me know Hi Dan C, Just uploaded the log and a .afpub file to your Dropboxlink! Quote
Dan C Posted January 25, 2022 Posted January 25, 2022 Many thanks for your files provided! I've been testing this internally and thus far I've been unable to replicate the crashing behaviour - however I can see from your crash report that this appears to be due to an error accessing one of your installed dictionaries. Can you please confirm for me: Under System Preferences > Date and Time - what is set for your region? Under Keyboard > Text > Spelling (dropdown menu) > Set Up... - which options are checked please? (a screenshot will suffice) Do you have any custom dictionaries installed under ~/Library/Spelling? Many thanks once again Quote
Lennypenny Posted January 26, 2022 Author Posted January 26, 2022 18 hours ago, Dan C said: Many thanks for your files provided! I've been testing this internally and thus far I've been unable to replicate the crashing behaviour - however I can see from your crash report that this appears to be due to an error accessing one of your installed dictionaries. Can you please confirm for me: Under System Preferences > Date and Time - what is set for your region? Under Keyboard > Text > Spelling (dropdown menu) > Set Up... - which options are checked please? (a screenshot will suffice) Do you have any custom dictionaries installed under ~/Library/Spelling? Many thanks once again - My timezone is set to 'Midden-Europese standaardtijd', 'Amsterdam- The Netherlands' - See attached files - Yes, I've installed a custom one; nl_NL from Github, also took a screenshot of this Quote
Dan C Posted January 26, 2022 Posted January 26, 2022 Many thanks for providing this for me! I've replicated your setup here, using the ln_NL files from the LibreOffice GitHub page and I'm still not seeing this crashing - though this may be due to the fonts being used in your document are 'missing' for me, or the dictionary files you have installed manually are different. Therefore can you please: Upload a copy of the font files in use to the above Dropbox link (specifically the AlwynNewRounded fonts) Copy the nl_NL folder from the Library > Spelling folder and paste this on your desktop, then remove the folder from Library > Spelling. You should find that Publisher is still able to spellcheck in this language, even without this folder in Spelling due to your macOS settings. With this folder on your desktop, does the app still crash when closing? Quote
Lennypenny Posted January 31, 2022 Author Posted January 31, 2022 Hi Dan C, It seems that I've located the problem. When I remove te nl_NL folder from the spelling folder, the crash report doesn't appear en everything seems ok. I recently added that language because hyphenation function didn't work properly in my native language. Hyphenation still doesn't work properly, but adding/deleting that folder doesn't seem to make any difference:). Quote
Dan C Posted January 31, 2022 Posted January 31, 2022 Many thanks for letting me know! Are you able to upload a copy of this folder to the below link for me? I'd like to try testing this here to see if I can replicate the crashing. https://www.dropbox.com/request/RfZRtOJWEomiXiqgPuVT If you replace the files in this folder with the 3 files attached here, does this a) stop the crashing and b) fix your hyphenation dictionary issue? hyph_nl_NL.dic nl_NL.dic nl_NL.aff Quote
RM f/g Posted January 31, 2022 Posted January 31, 2022 Looks like what I experienced. One of the dictionary files hadn't been downloaded correctly and appeared to be a html file instead of a text file. Dan C 1 Quote Macbook Pro mid 2015, 16 GB, double barrel: MacOS Mojave + Affinity 1 (+ Adobe’s CS6)/ MacOS Monterey + Affinity 2
Lennypenny Posted February 2, 2022 Author Posted February 2, 2022 On 1/31/2022 at 2:08 PM, RM f/g said: Looks like what I experienced. One of the dictionary files hadn't been downloaded correctly and appeared to be a html file instead of a text file. Thanks for pointing out! I've just found out that removing the nl_NL files doesn't seem to inflect the auto-hyphenation function: hyphenation works fine now.. Quote
Lennypenny Posted February 2, 2022 Author Posted February 2, 2022 @Dan CIt seems that my hyphenation 'problem' is solved now, if I use any other font than Alwyn New Rounded, the auto-hyphenation function works just fine. Could this mean that the font is conflicting with Publisher instead of the nl_NL dictionary? Quote
Dan C Posted February 2, 2022 Posted February 2, 2022 Thanks for confirming that for me! There should certainly be no issues with this font and auto-hyphenation. On my Mac I have enabled Netherlands spelling through System Preferences > Keyboard > Text and enabled this font through Adobe Fonts. Using Filler Text in the document, I ensured the Language & Hyphenation Language set for the text frame in the Character Studio are set to Netherlands, and Auto-Hyphenation is enabled in the Paragraph Studio, with this font set for this text. As can be seen, hyphenation appears to be working as expected for me: However I do note that the font used in the sample document previously provided to me has a slightly different name from the Adobe font I have installed - so this may be due to the font file itself in use. Do you recall where this font was obtained from? Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.