nwhit

Just as an FYI, I'm still using AP beta 1.9.2.236 and Unsplash works fine for me on Mac Catalina. While my "regular"/working version is still Affinity Store 1.8.6, I've been upgrading the betas through the 1.9 series and now using the last one. Doesn't provide a solution for your issue, but at least a reference point.

I'm still using beta 1.9.2.1024 and macOS 10.15.7, but it works fine for me.

I just tried my G**gle Nik filters using the 1.9GM beta and they seem to work fine on Catalina. I am using the Affinity Store version. Had to switch from MAS version and buy the Affinity version awhile back in order to get Eye Candy filter to work.

This feature is in APhoto 1.9 beta that is pretty close to coming out. They're working out the last few bugs, but you can try it yourself by installing the beta from the beta thread. Installs side-by-side with the release version, so nothing harmed by trying it. I also need this feature VERY badly, so am pleased it is finally here. This is the Mac beta: https://forum.affinity.serif.com/index.php?/forum/19-photo-beta-on-mac/

Thanks for this! I just last week started playing with the new beta and was perplexed on how to work with a merge, even after reading the Help file! Hopefully the release will have much clearer instructions similar to what you've presented!

What I eventually found out from exhaustive testing was that the Mac App store version simply could not get around Apple's sandboxing security to run Eye Candy. In my testing, the beta versions always ran it fine, but that is not using Apple's sandboxing since it comes from Affinity directly. In the end, I bought a new copy of Photo from the Affinity Store and it has worked well. Didn't like having to spend an additional $50, but for the amount of work it saves me using Eye Candy for client work, it was pretty danged cheap! It's not like competitive products where it might be several hundred dollars to buy an additional copy, so it fixed my problem and I'm happy. And with all of the major upgrades/improvements/new features Affinity has provided to date with no upgrade charges, well worth supporting them as much as possible!

Okay, I just tried opening multiple times with the 5 embedded-version docs open and it opened every time. I then switched to multiple opens of the original linked-version 5 docs and no crashes. The only "difference" that I can think of before this morning's crash was that the computer had been in Sleep prior to opening APub (woke up about about 20 minutes before opening APub). Not sure if that would be a cause of any issues, especially with the linked resources, but that's all I can think of that was different. And as originally reported, when it did crash and upon reopen asked if I wanted to reopen the previously open docs, it did not open them (as was the case with all previous crashes). Not sure why that has not been working as it should. Anyway, the docs and crash report are uploaded.

Sadly, had another crash on Open. I have uploaded the 5 files that were open plus the newest crash report. I changed the APub docs to have embedded resources, so everything should be there (hopefully!), although I normally work with mostly linked resources for the most part. On creating a new Prefs folder, can try that for an opening or two but can't do it for a longer time since I have work to get done and need my workspace layout and other defaults, etc. And since this has been an intermittent problem, not sure if that will do much, but can give it a temporary try.

Jon, since upgrading to 1.8.6 and then subsequently closing and reopening, I haven't had a crash. That said, I was working on several similar docs this last few weeks, so can't really remember which ones were open when the crashes were happening (typically have 4-6 open). Can you tell which docs were trying to open from the crash reports? I could save them as resource-embedded and send to you just to see if maybe I'm not currently working on one of those that were previously causing the crash. Thankfully I may not need to start with a new App Support folder since, if I recall correctly, I would lose my prefs, workspace, defaults, etc., which would be a real pain to try to reconstruct. I'm VERY pleased to see that the 1.9 beta will have savable workspaces/Studio layout. Takes some time to develop a "friendly" workspace, so in the past was always a huge PITA to lose it from a crash, etc. Also will be extremely nice to be able to switch to various workspaces based on what a person might be doing in a project. But as of today, opening APub 1.8.6 with 5 docs has not caused a crash, so either I am not opening the "faulty" doc any longer, or the problem has gone away with my recent upgrade.

Been having this issue for a few weeks using previous version of APub, so after finishing a project upgraded to 1.86 this morning to see if it would fix it. Didn't. Routinely get a crash (fails to open and get the Report dialog) with a cold start. Additionally, if I click to reopen the previously open docs, it never does. Have not had this occur through many versions of APub including numerous betas. Not sure what it causing it. None of the open docs are complex, etc., so doubt they are to blame. Also, never have this happen with APhoto, so just APub is doing this. 2019 iMac with internal SSD, Catalina latest. Last 2 crash reports attached. Affinity Publisher_2020-12-08-100020_TRAC-Main17.crash Affinity Publisher_2020-12-09-120542_TRAC-Main17.crash

