macmclaw

Wouldn't it be desirable if you could communicate with your customers directly via the customer account in the Affinity programs. In this way, customers could be taken directly to a forum page even in the event of program errors. Customers get the feeling that you care.

Have you tried clearing the user data (CTRL key when starting the software, select all, then clear / reset, see screenshot) to give it a fresh start? There might be some things hanging around from a previous beta or installation that give the software a hiccup.

Where can I detect the build no. in the retail versions on mac? – While it is shown for Betas in their "About" info the retail versions don't show the build after x.x.x (1.7.3) and not in the forums list of the most current versions. Also the build no for win and mac versions don't have to be identical, right?

Perhaps I've been too close to finding solutions. Did not realize, but see that Publisher is now on the app store. I have 1.7.3 official release version (from website) and 1.7.3.475 beta build. It's the beta build I've been working with (well, trying to get it to work), but just now updated my 1.7.2 original official release. It also crashes.

Is the app store version any different than the official San Serif web release or the beta builds? 

Trying to limit screen time. Vision improved, eye muscles an issue. Thought about Siri, decided not.

Anyway, busy weekend with EtreCheck and taking care of minor issues it pointed out. Bottom line is this, Still crashing. Attaching EtreCheck Report, Crash Report and Publisher file.

Thought I had a solution and was elated when I removed all Adobe garbage left over. Upon restart, I was able to open Publisher, create a new document and a new paragraph style. No Crash at this point. Closed file, reopened and tried to create a new paragraph style...Boom! Crash!

Attached files are for developers to let you know I'm doing my part to investigate on this end. Worthy to mention that Pauls suggestion to creating a new user profile did meet with success. There were no crashes. Have to admit, didn't like the consequences of having to set up my user account all over, so haven't tried that suggestion lately. 
Amazing in and of itself I was able to save a document. New style (Folio) was created on master pages. Attempt to create a second paragraph style took me back to the drawing board.

Sorry for multiple posts and repeated queries...just trying to solve a mystery. Thanks to all.
iMac 2019-09-30.etrecheck
Affinity Publisher Beta_2019-09-30-175545_iMacUp.crash
Bios and Farewells.afpub

Thomaso, thanks for clearing up the German thread. I gave it the ole college try. Thanks also for your assessment of Dr. Cleaner. It's been good, but I have been increasingly wary of it, especially since it's removal from the app store. Will look into AppCleaner as you suggested.
When I went to Mojave, I did a clean install, everything has been looking good. Your other recommendation, using EtreCheck, is wonderful. It has helped to identify some culprits, but also confirms that I'm in pretty decent shape. Right now, I am quite clean so that is why Dr. Cleaner Pro is beginning to raise my eyebrows.
Wearing my wife's store bought cheaters to read the screen, so taking it slow.  I'm hopeful we're getting close. 

Can't follow the language in last posts, mac and thomaso. Etrecheck I'm running is 5.3.3 from App Store. Purchased advertised 'user package.' Many thanks, wonderful program to analyze the mac. As mentioned, not following last posts...never graduated past English!! 

On a side note, additional to not reading the posts, healing from cataract surgery and reading the screen is equally troublesome! Working through that.

After running Etrecheck and looking at the report, found a few stragglers of old programs, plus some 32-bit apps that will have to go sooner or later. Cleaned things up. As I'm narrowing down, Dr. Cleaner Pro, 3rd party app, may be suspect. Have either one of you installed that app?

Oje, das klingt nach einer 'korrupten' Einstellungsdatei, von welchem Programm auch immer. Dazu fallen mir nur Standards ein:
– NVRAM zurücksetzen (cmd+option+R+P on boot).
– Einmal im Safe Boot Mode starten (shift on boot), um dabei ungewollte Prozesse zu verhindern und automatisch die Dateistruktur prüfen zu lassen.
– Ins Terminal tippen: "sudo languagesetup" (ohne " "), du bekommst eine Auswahlliste von ca. 35 Sprachen gezeigt, mit "q" beendest du das ohne Änderung.

