Jump to content

Major bug on Affinity Publisher 2.5.0


Recommended Posts

Hi,

I encounter a major issue with AP 2.5.0 (with work to deliver on Monday, of course). Several documents can be opened, but cannot be edited at all. I cannot delete the pages, create new pages, write on them…

I can still create a new document which is editable.

If I try to quit the app, a rotating colour wheel appears which indefinitely rotates.

What should I do?

Link to comment
Share on other sites

  • Staff

Hi @LEB,

Would you mind trying this in the beta we released yesterday and seeing if you have the same results?  You can sign up for the beta here as we believe the beta should resolve this issue. 

Link to comment
Share on other sites

10 minutes ago, notabene34 said:

I have the same problem. impossible to continue work already started with the old version. Everything is blocked. On the other hand, I can reopen and edit a file made with a very old version of publisher...

You could try the Beta (as mentioned above). Or you could revert to 2.4.2:

Beyond that I'm not sure what to suggest, and I'm not familiar with the steps needed to revert as I haven't needed to try that on my Mac. Sorry.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Link to comment
Share on other sites

I am having same issue. Multi page (50+) document will not let me edit, etc. 1-3 page documents working fine. How do I revert back to the earlier version? Is the beta going to be released soon as an upgrade for this problem?

Link to comment
Share on other sites

Hi @dee17 and welcome to the forums,

You can follow the 'Previous Versions' links in this post to revert back to v2.4.2...

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

Hi @LEB and @dee17,

Please be aware there is a reasonably serious bug in the 2.5.2 Beta for macOS (which affects the 2.5.0 release version as well) logged under AF-3209 which results in an instant crash when right-clicking any Master page element on a Publication page...

It doesn't prevent 'Edit Detached' or 'Edit Linked' functionality but is perhaps just something to be aware of...

Note: This doesn't appear to affect the Windows versions...

If your project is time-critical it 'may' be better to roll back to v2.4.2 for now...

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

23 hours ago, LEB said:

I think you should release a fix asap.

Lack of patience does not pay off.

First of all everyone should calm down and what I think it is best, proceed as follow:

  1. If you haven't updated to version 2.5 yet. Please wait with the update. Continue your super important projects in the version you are currently using.

  2. If you experience serious issues after upgrading to version 2.5, please revert to version 2.4.2.

  3. Damn it, let @Patrick Connor and his team do their job and test. Otherwise, another patch will be needed to put out another new fire.

Thank you, thats all. Patrick, I'm calmly waiting for the problems to be sorted out. Regards🖐️

 

Link to comment
Share on other sites

We have similar issues after the 2.5.0. Update. After some research here in the forum I decided to go back to Version 2.4.2. - now I can work in my files again. 

In version 2.5.0 everything worked fine with new documents, but older files (from version 2.4.2.) would cause a crash. After clicking in a text frame (in a 5 page document) the whole program stopped working. Restarting Publisher or the whole mac could not solve the issue. 

Link to comment
Share on other sites

It's an issue I actually had before 2.5.0 already. Reverting to 2.3.1 from 2.4.2 then worked for me. Hoped it had been resolved in 2.5.0 but not.

Out of curiosity downloaded the beta 2.5.2 and that - so far - seems to work again. The documents that were unresponsive before so far work again as expected. Will do some more research and post back if there's anything to report.

 

Link to comment
Share on other sites

Thanks, Hangman and all, I rolled back to v 2.4.2 and everything is working fine. Have my work ready to go for tomorrow morning.

Another weird thing v 2.5.0 did was it would not quit, had to force quit it every time.

Link to comment
Share on other sites

Hi @dee17,

That's great to hear, I'm glad everything is working for you again and you're all prepared for tomorrow morning...

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

Same problem: I'm very, very annoyed!…
I wasted a day of work trying to work around these bugs!…

image.png.ce5c54503c120b2aeadf5e82e5479022.png

— Mac Mini M2 Pro 16 Go - 512 Go - macOS Sonoma 14.7 —

Link to comment
Share on other sites

23 hours ago, Hangman said:

If your project is time-critical it 'may' be better to roll back to v2.4.2 for now...

You should never update your current tools amidst "time critical" projects…
(Yes, also I once learned the hard way :83_smirk_cat:)

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

