Garytagreg

Have just tried launching the apps again now that I’m home with internet access. The issue seems to have resolved itself. They all launch fine now… and significantly faster than when I was without internet access. Funnily enough, though, for a while if I toggled my wifi OFF I had the same issues as described above but then forcing the app to quit, toggling wifi back ON and then trying again worked fine… However, I then rebooted and everything works as expected now, wifi or no wifi. 🤷‍♂️ So, my problem appears solved but maybe there’s something that causes an issue somewhere if you update and try to use it without having run it with an Internet connection first. Rare, I’m sure, but it was annoying to not be able to use the apps at work today so maybe something to look into some time? Let me know if you need any further info. Been using these apps for 10 years now so happy to help make them even better. 😃

Hi, Last night I updated to version 2.5.5 (via the App Store). I didn’t run the apps immediately after updating but now that I try to, none of them want to launch properly. Photo and designer: app seems to launch as normal (shows splash screen etc.) and the window shows up but I get a beach ball and nothing (menus, panels, etc.) responds to clicks although the rest of the system is fine. I have to force the app to close. Publisher: after looking at suggestions in what looked like a similar thread, I control-started the app and cleared the user data. App “launches” to the splash screen (the “lessons” page) (the app does show up behind it) but attempting to click on anything just shows a beachball and is the same as the above. Activity monitor shows the app(s) using around 30% cpu and, over time app memory usage appears to be creeping up slowly (480MB to 700MB over about 5 minutes) I’m running the latest release of Sonoma (14.6.1), MacBook Pro 14 inch November 2023 model (M3, 16GB ram) I’ve tried rebooting and trying again a few times with no difference in what I’ve explained above. The machine is not connected to the internet (I’m at work where I have no access at the moment). I’ll try again when I return home tonight and update this report but that’s never been an issue before. The text that flashes up on the splash screen seems to indicate that it gets past any license authentication. I’m attaching the macOS report text from when I forced a close on publisher if it may be useful. Hope this helps! Report.rtf

Thanks, @SPaceBar ! That’s seems to have done the trick. All working now. I hope the devs will find my logs useful in fixing the issue.

Hi, I've run into a reproducable crash in the current app store version (1.8.4) of Publisher that's been quite a pain for me. I'm not able to install the current beta at the moment so I can't confirm if it crashes there as well, but I suspect it would, too. Basically, every time I create a document with a certain template I made, the app will crash if I: - creat artistic text - use the "Layer->Convert to Text Path" menu option on a curve If I don't use the template and just use a built-in preset (Print->A4, for example), the app does not crash and runs just fine, so I suspect there is something in the template configuration that is causing havoc somewhere. An important detail about my computer configuration: I have Japanese installed as my secondary system language (primary being “English (South Africa)”. The template in question does have some Japanese text in it, using "Hiragino Maru Gothic Pro" font, which comes pre-installed with macOS. I mention this as issues with Japanese text have been part of previous issues I've reported here. I'm attaching the following files that I expect will be useful - TextCrash.aftemplate : the template in question - Text on Path Crash Report.txt : crash report generated when I tried to "Convert to Text Path" - Artistic Text Crash Report : crash report generated when I tried to create artistic text I hope this helps! TextCrash.aftemplate Artistic Text Crash Report.txt Text on Path Crash Report.txt

Glad to hear that its getting tracked down Here is what "locale" gives me LANG= LC_COLLATE="C" LC_CTYPE="UTF-8" LC_MESSAGES="C" LC_MONETARY="C" LC_NUMERIC="C" LC_TIME="C" LC_ALL= My workaround is just to make really big frames before pasting the text, just to ensure it fits.

Thanks for the replies, I've answered the questions above and I've attached the crash report. I had some really wierd crashes with early versions of designer that eventually were found to be due to having Japanese installed as a secondary language on my computer (I live in Japan but I'm not Japanese). I seem to remember that it was crashing a menu somehow, even though I was doing something apparently unrelated. I'm just mentioning this again as it is the main difference in my setup to most folks. Hope it helps. Crash Report.txt

I'm getting a reproducible crash on publisher with the following steps: create a new document create an empty frame text frame copy a block of text several lines long from another app (I've been using the Notes app) that has enough text to not "fit" in the frame crashes every time I've attached a sample file with the empty text frame and a file with some random text. if you paste the text from the text file into the frame in the publisher file it crashes immediately. It also crashes the latest beta at this time (1.7.3 475). I'm running Mojave 10.14.6 on a MacBook Pro (Retina, 15-inch, Early 2013). As I've had weird crashes connected with text in designer and photo before, I should also mention that macOS has Japanese as a secondary language installed but that the text being pasted does not have any Japanese text in it. Hope this helps Text to paste.txt Empty frame.afpub

All right then... I just control- started the app and cleared all data and now it magically works... :rolleyes: There must have been something cached somewhere that was affecting things. So its all good now, but a pity we couldn't nail down exactly what was causing it. Thanks all! :)

Oh boy, not another one of those :wacko: ... I just tried it in the latest App Store version on my El Capitan partition and it worked fine: smooth, no beachballs...

I just tried moving stuff around on "Icecream Thing" sample and I get a definite 2~3 second delay when moving its shapes around. Usually not a beachball but I did get one or two in my test.

Nothing else major is running, just AD and safari and a couple of menu bar apps. I even reinstalled AD from the App Store. Did you manage to move a window on the building around? The scene itself works fine and I can pan and zoom around nice and smoothly without any beachball. Its when I try and move a window on the building to another place that it dies. Interestingly, option-dragging a window to duplicate it works fine, but will cause the beachball once I "let it go" and try to move it. BTW: during the beachball, activity monitor shows 100% CPU utilisation and no noticeable change in memory usage (about 350MB). If it succeeds in completing the move, CPU returns to 2% and the beachball disappears.

Hi I was testing out the symbols by making a simple isometric building with symbols for the windows and, while I managed to make a decent number of them, now trying to edit things by moving the windows around is dramatically slow, with the beachball coming up and usually ending with me having to force quit the program. Panning and zooming the scene is fine, but just trying to move a window by even a tiny bit brings up the beachball. While I can understand that there are quite a few shapes, groups etc. in the scene, it doesn't seem to me that there are so many to cause such a dip in performance. Maybe its something to do with symbols backend? Or, am I just being overly ambitious ;) I've attached the file in question. Try to select and move a window around. Hope it helps :) My system: MacBook Pro (Retina, 15-inch, Early 2013), 16GB RAM, using the GeForce GT 650M discrete card. Latest Sierra Public beta (10.12.2 Beta (16C60b)) AD ver 1.5.4 (Mac App Store version - I can't run the latest beta as its version is earlier than my App Store version) Apartment Building.afdesign

I'm getting a reproducible crash when trying to create a focus stack with the images linked below. I first came across it a beta version or two back but its still happening now so its probably unreported by others so far. They're not the best candidates for a focus stack (I was just playing around with the feature and some macro shots I took in the garden) but they shouldn't completely crash the program ;) Dropbox link Sorry if the file is a bit big (66MB - they're tiffs) but I wanted to send them as is, in case its an issue with the file format or something. Hope it helps :)

Mentioned already in the designer thread, but I can confirm that the issue I was having with renaming the currently selected layer is fixed (I assume that was the "Fix for double-clicking the selected row in the Layers Panel causing the incorrect behaviour.") Thanks!

Just to confirm that the issue I was having with renaming the currently selected layer is fixed :) Thanks!