Jump to content

Search the Community

Showing results for tags 'afd-3554'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 8 results

  1. Hi, using AD 1.7.1 version, when I want to export with any extention in the file name and destination window, I press save and the program freezes and stop responding. Any idea to solve this please?
  2. Hi, a weird glitch seems to have occured after updating to AP 1.7.0. Was able to export exactly one image but after a few changes and attempting to resave/export it just brings up the save screen but save functionality completely crashes. The background program still works but the save screen floats on top of everything and can't be cancelled or removed. Only option is to force quit Affinity. Have tried reinstalling it a few times / mac on and off a few times. No luck. Seems to work ok on El Capitan. Program is useless if I can't save. Any suggestions?
  3. Hi, I have been using Affinity Designer 1.7 and have the following issue so far, that occur sometimes, not sure if it is due to computer I use or if others are experiencing same issue:Sometimes Affinity Designer 1.7 crashes during export process, like I click export as PDF, then it crashes. I export first time as PDF then go through export process immediatly afterwards to export as JPEG, or the other way round, JPEG then PDF, it then crashes as specified during process. I use Affinity Designer 1.7 on a 21.5 inch iMac from late 2015 with OS 10.14.5 Mojave. Apple asks if I want to send crash report after Affinity Designer 1.7 crashes, and I click yes, so that may be passed onto Affinity Designer Serif. I can still use the software, it is just a bit of a hassle to have to have it randomly crash when exporting. You can see attachment shows the type of images I am working on when these two issues have occured. May it be resolved.
  4. If I do a Save as... with same .afpub name then the app crashes in most situations. I am able to repeat this with only a new document opened, too. (p.s.: didn't act like that in previous betas)
  5. I discovered the newly updated version of Affinity Photo today, when trying to export a PDF file for the printers. The program gets stuck every time I click on 'save' and I have to force quit. Hasn't happened to me before, perhaps a bug in the new release? Any help gratefully received!! Thanks so much!
  6. I just updated Affinity Designer to version 1.7.0 on my Mac (High Sierra). Now whenever I try to export a png file, the program freezes after I click save (and does not save the file). I then can only close the program by 'Force Quit' via Activity Monitor. (video of the problem is attached). AffinityDesigner problem.mov
  7. Hi Guys, I cannot export a file nor can I save any content because the dialog box clears, but does not save or export. I have attached a screenshot of what happens when I try to save or export (I get this and nothing happens). I am running 1.7.0 Affinity on MacOS 10.12.6. Any help? Stan
  8. Having a simple document and trying to export it as PNG file: (1) Selecting "File > Export..." from the menu and Export Window opens (2) Selecting "PNG" and clicking the "Export" button… (3) a Mac OS X "Save As" panel opens (4) I click "Save" in this panel (5) a new Window opens "Confirm access to export folder" (6) I click the "Confirm" button (7) error alert pops up that it couldn't save/export the file. I'm not entirely sure what triggers it. It failed 3 times like that in a row, but then suddenly started working normally (w/o the strange confirm access window). This is on a Yosemite machine (with all the "latest" updates: 10.10.5 (14F2511)). System Log reported this: 05/06/19 6:23:00,679 PM com.apple.appkit.xpc.openAndSavePanelService[51214]: *** Assertion failure in -[NSOpenPanelServicePanel _reactToPanelDismissalWithReturnCode:], /SourceCache/AppKit/AppKit-1348.17/Nav.subproj/NSSavePanel.m:5277 05/06/19 6:23:00,680 PM com.apple.appkit.xpc.openAndSavePanelService[51214]: -[NSSavePanel _reactToPanelDismissalWithReturnCode:] : unexpected nil URL value while handling NSFileHandlingPanelOKButton result! 05/06/19 6:23:00,686 PM com.apple.appkit.xpc.openAndSavePanelService[51214]: ( 0 CoreFoundation 0x00007fff8fb7f03c __exceptionPreprocess + 172 1 libobjc.A.dylib 0x00007fff9656476e objc_exception_throw + 43 2 CoreFoundation 0x00007fff8fb7ee1a +[NSException raise:format:arguments:] + 106 3 Foundation 0x00007fff9111a97b -[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] + 195 4 AppKit 0x00007fff9492bf3f -[NSSavePanel _reactToPanelDismissalWithReturnCode:] + 225 5 AppKit 0x00007fff9492c131 -[NSSavePanel _dismissWindowWithReturnCode:willRunSeamlessOpening:] + 26 6 com.apple.appkit.xpc.openAndSavePanelService 0x000000010907328a com.apple.appkit.xpc.openAndSavePanelService + 21130 7 AppKit 0x00007fff9492c565 -[NSSavePanel ok:] + 342 8 com.apple.appkit.xpc.openAndSavePanelService 0x00000001090732c0 com.apple.appkit.xpc.openAndSavePanelService + 21184 9 libsystem_trace.dylib 0x00007fff97ffecd7 _os_activity_initiate + 75 10 AppKit 0x00007fff944deeb1 -[NSApplication sendAction:to:from:] + 452 11 AppKit 0x00007fff944f4946 -[NSControl sendAction:to:] + 86 12 AppKit 0x00007fff944f4862 __26-[NSCell _sendActionFrom:]_block_invoke + 131 13 libsystem_trace.dylib 0x00007fff97ffecd7 _os_activity_initiate + 75 14 AppKit 0x00007fff944f47bf -[NSCell _sendActionFrom:] + 144 15 libsystem_trace.dylib 0x00007fff97ffecd7 _os_activity_initiate + 75 16 AppKit 0x00007fff944f2cb3 -[NSCell trackMouse:inRect:ofView:untilMouseUp:] + 2821 17 AppKit 0x00007fff9454b34f -[NSButtonCell trackMouse:inRect:ofView:untilMouseUp:] + 770 18 AppKit 0x00007fff944f1366 -[NSControl mouseDown:] + 714 19 AppKit 0x00007fff94a5b2dc -[NSWindow _reallySendEvent:isDelayedEvent:] + 14125 20 AppKit 0x00007fff943eac86 -[NSWindow sendEvent:] + 470 21 AppKit 0x00007fff943e7212 -[NSApplication sendEvent:] + 2504 22 ViewBridge 0x00007fff8dd58e7b -[NSViewServiceApplication sendEventWithoutCatch:withForwarding:] + 652 23 ViewBridge 0x00007fff8dd5958d -[NSViewServiceApplication sendEvent:withForwarding:] + 29 24 AppKit 0x00007fff94310b68 -[NSApplication run] + 711 25 AppKit 0x00007fff9428d244 NSApplicationMain + 1832 26 libxpc.dylib 0x00007fff8cd90928 _xpc_objc_main + 793 27 libxpc.dylib 0x00007fff8cd92030 _parse_sysctl_once + 0 28 ViewBridge 0x00007fff8dda7ba5 xpc_connection_handler + 0 29 ViewBridge 0x00007fff8dd5c656 NSViewServiceApplicationMain + 2035 30 com.apple.appkit.xpc.openAndSavePanelService 0x0000000109074035 main + 208 31 libdyld.dylib 0x00007fff936e45c9 start + 1 32 ??? 0x0000000000000001 0x0 + 1 ) In fact the 'com.apple.appkit.xpc.openAndSavePanelService' crashed silently (only to be noticed by the generated User Diagnostic Report): "Application Specific Information: Crashing on exception: -[NSSavePanel _reactToPanelDismissalWithReturnCode:] : unexpected nil URL value while handling NSFileHandlingPanelOKButton result!" ---- Currently the problem seems to have disappeared and I can not reproduce it anymore. I'll will investigate further, if it might pop up again.
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.