Jump to content
You must now use your email address to sign in [click for more info] ×

Recommended Posts

  • Staff

Hi jaxfh,

I've passed this on to development to look into and they've requested a copy of your cs.json file. Could you navigate to ~/Library/Group Containers/6LVTQB9699.com.seriflabs.beta/v2/ and attach 'cs.json' please?

Link to comment
Share on other sites

6 minutes ago, Sean P said:

Hi jaxfh,

It looks like it might be something in the Welcome Screen/My Account dialog that is causing the app to crash. I'll pass the reports on to development for a closer look. In the meantime could you try the following for me please:

Open up Terminal, paste the relevant command from below and run it. It will disable the Welcome Screen/My Accoutn from appearing as though you had unticked the option. I'm just curious to see if this gets you up and running!

Photo Beta:

defaults write com.seriflabs.affinityphoto2.beta com.seriflabs.ShowNewDocumentOnStartUp 0

Designer Beta:

defaults write com.seriflabs.affinitydesigner2.beta com.seriflabs.ShowNewDocumentOnStartUp 0

Publisher Beta:

defaults write com.seriflabs.affinitypublisher2.beta com.seriflabs.ShowNewDocumentOnStartUp 0

 

Still Crashing. 

Designer.txt Photo.txt Publisher.txt cs.json.zip

Link to comment
Share on other sites

7 minutes ago, Sean P said:

Thanks for that!

If you delete that file, can you see if the apps then run up correctly for you? It'll regenerate itself correctly - it looks to be missing all its contents!

Yes, the apps are starting normaly, even if i put the Terminal Things to 1 again

Link to comment
Share on other sites

  • Staff
Just now, jaxfh said:

Yes, the apps are starting normaly, even if i put the Terminal Things to 1 again

Thats great to hear! I've logged the issue with development. I've removed the post regarding the Terminal commands as it was in a different area than I suspected.

Link to comment
Share on other sites

  • Staff

The issue "App crashes on launch if cs.json is empty" (REF: AF-2879) has been fixed by the developers in internal build "2.5.0.2430".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer 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 @Affinity Info Bot to notify us.

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.