j_h Posted February 23 Posted February 23 Hello, after upgrading to macOS 15.4 Beta (Intel iMac) Publisher 2.6, (Photo and Designer as well) could not save any files after changing content in the layout anymore. Works fine on a Macbook (M3) with macOS 15.4 Beta (24E5206s). Quote
PaulSelden Posted February 25 Posted February 25 I am having exactly the same problem, but on Mac OS 15.4 Beta (24E5206s) on Intel MacBook Pro, Affinity 2.6.0 (3134) Paul Quote
MikeTO Posted February 25 Posted February 25 Where are you saving to? Please ensure Affinity has access with Apple menu > System Settings > Privacy & Security > Files & Folders. Also have you tried a different location? For example, if you normally save to your Documents folder, have you tried your Desktop or vice versa? Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
Hans-Chr. Posted February 25 Posted February 25 Same issue with my MacBook pro i5 running 15.4beta . Affinity 2.6 programs are not able to save after changes. Under Privacy & security > Files and folders the Affinity programs is not visible at all. Quote
MikeTO Posted February 25 Posted February 25 I've seen 4 reports of being unable to save with the Sequoia 15.4 beta now. @DrMike You also reported this issue saving from the Sequoia 15.4 beta in another thread. Does your Mac have an Intel or Apple Silicon processor? Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
j_h Posted February 25 Author Posted February 25 [macOS 15.4 Beta] “Could not lock file” error or freeze when saving in Affinity Publisher 2 Description: Since updating my Intel iMac (Retina 5K, 27-inch, 2017) to macOS 15.4 Beta, Affinity Publisher 2 consistently fails to save documents—both newly created and older files. Sometimes I see the error “Could not lock file,” other times the app just hangs during the save dialog, forcing me to do a Force Quit. This issue happens regardless of the file’s location (local SSD, iCloud Drive, or external volume). I’ve tested in a new user account and in Safe Mode, but the error persists. On a MacBook Air (M3) running the same macOS 15.4 Beta, saving works normally, so it seems to be specific to my Intel iMac under this beta. Key points: macOS 15.4 Beta on Intel iMac (Retina 5K, 2017) Affinity Publisher 2, all updates applied Occurs with both new and existing .afpub files Error: “Could not lock file” or silent freeze during Save/Save As Requires Force Quit to recover Does not occur on my MacBook Pro (M3) with the same beta Troubleshooting done so far: Tried multiple volumes (local, external, iCloud) Reset app preferences, checked file permissions Tested new user account and Safe Mode Ran Disk Utility’s “First Aid” with no issues Rolled back to macOS 15.3.1 as a workaround (solves the issue) It appears to be a beta-related file locking bug on Intel Macs. Any suggestions or known workarounds would be greatly appreciated! Sedulius and MikeTO 2 Quote
DrMike Posted February 25 Posted February 25 Hi MikeTO. I am using a MacBook Pro with 2.4 GHz 8-core Intel Core i9. MikeTO 1 Quote
MikeTO Posted February 25 Posted February 25 Thanks @j_h and @DrMike. I hope the information you've shared with help Serif figure this out. Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
PaulSelden Posted February 26 Posted February 26 Just to confirm what I reported before and confirms what others are finding. My setup is: Intel MacBook Pro (2019) running Sequoia 15.4 beta (24E5206s), and Affinity Publisher 2.6.0 beta (3134). There are actually two problems related to the upgrade to Mac OS 15.4 on Intel. The first is critical: nothing can be saved. Any changes to the file and then Save (or Save As...) results in a hung progress bar. The second happens straight after the upgrade (it happened after the last upgrade); one file (not necessarily the same one), but not all, will not load for an hour or so. It does eventually. It suggests that Affinity is doing some complicated housekeeping in the background. Once it has loaded, everything is OK again (until the next upgrade). I hope Serif can sort this out very soon: without Save we are completely stuck. Thanks all! Paul Quote
Sedulius Posted February 26 Posted February 26 Exact same problem here with saving, although I haven't had any file loading issues. My Setup: MacPro 2019 3.5 GHz 8-Core Intel Xeon W running Sequoia 15.4 Beta (24E5206s) and Affinity Publisher 2 2.6.0. Thanks Oliver Quote
PaulSelden Posted February 28 Posted February 28 Just to confirm that this problem does not exist on MacBook Air with Apple chips. Paul Quote
Staff NathanC Posted February 28 Staff Posted February 28 I can confirm this issue is logged internally with the developers for further investigation, thanks all for providing additional info and device specs. j_h and transitdiagrams 2 Quote
transitdiagrams Posted March 1 Posted March 1 Seems to be only with Intel based processors in combination with MacOS - my M1 and M3 machines work perfectly fine with 15.4 beta. On the same Intel iMac I use bootcamp with the newest Windows 11 Insider Preview and it works without any issues. I know, different code base Quote PS: If you like maps you might also have a look at this community!PPS: Want to know more about me and my ways? Head over to an Affinity Spotlight article about me and my maps!PPPS: Do you love public transit and transit maps too? Then have a look at my home-made collection of transit maps under www.instagram.com/transitdiagrams or www.twitter.com/transitdiagrams. PPPPS: Other works than transit maps can be found here www.behance.net/chrisneuherz
PaulSelden Posted March 2 Posted March 2 Just this morning I am having the same problem with Affinity Designer. Paul Quote
Hans-Chr. Posted March 4 Posted March 4 I juts downloaded MacOs 15.4 beta 2. First test shows that the issue may be solved for this issue. Quote
transitdiagrams Posted March 4 Posted March 4 After installing 15.4. Beta 2 the issue is gone, Apple seems to have fixed the problem. 🙂 Quote PS: If you like maps you might also have a look at this community!PPS: Want to know more about me and my ways? Head over to an Affinity Spotlight article about me and my maps!PPPS: Do you love public transit and transit maps too? Then have a look at my home-made collection of transit maps under www.instagram.com/transitdiagrams or www.twitter.com/transitdiagrams. PPPPS: Other works than transit maps can be found here www.behance.net/chrisneuherz
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.