Affinity designer won’t open and crashes on mac

[Shilp]

I have a MacBook Pro late 2011 edition running Mac OS high Sierra . I recently purchased affinity designer after owning the iPad version for years . Right from the first time the app crashes and won’t open  !!! I have attached the crash report . Please help ! 

text.txt

Edited November 30, 2020 by Shilp
Added tags and detail to help get a quick answer since it’s been over 12hrs since I posted

[Shilp]

Bump

[DWright]

Hi @Shilp,

Welcome to the forum

Can you please try opening Affinity Designer while holding down the CTRL key while launching the app. When the Clear User Data window appears, click Select All and then Clear and let me know if the app still crashes..

 

 

 

[Shilp]

I tried holding down the control key and opening it still crashed . I however never got a window asking to clear user data . It just as before gave me a crash report . 

[yslart]

Haing same issues  with Photo.

iMac 2010. Mac OS 10.13.6

[Obi_Jan]

Same here, Designer, Photo, Publisher won't start. Crash-window after 2 seconds, no matter pressing ctrl or not.
Recently updated to HighSierra. All apps are freshly updated as well.

MacbookPro 8,1, OSX 10.13.6

Crashreport enclosed:
_____________________________________________________________________________________

Process:               Affinity Publisher [643]
Path:                  /Applications/Affinity Publisher.app/Contents/MacOS/Affinity Publisher
Identifier:            com.seriflabs.affinitypublisher
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Affinity Publisher [643]
User ID:               501

Date/Time:             2020-12-03 14:43:14.269 +0100
OS Version:            Mac OS X 10.13.6 (17G14042)
Report Version:        12
Anonymous UUID:        983B53BC-A0A6-ABE2-25BF-6DD327B5EE09

Time Awake Since Boot: 500 seconds

System Integrity Protection: enabled

Crashed Thread:        0

Exception Type:        EXC_CRASH (Code Signature Invalid)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY

Termination Reason:    Namespace CODESIGNING, Code 0x1

kernel messages:

VM Regions Near 0 (cr2):
--> 
    __TEXT                 000000010fd50000-000000010fda4000 [  336K] r-x/r-x SM=COW   [(null)]

Thread 0 Crashed:
0   ???                               0x000000011744f19c _dyld_start + 0

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x0000000000000000  rcx: 0x0000000000000000  rdx: 0x0000000000000000
  rdi: 0x0000000000000000  rsi: 0x0000000000000000  rbp: 0x0000000000000000  rsp: 0x00007ffedfeafbe8
   r8: 0x0000000000000000   r9: 0x0000000000000000  r10: 0x0000000000000000  r11: 0x0000000000000000
  r12: 0x0000000000000000  r13: 0x0000000000000000  r14: 0x0000000000000000  r15: 0x0000000000000000
  rip: 0x000000011744f19c  rfl: 0x0000000000000200  cr2: 0x0000000000000000
  
Logical CPU:     0
Error Code:      0x00000000
Trap Number:     0

Binary Images:
       0x10fd50000 -        0x10fda3fff +??? (???) <D85CDEBF-225A-3623-BBE5-06629C573717> (null)
       0x11744e000 -        0x117498adf +??? (551.5) <CB9BFB56-4511-36F1-A546-891FF770C01C> (null)

External Modification Summary:
  Calls made by other processes targeting this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by this process:
    task_for_pid: 0
    thread_create: 0
    thread_set_state: 0
  Calls made by all processes on this machine:
    task_for_pid: 348
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=940K resident=0K(0%) swapped_out_or_unallocated=940K(100%)
Writable regions: Total=8420K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8420K(100%)
 
                                VIRTUAL   REGION 
REGION TYPE                        SIZE    COUNT (non-coalesced) 
===========                     =======  ======= 
STACK GUARD                       56.0M        2 
Stack                             8192K        2 
__DATA                             288K        5 
__LINKEDIT                         316K        4 
__TEXT                             636K        3 
shared memory                        8K        3 
===========                     =======  ======= 
TOTAL                             65.2M       13 

Model: MacBookPro8,1, BootROM 87.0.0.0.0, 2 processors, Intel Core i5, 2,4 GHz, 8 GB, SMC 1.68f99
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In
Memory Module: BANK 0/DIMM0, 4 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3431554638424455352D474E2D4620
Memory Module: BANK 1/DIMM0, 4 GB, DDR3, 1600 MHz, 0x02FE, 0x45424A3431554638424455352D474E2D4620
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.102.30)
Bluetooth: Version 6.0.7f22, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Samsung SSD 850 EVO 250GB, 250,06 GB
Serial ATA Device: MATSHITADVD-R   UJ-8A8
USB Device: USB 2.0 Bus
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: IR Receiver
Thunderbolt Bus: MacBook Pro, Apple Inc., 22.1
 

[gthomas]

Same problem here. Running Monterrey 12.2.1. on 2019 MBP. Designer won't even open. Just the endless spinning beachball of death. I've tried restarting Mac. Deleting and re-installing Designer. And the suggestion from DWhite above. First time I tried it, nothing happened. Second time I tried it, I got the option to clear user data, tried that, and Designer opened...and then the spinning beachball of death returned.

Updated Mac to Monterrey 12.3. It made no difference.