Dan C

Welcome to the Affinity Forums @Bobolous & sorry to see you're having trouble! Can you please provide a copy of the PDF file you are importing into Affinity here for me? Many thanks in advance

Thanks for trying that for me, I doubt that 'Clean My Mac' would affect this but it's nice to be certain. Absolutely, we can try changing Affinity Designer 2 to the Affinity Store version to see if this is related to the issue you're having - in order to do this, please: Open your Applications folder Select Affinity Designer 2 Right-click and select Send to Trash Visit the below link to download the latest 2.2 DNG: https://store.serif.com/update/macos/designer/2/ Install this using the default installation method With this version, try the previous workflow outlined above If the issue continues, can you please provide a screenshot of your Apple System Settings > Privacy & Security > Full Disk Access? I note you have mentioned you've checked your permission settings already, but I'd like to be certain. Finally, I'd recommend trying the following suggestions from thomaso above; Please do let me know if this changes the behaviour experienced!

Hi @Romanos, Welcome to the Affinity Forums & thanks for your report! From the file provided, this appears to be failing to export to PDF due to the "School Masses, Ordinary Time Fall 2023 (A) Fridays of August & September • Voice 5.5.pdf" document, placed in your file. As can be seen in the Resource Manager, this is the only embedded PDF file which cannot be 'Collected' or 'Make Linked', indicating the PDF data itself is missing from your Publisher document - I'm not entirely certainly of the cause of the issue with this PDF in your file - however after deleting the 3 instances of this placed document from your file, I was able to complete the PDF export as expected. I'd recommend deleting this placed PDF from your document and replacing this with the original PDF file, then try exporting once again. I'm logging this document with our development team now as I've not seen this occur previously. If possible, are you able to attach a copy of this specific PDF file here for me? I hope this helps

Thanks for letting us know @Sulaiman_ and we're sorry to hear this. As above our team are aware of this issue and we're working to resolve this as soon as possible. Many users report that this only occurs with 60/70+ fonts, though I do appreciate it is not ideal to have to remove fonts installed from your iPad as a workaround in the meantime. I hope this clears things up

Sorry to hear you're still having trouble here! As Walt has mentioned, the best thing would be a screen recording showing the exact steps you're taking and the results you're seeing. If you're unsure how to take a screen recording, please check out our FAQ linked below - Many thanks once again

I wish to provide an update regarding your reports @Caleela & my apologies for the further delay here, this issue is still ongoing in testing and I can confirm I've now been able to replicate the issue with your file size not changing after deleting multiple pages from your file etc - however I am still investigating the Data Merge and Add Pages From File issues. This is unfortunately taking longer than I had hoped currently due to the 2.2 update being released recently and our technical support team being inundated with customer contacts at this time. We're doing our best to ensure that both new users/issues are addressed quickly, whilst trying not to allow previous reports to fall too far behind. Due to the nature of this issue, the long delays between opening, editing and saving your document are also increasing the time it takes our team to fully investigate and report these issues to our developers. I understand this issue is of importance to yourself, so I must apologise if this is seen as an excuse and I thank you once again for your patience and understanding here, it's certainly appreciated. I will be sure to update this thread in due course regarding the other issues you have raised here

The users screenshot appears to show the Toolbar without a document open, which is purposefully 'greyed out' as the options cannot be used, and therefore it's expected to render slightly darker. If they open or create a new document, I would expect the UI to match the screenshot above - as this is the behaviour I experience.

I can confirm our team are aware of a few different anti-virus apps causing issues with the new 'lock' file functionality with Affinity documents - can you please confirm which exact Antivirus you are using? I can also verify that we're not aware of any issues from the Mac App Store Sandboxing with this new functionality, though it's certainly not technically impossible. Luckily, with Affinity V2 apps you can install from either the Mac App Store or the Affinity Store directly under your one license. If you'd like to swap to try the Affinity Store version and need assistance through this process, please do let me know

