Dan C

As I understand it, an Open Curve will only display 1 node handle for the Start & End node and this is expected behaviour. If the Start / End node is set to Smooth or Smart, then an opposing node handle will only be shown when moving the visible node handle and will not remain visible once the transform has been completed. Therefore I don't believe that a node handle is 'missing' in the users file - as there are multiple actions that I have found that will fix the issue with the users curve in the file, that don't involve directly editing the node. For example, simply using Flip Horizontal on the entire curve object then allows it to export, but using this command twice to return it to it's original position shows the issue return - 2023-10-09 11-16-45.mp4 I haven't seen this occur previously - converting/transforming the end node, editing the node handles or flipping the Curve allows the object to export, but I cannot see a clear cause for this in the file. Therefore I will be logging this with our dev team now, though in the meantime using any of the above options should resolve this for you. I hope this helps

Of course, following the steps I outlined previously you can install Affinity Photo and Publisher from the below links: Photo - https://store.serif.com/update/macos/photo/2/ Publisher - https://store.serif.com/update/macos/publisher/2/ I hope this helps

Thanks for letting us know @Jose.rios & I'm sorry to hear this. I have updated our bug report and 'bumped' this issue with our development team to bring it to their attention once again! I hope this helps

Thanks for your report @anto! As above, this issue is already logged with our development team, therefore I have updated this report and 'bumped' it to bring it to their attention once again. I hope this helps

Thanks for letting me know and I'm sorry to hear this - unfortunately this issue is still marked as unresolved currently. I've updated the development log and 'bumped' this issue with the team, to bring it to their attention once again. I hope this helps

Hi @BengtCa, Unfortunately the Affinity apps don't support any Lightroom Presets, therefore this pack is not compatible, my apologies.

Hi @DayDot, Welcome to the Affinity Forums & thanks for your report! As you've found, unfortunately this is a known issue with V1 on Sonoma, which has been logged with our development team. I'll be sure to 'bump' this with our team using your thread, to bring it to their attention once again. We hope to have this issue resolved as soon as possible, but I'm glad to hear you're able to use the V2 trial as a workaround in the meantime

Hi @aleale1, As confirmed above, unfortunately this is not a bug, simply the Affinity apps do not support this feature at this time. Therefore I will move this thread to the Feedback section of the Forums for our team to see and consider adding this in a future update. I hope this helps

Hi @Barbarazo, Welcome to the Affinity Forums As above, I suspect the Affinity app hasn't quite been installed correctly, causing the behaviour you're seeing. The install process has previously been covered by my colleague MEB, could you please check the steps shown below post and ensure you're following this workflow exactly with the downloaded .DMG file? Once you have installed the app using this method, you should find it appears within your Applications folder and should be retained here, as expected. I hope this helps!

Hi @rhythm.rubrics, Welcome to the Affinity Forums Thanks for your report! As above this is a known issue which is already logged with our development team, though I have 'bumped' the issue with this thread to bring it to their attention once again. We hope to have this issue resolved ASAP, our apologies for any inconveniences caused in the meantime. I hope this helps!

Thanks for your report @vincentlepes, as above this is a known issue which is already logged with our development team. I'll be sure to 'bump' this issue using your thread with our dev team now, to bring it to their attention once again and we hope to have this resolved in a future update. Please note that the previous 'AFD-5459' report tag has since been updated internally and is now logged under 'AF-633'. I hope this helps

Thanks @MikeTO & @walt.farrell for your report / testing here! I've been able to replicate this issue (it seems to work correctly with an active text selection, but not when the text caret is simply placed within the text object) and therefore I have logged this with our development team now

Thanks for confirming that for me, I'll be sure to update our development log regarding this now. This isn't behaviour I've seen being reported by other users - either in relation to this specific issue, or the 2.2 update in general. Are you able to provide a screenshot showing the exact issue you're seeing when your file loads within Affinity? Does this happen for any document, or only one specific one? If you use File > New and create a new document, does this display as expected, or do you see the same error with a blank document please? Many thanks once again

Thanks for letting me know, I'm certainly glad to hear this seems to have resolved the issue for you - though please do keep us updated! I would certainly recommend this to avoid similar issues in the future

Hi @Jon McCallon, Sorry to see you're having trouble! In order for our team to investigate this further, can you please confirm for me: How are you connecting your MBP to the external display? Do you have the MBP open (ie with the screen in use) or closed (ie with the screen off) when connected to the external display? Are you opening the Affinity app on the external display, then disconnecting the display with the app still open to continue on your MBP when the above issue occurs? If this isn't the correct workflow, what exact steps do you take to trigger this issue please? Many thanks in advance

Hi @white flash, Sorry to hear you're having trouble! I can confirm that the Affinity apps have no control over files/folders that aren't currently open within the application and therefore have no way of deleting or editing files/folders from your PC that aren't actively in use within Affinity. I do note that you mention you've been able to replicate this with your specific workflow, however unfortunately I don't fully understand the steps you are taking. Can you please provide a screen recording showing the exact steps you are following, including; the folders you are creating, the files you are editing, how you are opening/saving/closing these files within Affinity exactly what you are doing when the files/folders disappear If you're unsure how to take a screen recording, please check out our FAQ linked below - Many thanks in advance!