Well that's some good news - I'll add that info to the bug report. As to what's causing it is hard to pin down unless we can ever replaicate that issue here. I still suspect some software influence having seen the crash report.

Created new admin user account and putting the latest beta build through some motions. Feels strange not having a crash. I would agree with you about the software influence. If not an actual installed app, perhaps a remnant in a plist. 

For now, holding off on switching user accounts. Copying library folders will copy the original crash problem. When the developers get the bug report, it might spark something.
   

To possibly detect a culprit you could run https://etrecheck.com/  It creates a diagnose list with apps, daemons, kernels, agents or processes that might disturb. Once it finished its diagnose you can jump to the "Report" view in the sidebar bottom to see if any strange item is mentioned. That info might help you to remove those. The Etrecheck.app itself doesn't do anything else than diagnose.
The last free version was 3.4.6 from 2017 and is still available here: https://www.techspot.com/downloads/7028-etrecheck.html

Well, I'll be. Pauls, you have something. 
Created a new user account on the mac. Yikes, had to validate the Publisher Beta, but found my activation key and she opened fine. I should also mention I am using the 1.7.3.475 beta build.
Purposely, went through the same routine of creating a new document preset, then, on master pages, created a new paragraph style - with all the same parameters as before.

NO CRASH!

Can you explain why my user account appears to be out of whack enough to crash Publisher? Absolutely no other problems, with Affinity Photo or any other app. How would you recommend I proceed.

Pauls, this is a most incredible development. You need to speak with the developers!

Not knowing whether you mention your Onyx installation as a possible reason for your initial bug report - or in the sake to solve it, this article can be useful:
https://discussions.apple.com/thread/6455117
Though the text was published in 2014 its basic idea not to influence the macOS built-in self-cleaning and/or security processes with additional, possibly conflicting tools, becomes with any macOS upgrade rather more valid than redundant. Especially "play around with that" does not sound healthy by default

I would consider any unusual graphics/User interface/system applications first.

Hello,
Indeed, working on another account, it works without problems.
What do you recommend? My account has a lot of settings ...
cordially
Bonjour,
Effectivement, le travaillant sur un autre compte, ça marche sans problème.
Que me conseillez-vous? Mon compte a beaucoup de réglages …
Cordialement
 

Hello, I'm on Mac and Windows ...
On Mac, I have the same crash problem with Affinity Publisher. I can enter the style menu to create one, but can not save or leave, it crashes immediately and Publisher leaves ...
On Windows, I do not have the same problem.
 
Bonjour, je suis sur Mac et Windows…
Sur Mac, j'ai le même problème de crashe avec Affinity Publisher. je peux rentrer dans le menu des styles pour en créer un, mais impossible d'enregistrer ou de quitter, ça plante tout de suite et Publisher quitte…
Sous Windows, je n'ai pas le même problème.
C'est vraiment très gênant!
Rapport d erreur Affinity publisher mac styles plantent.txt

I'd be surprised if it's a third party font specifically that's causing it, but it could be the case. It would be nice to find out what is in common with both of yours setups that means you can constantly reproduce this crash when creating a text style, things like third party apps and so forth, although we've already been through "cleaning" out these with Wolf and not had any luck in preventing it happening yet.
@macmclaw Can you post some of the crash reports being generated when this happens?

Wish I could help Mac, but I'm still crashing. Fonts have been cleaned up and streamlined, at least Font Book is happy. Removed all extra fonts and went back to system fonts, plus two additional OpenType fonts. The fonts are a combination of TrueType, OpenType, OpenType Postscript.

Other than that, stymied as to what else, even minor, could be causing the crashes.

I'm following the beta notifications and have the latest beta build installed (1.7.2.458) Same crash results. 

All I can tell you is they have logged my issue with the developers and from reading the forums, they are quite gainfully employed with the many other fixes. Hoping something will reveal itself soon.  I'm left-handed and have an open mind.