Thanks for confirming that for me! Unfortunately this is a consequence of the Affinity apps using the MSIX format and is something that Windows needs to resolve. This issue applies to any MSIX / Windows Store installed application, such as the 'Calculator' app provided with Windows. As shown below, there is no padded Colour around the app icon in Explorer, until it is added as a desktop shortcut and the blue highlighting around the icon is then added by Windows - Unfortunately Windows will need to address this for MSIX, as it is out of our control at Affinity. I hope this clears things up

No problem at all! As far as I understand, this issue has been tentatively fixed internally by our development team, pending further testing. Once this has been tested and confirmed, we'll likely release a beta update to allow users to test these fixes before we push the next update live. We don't currently have an exact timescale for either the beta or release update to resolve this issue yet, but we're working hard to ensure this is as soon as possible, as we understand how serious these issues are for our users. I hope this clears things up and my apologies I cannot be more specific at this time.

Thanks for providing that for me! I've tried using multiple methods to 'trigger' this issue, though unfortunately I'm unable to replicate this currently, a the Symbols Studio continues to work as expected in my testing. I have noticed a few things however: Is there a chance that the 'Spacebar' key is being held down, either incidentally or by a third party app that controls your keyboard input? As dragging a Symbol with the Spacebar held will appear to work correctly, but no Symbol instance will be added to your document. In the screen recording provided, as you select and drag the Symbol, a different symbol is highlighted once your cursor passes over it (note you click & drag the 'O', but the 'K' Symbol becomes selected) - Again, I haven't been able to replicate that behaviour here in my testing. What are you using for an Input Device please? Is this simply a mouse, a drawing tablet etc? Can you please verify for me, is this something you're able to consistently trigger in this file on your PC? If so, do you recall any workflow steps that you have to take in each file in order for the issue to occur? Many thanks once again

Not to worry, I can move this thread to the relevant section such that a new thread shouldn't be required I've tried replicating this here on my M1 Sonoma machine and unfortunately I'm not seeing the same issue currently - both in an Artboard / Canvas documents, and with Metal enabled / disabled. Can you please confirm for me, are you able to replicate this from scratch in a new file? If so, please attach a copy of that new file for me. If this only occurs in the file in your recording, please let me know and I will be happy to provide an upload link for this document, so that I can test further. Many thanks in advance!

Hi @HeikoKrause, Welcome to the Affinity Forums & sorry to hear you're having trouble! I can confirm this is a known issue in Affinity 2.2, please see the below FAQ for more information here - Unfortunately the only known workaround currently is to revert to update 2.1.1 - if you require assistance in reverting then please let us know

Welcome to the Forums @Barn 1965! Sorry to hear you're having trouble - as Hangman mentions above there is a known issue within Affinity 2.2 with applying Swatch Colours to Gradients, causing a crash of the apps. This issue is logged with our development team and we're working to resolve this in a future update, though I did want to confirm that this was a similar workflow you are following in order to trigger this crash? If you aren't using Swatches with the Gradient Tool, are you able to provide a screen recording showing the exact steps you're taking to trigger this crash please? If you're unsure how to take a screen recording, please check out our FAQ linked below - Many thanks in advance

Hi @j3rry, Thanks for your report! As above, unfortunately there is a known issue in Affinity 2.2 on Sonoma with selecting Lens Profiles currently - which is logged with our development team to be resolved ASAP. I'll be sure to 'bump' this log with your thread now, such that you are informed here once the issue is fixed. I hope this helps

Thanks for your report @maurizio f! I can confirm this is a known issue which our team are investigating further - I'll be sure to 'bump' this internal log with your thread now. We hope to have this resolved in a future update, our apologies for any inconveniences caused in the meantime.

Hi @MessyBOB, Welcome to the Affinity Forums Inspecting your document, I've found the following Mask layers on Page 8 to be the cause of the error/failure to save the document correctly: After deleting these mask layers, the error no longer appears and the document can be saved as expected. I'm not entirely certain of the exact cause for these masks to have become corrupted, as I cannot see any issue with their usage/layer structure of your document currently - therefore I'm logging this file with our development team to be investigated further. In the meantime, I've attached a copy of the recovered file here for you. onboardings kaarten_F.afpub I'm very sorry to hear that your work was lost due to this issue, as above I cannot see any particular cause for this currently, and I certainly don't believe that you as a user did anything incorrectly, or could have avoided this issue with a different iPad etc - simply unfortunately programmatic errors can occur within documents occasionally, and it appears as though your document was a recipient of such. I certainly would not expect this issue to occur again, but should you be able to recreate a corrupted Mask layer in a new document following a specific workflow, please do let us know and our team can investigate further

