AD V1 Bug?

[jackamus]

I'm getting a message saying that I don't have permission to create a file in that location. I've been working on this project for several hours without any problems. Is this a big?

 

[jackamus]

I have tried saving it elsewhere and with a different filename but I still get the error.

[jackamus]

I'm unable to do anymore work as I cannot save anything. This is worrying!

[markw]

Can you create a new document, then copy & paste the content of the problem document into the new document and then Save the new document?

[jackamus]

I created a new doc and copied the contents of the old page into it but I still can't save it.

[jackamus]

I'm getting a bit concerned that nobody has been able to advise me about this issue.

[markw]

Not sure I really have any solutions here as this has never happened to me, just things you might try!

Are you Saving locally to you internal drive and to a folder that is not synced to some form of Cloud Storage?
Can you make any new empty documents in Designer and Save them, say to your Desktop?

Do you have APhoto? Can it still save new or existing documents? If yes maybe try the Copy & Paste again but this time into a APhoto document and Save from APhoto.

[jackamus]

The problem seems to have gone away! Thanks for your concern.

[jackamus]

On 3/15/2023 at 10:55 AM, jackamus said:

I'm getting a message saying that I don't have permission to create a file in that location. I've been working on this project for several hours without any problems. Is this a big?

 

Although this problem seemed to go away it has come back again. I tried to save the file to a different folder - Desktop but it will not save. In order to carry on I'll close AD and hope that the file was automatically save earlier and try again.

[jackamus]

As I was closing Ad a message came up saying AD quit unexpectedly. I clicked the button to send to Apple but I doubt they will do anything.

Whilst writing this reply AD automatically re-opened and the file I was trying to save was still there. I am now able to save files OK.

This must be a bug so how do I isolate it if it happens again?

[v_kyr]

18 minutes ago, jackamus said:

I clicked the button to send to Apple but I doubt they will do anything.

What should Apple do about it if it's an Affinity software problem? - You better look after Affinity's own crash reports and the like ...

 

[jackamus]

8 minutes ago, v_kyr said:

What should Apple do about it if it's an Affinity software problem? - You better look after Affinity's own crash reports and the like ...

 

I agree and that's why I sent in that reply!!!!! I need to know what to do! You don't need to talk down to me in that way!

I followed the advice in the crash report link. Once I opened the Utilities app I found the Console app but it didn't offer 'Crash Reports - it offers

1Mac Analytical Data, 2 System Reports and 3 User reports. Which one should I look at?

[v_kyr]

24 minutes ago, jackamus said:

Which one should I look at?

Try to enclose the list to only those entries which are Affinity related ...

Beside the default MacOS Console tool, there is a another free and clear application for those things, it's also called Console and is from XS-Labs, see here the links ...

• https://github.com/macmade/Console
• https://github.com/macmade/Console/releases/download/0.3.1/Console.app.zip  <-- (it's app binary)

You can extract it and place that into the "/Users/your-user-name/Applications" folder. - That console app is slightly clearer in usage!

Another maybe even better one from XS-Labs is the Diagnostics app, see therefor ...

• https://github.com/macmade/Diagnostics
• https://github.com/macmade/Diagnostics/releases/download/1.4.1/Diagnostics.app.zip  <-- (it's app binary)

[jackamus]

I'm sorry but I cannot follow any of this. Its just confusing. I cannot beieve that there isn't a simple way to find the crash report without having to consider other diagnostic methods. In the past I managed to find the crash report easily but that was a long time ago. I imagine that software updates have added more complication to it! All I want is for someone to spoon-feed me a way into finding the crash report.

[v_kyr]

17 minutes ago, jackamus said:

... All I want is for someone to spoon-feed me a way into finding the crash report.

I've already pointed you to all that is usually needed about it to find crash reports! - And if you follow this advice here ...

Quote

macOS

Open the Console app from Applications > Utilities. In the left hand panel click Crash Reports - you will see a list of Crash Reports. Find the relevant crash report - it should display the app's name in the Process Name column. Right click and select Reveal in Finder. Please send us the .crash file.

... you should find any Affinity crash reports (... as far as there are some crash reports at all about it on your system). - Further I've also pointed you to alternatively more easily usable apps for these "finding crash reports" tasks on your system. - That's all I can do from here, the rest is up to you!

BTW, next time you get such an ADe quited unexpectedly message, copy it's contents as text into a file, so you can share it afterwards here in the forum and people can take a look at it and maybe identify what the overall problem listed is!

[jackamus]

Why do I need an alternative way if my Mac already can do it? The problem is that what you see on your computer when you open Console is not what I see on my Mac when I open it! I told you what I see and I imagine many other people will see the same thing on their Macs. All I want to know is which of the three choices have is the one to look at?

[Old Bruce]

1 hour ago, jackamus said:

As I was closing Ad a message came up saying AD quit unexpectedly.

 

20 minutes ago, jackamus said:

I cannot beieve that there isn't a simple way to find the crash report without having to consider other diagnostic methods. In the past I managed to find the crash report easily

Quitting unexpectedly is not crashing. Hence no crash report.

[v_kyr]

13 minutes ago, jackamus said:

Why do I need an alternative way if my Mac already can do it? The problem is that what you see on your computer when you open Console is not what I see on my Mac when I open it! I told you what I see and I imagine many other people will see the same thing on their Macs. All I want to know is which of the three choices have is the one to look at?

Make some screenshots and share them here (... from the initial error message, your Console view ... etc.) , so we (I) don't have to guess what you might see on your system instead!

The one you showed initially moaned about access rights ...

... did you checked your access rights, permissions, on that folder location? Also were you able to save that file under a new filename at all? - Did you also checked who's the owner of the file (root or user), or if maybe some other Affinity app had already a file handle on that document (it opened) so you can't save from Designer?

 

[jackamus]

OK maybe quitting was not a crash however attached is a screen shot of the Console app showing the report choices I have.

[v_kyr]

Note the search field there top right, type "affinity" in, also click/go threw the left hand side Report & Log sections there!

Other than that see the Apple documentation about the console app below, see also the table of contents there!

View reports in Console on Mac:

• https://support.apple.com/guide/console/reports-cnsl664be99a/mac

Find log messages and activities in Console on Mac:

• https://support.apple.com/guide/console/find-log-messages-and-activities-cnslbf30b61a/mac

 

[jackamus]

Thanks for the links. On opening the first link I selected my Mac OS and saw how to locate a 'System Report'. On inspection there was no AD crash but I did find an old report created about a month ago where AD 'Hung'.

I'll try to remember this procedure for the future.