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

macOS Sonoma Startup


MWi

Recommended Posts

Affinity Designer V1 does not start up on macOS Sonoma, MacBook Pro 1998, Intel Chip.

Detailed bug report: 

-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               Affinity Designer [7572]
Path:                  /Applications/Affinity Designer 1.app/Contents/MacOS/Affinity Designer
Identifier:            com.seriflabs.affinitydesigner
Version:               1.10.6 (1.10.22)
App Item ID:           824171161
App External ID:       853519605
Code Type:             X86-64 (Native)
Parent Process:        launchd [1]
User ID:               502

Date/Time:             2023-09-27 09:32:14.5585 +0100
OS Version:            macOS 14.0 (23A344)
Report Version:        12
Bridge OS Version:     8.0 (21P365)
Anonymous UUID:        8A5C2B81-EF51-3C03-47DE-1C06A47F7452

Sleep/Wake UUID:       E674511B-A21E-404D-BAF9-3D0FE4636612

Time Awake Since Boot: 33000 seconds
Time Since Wake:       1560 seconds

System Integrity Protection: enabled

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000

Termination Reason:    Namespace SIGNAL, Code 6 Abort trap: 6
Terminating Process:   Affinity Designer [7572]

Application Specific Information:
abort() called


Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib                0x7ff818c497a6 __pthread_kill + 10
1   libsystem_pthread.dylib               0x7ff818c81f30 pthread_kill + 262
2   libsystem_c.dylib                     0x7ff818ba0a4d abort + 126
3   libc++abi.dylib                       0x7ff818c3ac72 abort_message + 241
4   libc++abi.dylib                       0x7ff818c2ce1a demangling_terminate_handler() + 266
5   libobjc.A.dylib                       0x7ff8188cd36e _objc_terminate() + 96
6   libc++abi.dylib                       0x7ff818c3a0cb std::__terminate(void (*)()) + 6
7   libc++abi.dylib                       0x7ff818c3a086 std::terminate() + 54
8   libdispatch.dylib                     0x7ff818ada5ae _dispatch_client_callout + 28
9   libdispatch.dylib                     0x7ff818adb7cb _dispatch_once_callout + 20
10  libcocoaui                               0x10a40595d +[SchemeManager GetInstance] + 93
11  libcocoaui                               0x10a212508 -[Application initialiseBackend] + 3176
12  libcocoaui                               0x109b95b62 -[ApplicationDelegate applicationWillFinishLaunching:] + 178
13  CoreFoundation                        0x7ff818d527b0 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 137
14  CoreFoundation                        0x7ff818de3436 ___CFXRegistrationPost_block_invoke + 88
15  CoreFoundation                        0x7ff818de3380 _CFXRegistrationPost + 532
16  CoreFoundation                        0x7ff818d226bb _CFXNotificationPost + 682
17  Foundation                            0x7ff819c9f7a7 -[NSNotificationCenter postNotificationName:object:userInfo:] + 82
18  AppKit                                0x7ff81c3548a7 -[NSApplication finishLaunching] + 269
19  AppKit                                0x7ff81c3544d9 -[NSApplication run] + 250
20  AppKit                                0x7ff81c328670 NSApplicationMain + 816
21  dyld                                  0x7ff8188f93a6 start + 1942

Thread 1:
0   libsystem_pthread.dylib               0x7ff818c7db88 start_wqthread + 0

Thread 2:
0   libsystem_pthread.dylib               0x7ff818c7db88 start_wqthread + 0

Thread 3:
0   libsystem_pthread.dylib               0x7ff818c7db88 start_wqthread + 0

Thread 4:
0   libsystem_pthread.dylib               0x7ff818c7db88 start_wqthread + 0

Thread 5:
0   libsystem_pthread.dylib               0x7ff818c7db88 start_wqthread + 0


Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x0000000000000006  rcx: 0x00007ff7b79d8278  rdx: 0x0000000000000000
  rdi: 0x0000000000000103  rsi: 0x0000000000000006  rbp: 0x00007ff7b79d82a0  rsp: 0x00007ff7b79d8278
   r8: 0x00007ff7b79d8140   r9: 0x00007ff7b79d83a0  r10: 0x0000000000000000  r11: 0x0000000000000246
  r12: 0x0000000000000103  r13: 0x0000003000000008  r14: 0x00007ff85c25ae80  r15: 0x0000000000000016
  rip: 0x00007ff818c497a6  rfl: 0x0000000000000246  cr2: 0x000000010f32a000
  
Logical CPU:     0
Error Code:      0x02000148 
Trap Number:     133

 

Link to comment
Share on other sites

  • Staff

Hi MWi,

We are aware of an issue causing our V1 apps to crash on start up when using Sonoma at the moment we can only advise rolling back the update if need to use the Affinity apps. I should hopefully have some more info regarding this soon.

Thanks
C

Please tag me using @ in your reply so I can be sure to respond ASAP.

Link to comment
Share on other sites

  • Staff

Its worth noting that this issue currently only occurs if the app are set to use Light UI rather than the default Dark UI.
Currently pasting "defaults delete com.seriflabs.affinityphoto" into terminal should reset the app to the default Dark UI solving this problem until we release an update however we have found mixed results with this fix internally so it may not work for everyone.

Thanks
C

Please tag me using @ in your reply so I can be sure to respond ASAP.

Link to comment
Share on other sites

1 hour ago, Callum said:

Its worth noting that this issue currently only occurs if the app are set to use Light UI rather than the default Dark UI.

In case it's useful info, I'm able to run 1.10.6 in light mode.

Download a free manual for Publisher 2.4 from this forum - expanded 300-page PDF

My system: Affinity 2.4.0 for macOS Sonoma 14.3.1, MacBook Pro 14" (M1 Pro)

Link to comment
Share on other sites

  • 1 month later...
  • Staff

The issue "[macOS Sonoma] - V1 Changing User interface settings on Intel Mac can crash app and then prevent run up" (REF: AF-481) has been fixed by the developers in internal build "1.10.8.318". The Affinity Store and Mac App Store releases of Affinity v1.10.6 were found to not start when running in light UI. The update to Version 1.10.8 addresses only this specific issue, allowing the V1 range of Affinity software to work on Sonoma in both Light and Dark UI.

This fix is planned for inclusion in the next customer release of Affinity Photo, Publisher and Designer on macOS, 1.10.8 on the Affinity Store and Mac App Store.

This build is not yet available but we are trying to release this fix as soon as possible. When released this build will be announced in the announcements forum.

If you are already experiencing this problem in the Affinity store build, you will need to download the installer from the Downloads section your account on the Affinity Store, as the crash comes before the software can display any available updates.

If you still experience this problem once you are using 1.10.8 version (or later) please reply to this thread including @Serif Info Bot to notify us.

Link to comment
Share on other sites

  • 2 months later...

@Callum, your fix worked perfectly, that was easy. (That's using Terminal, "defaults delete com.seriflabs.affinityphoto" )

A note, folks: don't miss the obvious. Change "photos" to "designer" in the Terminal statement that Callum provided, in order to get that app to sort out. ;-) 

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.