Hi @Tambbu, Welcome to the Affinity Forums & sorry to hear you're having trouble! I can see from our internal database that your Affinity ID uses the same email address as your Affinity Forum account, and this Affinity ID has a valid Universal License for Affinity V2 - though of course due to privacy reasons I cannot see your password used for any account. I understand you aren't seeing the same issue when attempting to sign into the Affinity website directly, however I would recommend resetting your password for your Affinity ID using the below link, then try signing into the Affinity app once again to activate your license - https://store.serif.com/reset-password/ If you're still having trouble after trying this, please email affinitysupport@serif.com and we can assist further, as this will be easier when dealing with private information such as emails & passwords. Many thanks in advance

No problem at all, happy to help!

Hi @larsh, Sorry to hear you're having trouble! Are you referring to the following post? If this doesn't solve the current issue, can you please provide a screenshot of your document showing this text object with the Layers Studio visible, or alternatively provide a copy of the Affinity file so we can assist further? Vielen Dank im Voraus

Hi @Antonio Peregrino, Welcome to the Affinity Forums and I'm sorry to hear you're having trouble! Following the release of macOS Sonoma, our team have seen an increase in similar reports and we're currently investigating this further - as it appears as though a change to how macOS handles documents stored in the Cloud is affecting certain Affinity users. I note that you mention the 'Affinity Cloud' for your document storage, however we don't offer such a service at this time. Can you please confirm if you are using iCloud, OneDrive, Dropbox, GoogleDrive etc? Secondly, many of the users that report this issue have informed us that after waiting a certain amount of time with the Affinity app 'loading' the document, it will then open as expected and further files will not have any issue - such as in Jaya72's post above. Can you please try opening one of these documents and simply waiting for the app to load this file, and let me know if this eventually completes? The time users need to wait seems to vary based on how much data they have saved to their specific cloud service (also indicating this is a wider overall issue with macOS Sonoma , rather than the Affinity apps themselves), meaning you may need to wait upwards of 60 minutes for the file to open. Once this file opens, are you then able to load and edit further files from your Cloud source, as expected please? Thanks in advance! _______________ Hi @Jaya72, Sorry to hear you're having trouble here also! Many thanks for letting us know - this certainly sounds like the known issue that our team are investigating, as covered above, and I'm glad to hear documents are now opening correctly for you. Our team are tracking all information our users provide regarding this issue, in order to relay to Apple to try and determine the root cause, so I will be sure to 'bump' the internal development log with this thread now. As far as I'm aware, after waiting the initial period for the first file to open, further documents should load as expected and we're yet to see a report of this behaviour returning for any users after this - but please don't hesitate to update this thread should you need any further assistance or have any further details to share

Hi @Lorox, Thanks for your report! As noted above, this is unfortunately a known bug in 2.2 which our team are working to resolve ASAP. I'll 'bump' this issue with our development team using your thread, meaning you should be automatically informed here once the issue has been fixed by our team. I hope this clears things up

Welcome to the Affinity Forums @LilyB! I can confirm this is a known issue with Affinity V1 on macOS Sonoma, please see the below FAQ for more information and steps to resolve this crash - I hope this helps

As I understand it, 'Full Disk Access' allows the Affinity app to read/write files anywhere on the macOS System. Without this option enabled, the Affinity app will be able to read/write to folders that have been previously 'Allowed' when prompted for access, which can be seen under Privacy & Security > Files & Folders. For example - However as I'm personally a Windows user and not a macOS aficionado, I believe there are some additional caveats with macOS file security that are beyond my current understanding - therefore our team are advised to simply ensure that Full Disk Access is enabled for any such reports, to ensure that the users issue isn't caused by a permissions issue with macOS directly.

I believe the PDF data from the embedded file is essentially 'missing' from the Affinity document, and the app is trying to determine the file type for the data remaining - albeit incorrectly. There are a few oddities with this embedded file, including the 'Type' shown in the resource manager, assumedly due to the unexpected status of this embedded data, which is also causing the reported issues when exporting. As above, I've logged this file with our development team for further investigation, as without the required development tools it would be very difficult for me to be certain of the exact reason for this file being in the 'embedded' but 'missing' state that it appears to be in.

No problem at all, thanks for verifying that! Looking on the Acer website, it appears as though version 27 is the latest driver provided there, however AMDs website shows that Adrenaline version 23.9 (which contains driver version 31) is compatible with your AMD 35000U APU. Please find this available for download here - https://www.amd.com/en/support/apu/amd-ryzen-pro-processors/amd-ryzen-5-pro-mobile-processors-radeon-vega-graphics/amd-0 You may wish to perform a 'clean installation', removing your current driver using DDU, before installing the above driver - though this shouldn't be a forced requirement. Please do let me know if this helps