I moved the main text frame off the page, created a new text frame on the main page, then copied and pasted all the text from the single, old, stretched text frame. Once pasted into the new text frame on page 1, I could then click and flow to a new frame on page 2 without the issue. Apparently at some point the original main text frame became corrupted, thus not allowing a flow to a new frame. Not sure when or how that happened since I have been using this "template" for a while now without that issue. And for 2+-column main text frames, never use the scale handle. But in the end, now can say it's fixed.

Yes, I read the thread on the IDML import, but this was a created from scratch back a couple versions. Text was a copy/paste (unformatted) from a text document for other media, but each paragraph copied/pasted from various other text sources (web, html email versions, etc.), but as normal for much of our past work, all brought in as plain text (unformatted) and into paragraphs setup with Styles. Unlike in past versions, the formatting/font size stays correct if the text flows within the same frame. But as soon as you flow it to a new frame, the remainder of the interrupted paragraph in the new frame is the wrong size. The following paragraphs remain correct within the new frame. And, you are correct. The original frame was not scaled. I did find one workaround, but it is not a workable solution. If I copy the initial text frame with the entire text, paste it on the new or same page, delete the text within that pasted frame, then flow from the original into this now blank frame, things work. Very strange. And the odd thing that suggests a bug is that when you roll-up the original text frame, thus pushing more text into the new linked frame, the text that moves into the new frame is likewise enlarged/wrong size. The "split" paragraph simply can't make it across the link without changing font size in the new text frame for the balance of the split paragraph.

Not sure if this is the same as a couple other threads that report similar issues, but I can't seem to work around this issue. In 1.8.4 when I try to flow text to a new frame, the font size jumps significantly FOR THE REMAINING PART OF THE PARAGRAPH THAT FLOWS TO THE NEXT FRAME. I've tried using the loaded cursor (from the flow icon) to drag out the new text frame, tried creating a new, blank frame, and either way, the first few lines of the overlapping paragrpah have the wrong font size (Text Style was applied to the paragraph). And, no, I did not stretch the text frame using the "scale" handle. I dragged out a new text frame, either from scratch/new or with the loaded flow cursor. I can upload the file with embedded assets with a private link. I don't recall having this issue in previous versions. I also have read that there is a reported bug if the text frame has been scaled with the bottom-right extended scaling handle, but I didn't do that in this case. Has made it very difficult to edit and finish the last couple of these docs where this problem cropped up. Has required creating a line break and then changing the incorrect font sized lines. Thanks.

Thanks, Gabe. I can't remember if I copied the assets.propcol from my MAS version or from my beta version, so I have attached both in a zipped folder. I had copied all the user files/prefs, then after opening the app and discovering that I had lost my workspace, began to recreate it. When I started to add panels to the left side, that's when I got CTDs with some panels. The assets one could not be added, crashing each time I tried to add it. Thus I deleted the pref and it worked to add a new, blank panel. I can't really recall if I was actually using any assets in Photo. I know I have been in Publisher, but only for minor things until that feature got ironed out a bit in the last couple versions. May have to try using it more now in both apps, assuming things are working well with it. Thanks for checking on this. Just so darned pleased that I now have EC working in a release version! Kind of a minor thing, but I do use it for clients routinely, plus I'm attempting to move from Mojave to Catalina, thus need to rely on my old CS5 apps from within a Parallels Sierra virtual volume, which works but isn't ideal. Assets prefs to Serif.zip

That would be VERY welcome, and I'm sure by many, many pro users. Been spoiled with so many media production apps that have had that, I think many were surprised when the Affinity suite didn't have it. Let's hope you're right. I'm suspecting that it might be awhile before we see the next betas due to the ongoing situation, especially in the UK. But keep our fingers crossed. It's one of the reasons I didn't feel badly at all about paying an extra $50 for a new copy of Photo to solve my needs, especially given how generous/wise Serif have been about the multiple upgrades this last few years.