Welcome to the Affinity Forums @gabodoloroso & I'm certainly sorry to hear this. Our team are investigating this issue further to try and determine a possible cause, as this has not occurred on previous iPad update releases. Please do let us know if you require any assistance in following the iMazing steps above - I hope you are able to recover your files using this method. Our sincerest apologies once again for any inconveniences caused to our due to this.

Thanks for providing these for me - this shows that the AMD GPU is still using the same driver from 2020 that I mentioned previously, causing the crash within Affinity. I believe version 30 of the AMD GPU driver is compatible with your card, and you're currently running version 27. I believe this needs to be updated to use the Affinity app. However it may require an 'OEM' driver update, depending on the specific device you're using. Can you please confirm for me, what is the make and exact model number of the PC/Laptop you're using? If I'm not mistaken, I believe it is an 'ACER' device and therefore you may need to download the driver from Acer, rather than from AMD directly. Many thanks once again!

This issue is still logged with our development team as yet to be resolved internally, so I'm more surprised to hear that the issue was temporarily fixed and has now returned! I'm unsure why this would have been working correctly for you, but I can confirm that as the issue still remains 'Open', I would expect this issue to continue to occur, my apologies. However our team are working to resolve this and we hope to have it fixed in an upcoming update. I hope this helps

My apologies, this issue is not one that our team can replicate internally, nor are we seeing reports of this issue from other users at this time. I note that in your latest recording, the issue appears to begin after using Copy / Paste - does this always trigger the issue for you? Are you using a third party Clipboard Manager or similar? As I believe this issue is specific to your PC/User account, can you please create a new user account on your system, install Affinity Publisher 2 and let me know if the same issue occurs here?

I've followed the steps shown in the above tutorial and this is working as expected for me - my recording shows a 4 page PDF with the page number on each page, placed into 4 pages of a new Affinity document. 2023-10-02 15-48-41.mp4 From your description, it's unclear if you are 'expanding' the Placed PDF file in the Place Studio, selecting the pages themselves to auto-flow within the document. If you're still having trouble, can you please provide a screen recording showing these steps for me? If you're unsure how to take a screen recording, please check out our FAQ linked below - Many thanks

No problem @loudo, thanks for letting me know. I've reopened the same request, can you please try using the link above again for me?

Hi @tersmuse, Please see the below FAQs covering these issues: We're working to resolve these ASAP - if you need any assistance in 'rolling back' to 2.1.1, please do let us know

Welcome to the Affinity Forums @UltraDev I can confirm that this is expected behaviour - a placed 'Image' or 'Document' layer is rendered within a vector container, therefore can have Stroke settings applied. Once you rasterise the layer to a 'Pixel' object, it is no longer contained within a vector container and therefore the Stoke attributes simply aren't' compatible with this layer type. As mentioned above, the Select menu options are related to an active Pixel Selection ('marching ants') on your canvas and are completely separate from the FX options, which do not require an active selection. Unfortunately as confirmed by Return, there is currently no 'trace' tool within Affinity apps - though this is a highly requested feature and one our team hope to implement in a future update. You may be interested in the following list of third party alternatives for 'tracing' bitmaps/selections to vector objects: Sorry to hear you're experiencing rendering errors in Affinity, this isn't something we're seeing reported from other users consistently, therefore it may be related your system, Affinity document etc. Firstly, if you experience rendering errors then please try zooming in and out of the document - this will force the canvas to redraw & refresh and should hopefully mean you no longer need to close and reopen the app. Secondly, please ensure that your GPU driver is fully up to date, directly from the manufacturers website, as outdated GPU drivers can cause rendering issues within Affinity apps. I hope this helps!