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

Search the Community

Showing results for tags 'AF-481'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.4 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start



Website URL



Member Title

Found 8 results

  1. The great many of us who like to use Separated Mode were told to stick to Designer V1. With the macOS 14 Sonoma update, V1 no longer works, so this option has now evaporated. I know I am far from alone in preferring to work in separated mode - to the point that I am considering abandoning Designer. Is there any plan to bring separated mode back? Can there PLEASE be an V2 update with this function restored?
  2. Following the release of macOS Sonoma, our team have identified an issue whereby the Affinity V1 apps will crash on launch, if the UI style is set to Light UI for Intel / Rosetta based macs. In order to resolve this crashing issue, you will need to reset the Affinity V1 app to default settings. To do this, please open Applications > Utilities > Terminal. In the Terminal window that opens, type the following and hit Enter, depending on the Affinity app you are using: Photo - defaults delete com.seriflabs.affinityphoto Designer - defaults delete com.seriflabs.affinitydesigner Publisher - defaults delete com.seriflabs.affinitypublisher Some users may receive a 'Domain not found' error when using the above Terminal command. If this occurs, you will also need to manually delete a file through Finder. Please open Finder and navigate to the following location: ~/Library/Preferences Within this folder, please locate the below files and delete these, for each app that is crashing: Photo - com.seriflabs.affinityphoto.plist Designer - com.seriflabs.affinitydesigner.plist Publisher - com.seriflabs.affinitypublisher.plist This should reset the app to default settings, using the Dark UI style, and should stop the app from crashing when launched. Our team are aware of this problem and are investigating further. If you have any issues resetting the app, or if the crash continues to occur after following these steps, please create a New Thread and our team will be happy to assist!
  3. Hello, I've recently updated my MacBook to the new OS 14 Sonoma and now my Affinity Designer V1 will no longer open. Is this an issue other people are having or has V1 already stopped receiving support updates for new software??? Please advise, Thank you.
  4. 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
  5. Hi there, I've just upgraded to Sonoma 14.0 and Affinity Publisher just cannot open. Every time when I try to launch it, just crashes. What is going on and is there a way to be resolved? I have a digital products business which is completely based on the use of Publisher and all my work is just stuck now. I see here and there in the forum that Publisher is not prepared to work with Sonoma, but if (I hope not) is true then there had to be some announcement! 😑
  6. All my Affinity Programs keep quitting on opening them. I recently changed my OS to Sonoma. Can you help?
  7. My Affinity 1.10.6 does not work on my MacBook running Mac OS Sonoma. It crashes every time when loading the App. For those interested crash report attached Anyone on here successfully running Photo 2 ?? photo1.10.6 Crash report.pdf
  8. Hi there, I still have Affinity Photo V1. I hadn't updated it in a while. After I upgraded to MacOS Sonoma, the app crashes when I open it. It won't go past the splash screen. The app version I am using is 1.10.6. Is there a newer version I could download?
  • 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.