matthewjrallen Posted June 7, 2019 Posted June 7, 2019 (edited) When I try to export an image image since 1.7 the saving process wont proceed past where I press the save button. The app hasn't crashed as I can still access the mac menu bar. Update: It seems to only happen when replacing a file. If i choose a different location to save it to, it behaves normally. Edited June 7, 2019 by matthewjrallen Added an update after further testing Quote
Staff Chris B Posted June 7, 2019 Staff Posted June 7, 2019 Hey matthewjrallen, welcome to the Affinity Forums. I believe this is an old issue but I haven't seen it for a while. Could you confirm which version of macOS you are on? Are you also trying to rename the file by right-clicking it too? Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
matthewjrallen Posted June 7, 2019 Author Posted June 7, 2019 Hi Chris, Thanks. No, not trying to rename by right-clicking it. I just click save and the finder window where all the files were goes blank and then wont do anything else. I'm on High Sierra 10.13.6 Quote
Staff Chris B Posted June 7, 2019 Staff Posted June 7, 2019 I think this might be a High Sierra issue which is why I haven't seen this for a while. It was reported in 2017 and I've only seen a couple of reports since Mojave came out. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
peter67 Posted June 8, 2019 Posted June 8, 2019 I have the same issue since updating to 1.7 and I am running Mojave. I have just found a way round it by using the share option to save the photo back into the Mac photo section. Quote
Staff Chris B Posted June 10, 2019 Staff Posted June 10, 2019 Hey peter67, That's not really a workaround we would expect you to have to do. I'd really like to investigate this so could you go into a bit more detail please? The issue mentioned above should only happen when replacing a file on High Sierra or older AFAIK. Can you confirm if you are replacing an existing file or trying to save a new file. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
matthewjrallen Posted June 12, 2019 Author Posted June 12, 2019 Can you suggest anything I can do to try and fix the issue? Quote
Staff Chris B Posted June 12, 2019 Staff Posted June 12, 2019 4 hours ago, matthewjrallen said: Can you suggest anything I can do to try and fix the issue? For now, just save the file as opposed to replacing it. We are starting to see more reports of this emerge—which is odd seeing as we haven't seen it for a long time. It could be the update that has caused it but I'm not sure. AFAIK it is currently being looked into by a colleague so I'll update you once I have any news. Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
matthewjrallen Posted June 12, 2019 Author Posted June 12, 2019 23 minutes ago, Chris B said: For now, just save the file as opposed to replacing it. We are starting to see more reports of this emerge—which is odd seeing as we haven't seen it for a long time. It could be the update that has caused it but I'm not sure. AFAIK it is currently being looked into by a colleague so I'll update you once I have any news. Thanks for the update. Glad to hear it is being looked into! Quote
Recommended Posts
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.