…in fact, Serif has not accustomed us to such bugs (have the teams changed since the “Canva Affair”?…).

I will exercise extreme caution in the future.

And also I blame myself for not having had the healthy reflex to consult this forum: I would have saved a lot of time.

— Mac Mini M2 Pro 16 Go - 512 Go - macOS Sonoma 14.7 —

Link to comment
Share on other sites

12 minutes ago, loukash said:

You should never update your current tools amidst "time critical" projects…
(Yes, also I once learned the hard way :83_smirk_cat:)

I normally am very wary however was hoping that 2.5.0 would solve this problem I had in 2.4.2!

 

 

Link to comment
Share on other sites

...besides, won't the coexistence of Affinity Publisher v2.4.2 with Affinity Photo and Affinity Designer v2.5.0 cause problems?...

— Mac Mini M2 Pro 16 Go - 512 Go - macOS Sonoma 14.7 —

Link to comment
Share on other sites

1 hour ago, BertD said:

was hoping that 2.5.0 would solve this problem I had in 2.4.2!

1 hour ago, sansnom said:

won't the coexistence of Affinity Publisher v2.4.2 with Affinity Photo and Affinity Designer v2.5.0 cause problems?

This is why I'm participating in the beta program.
Affinity's "release candidate 2" is usually identical to the final release. 

  • If there were unresolved issues that would hinder me by some means, I won't update. 
  • If I'd "desperately" need some of the new features, I have the "RC2" beta version next to the previous "stable" version handy.

MacBookAir 15": MacOS Ventura > Affinity v1, v2, v2 beta // MacBookPro 15" mid-2012: MacOS El Capitan > Affinity v1 / MacOS Catalina > Affinity v1, v2, v2 beta // iPad 8th: iPadOS 16 > Affinity v2

Link to comment
Share on other sites

I’ve been running 2.5.0 without any problems until noon today and then all hell broke loose. My file would load but wouldn’t respond. I decided to sign up for the beta and run that. The problem was , it said the file was open in another copy of Affinity Publisher - it wasn’t. As a reboot didn’t fix the problem, I uninstalled 2.5.0 so was able to load and edit my file in the beta. I’ve now reinstalled 2.5.0 but I am awaiting a an official release. None of this is nice.

Link to comment
Share on other sites

Hi @Catshill,

If you see, 'the file is already open in Affinity Publisher 2 (or Affinity 2 Customer Beta) on this device', if that is not the case it means the hidden 'Lock' file created when opening any Affinity Document hasn't been deleted... You can read about Lock files here...

Sometimes when the Affinity App crashes or the file fails to load properly the Lock file doesn't get deleted so despite the file not being open you still see this message when attempting to Open the file in a different version of the app, e.g., a Beta version.

To work around this, if you navigate to the folder where the file is located and then hit 'Command Shift Full Stop' on your keyboard this will show hidden files and allow you to delete the Lock file which will then mean the file can be opened again without the error message appearing.

Command Shift Fullstop can then be used to hide hidden files again.

Affinity Designer 2.5.5 | Affinity Photo 2.5.5 | Affinity Publisher 2.5.5
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Link to comment
Share on other sites

23 hours ago, sansnom said:

…in fact, Serif has not accustomed us to such bugs (have the teams changed since the “Canva Affair”?…).

I will exercise extreme caution in the future.

And also I blame myself for not having had the healthy reflex to consult this forum: I would have saved a lot of time.

I agree with @sansnom's statement. It would be interesting to understand how such a beautiful piece of software, with a competent team and a very broad and generous beta program could meet with such a failure.

Does this mean that important pieces of code were added at the last minute, which were not properly checked as part of the beta? Is it a new management to issue to accelerate a release in the context of the purchase by Canva?

In any case, I will also exercise extra caution in the future.

Link to comment
Share on other sites

3 hours ago, Hangman said:

To work around this, if you navigate to the folder where the file is located and then hit 'Command Shift Full Stop' on your keyboard this will show hidden files and allow you to delete the Lock file which will then mean the file can be opened again without the error message appearing.

Or, you should be able to simply wait 5 minutes. 

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Link to comment
Share on other sites

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.