dkenner

Not seen anything. Hopefully buried in a queue somewhere.

Perfect. Sadly for me, and a bit confusing, the most recent file in there is from February, with several from 2023. Given the daily use, and crashes, I'd have thought it would be more recent. Oh well. Thank you. Dixon

That directory has a large number of *.propcol files. most from 2022, the last from October 2023.

Nope. Says to look in -> ~/Library/Group Containers/6LVTQB9699.com.seriflabs/v2/user/ There is no "Group Containers" within /library, nor "Containers", nor the plist.

That was back in 2020/21 when I was endeavouring to use an external, parasitic HD. Tried several different ones, but APub would inevitably crash when placing an image. Eventually, all work with APub is done on the local drive.

Oh, this was during a save. I a quite familiar with APub and application crashes. This one was with a CMD+S. You see, APub crashes regularly, and yesterday was about six crashes. Two of which I sent the crash reports to Serif. The second was this (I have a screen shot right before things went south), earlier in the day, the other was a crash while deleting text (go to a text box, hit CMD+A, then the space bar as a fast and easy way to get rid of it) and then realising that one was a mistake, so hit CMD+Z. Crash. I have been sending in crash reports for a couple years now. Though only the "new" ones that I come across. The earlier one yesterday I thing was when I used CMD+Z to restore some text within a small text box. Recently, even moving between CMD+0 and CMD+1 can generate a crash report. When I come across something "different" I send in the crash report. APub will crash several times a day just placing images into a picture frame. That has been going on since V1 several years ago. 2020 I believe when I first tried out APub and loved it and bought the suite. Back then, the guess was the use of an external, parasitic hard drive, on this M1 MacBook Air. Now, everything is processed on the local drive. And given APub's tendency to crash multiple times a day, I use CMD+S religiously after almost every change to the documents. So, all to say, quite familiar with this drill. Multiple versions? Yes, my bad. I create a new one every week. I was just getting towards that step when this happened. V2.5.5 has been particularly horrific for crashes, with multiple per day. Thank you for your help, I'll check out the links. Dixon PS As ref, latest version of APub, Latest version of MacOS on a M1 MacBook Air, 8gb ram, 512gb disc.

Where my a previous recovery file be located on the local drive (MacBook, M1, Latest OS, APub 2.5.5)? I was working on a document, hit CMD+S and the above message appeared. I am hoping not to lose a month's worth of work. Thank you,

Mostly just curious. When I [cmd+s] to save a file regularly (APub likes crashing at odd intervals) sometimes the dialog box with the progress bar pops up and shows it saving the file, most of the time it doesn't. Why? I would have thought that the behaviour would be consistent, always showing it, or never showing it. Again, just curious. Dixon Kenner MacbookAir, 8gb, latest MacOS, latest APub v2.1

I installed the Beta on my MacBook the other day to look and see if I could recreated some issues that crash v2.0.4 on a regular basis. The Beta installed flawlessly, was opened, a journal that I have been working on was copied to a new file opened, and that testing started. I then went back to my v2.0.4 and continued to work on the journal (note, the autosave is configured and it never singled a problem). Eventually I hit [cmd + s] to do a save and I got an error message. "Failed to save document: xxx. Save Failed - changes to the file are not allowed". This caused some head scratching. I posted the screen shot and asked for idea, as I was at a loss. One suggestion was to [cmd + I] the file and check the permissions. Good idea ... Going into the file finder I highlighted the open document and hit [cmd + I]. Up popped up information on the file. Nothing obvious in the top section, so I opened up every possibility looking for the read, write execute permissions. When I got to "Open With" there was the problem. I installed the Beta recently and it had changed all of the .APub files to open with the beta and not with v2.0.4. I changed all .APub back to APub 2 from the beta and the problem seems to have vanished (now now).

Relative paths for the .apub file to relatively linked resources would be nice when the .apub is in the cloud (with linked resources), the local HD or on an external drive (w/ resources locally).

I just installed Ventura and Publisher came right up. No issues that I see...

It was unchecked, so I checked it. No change. Documents open when I close APub are not reopened when APub is relaunched. I will check the iMac settings later this week. Odd. More curious than anything. Thank you for the idea though. Dixon Kenner

I have the checkbox turned "on" on both my 2019 iMac and my 2020 MacBook Air. On the iMac, when I relaunch Affinity Publisher it opens the documents that were open at shut down. On the 2020 MacBook Air, they do not open. Am I missing something? Just curious, it is easy enough to goto "open recent" and take the topmost file to open. Both devices are running the latest OS/X (12.3.1), and the latest version of Publisher (1.10.5)

This does seem to get around the issue, though [option]+[green dot] is relatively unknown, and I would postulate that most will just click the green dot to maximize the screen. Thank you for this work around.

Something new. Thank you, Screen Recording 2022-04-04 at 13.51.18.mov It does it with other panels too. But I'll stick to this example.