Patrick Connor

We are pleased to announce an update for the iPad release of Affinity Designer 2 for iPad, version 2.4.2 The changes in Affinity Designer 2 for iPad 2.4.2 are listed in this FAQ forum post: Those are the changes made since the last release Affinity Designer 2 for iPad 2.4.0 & 2.4.1 To get notified when any new releases are made please follow the latest releases thread by clicking here UPDATING TO THIS VERSION (which is free for all V2 users) The software version can be seen in the bottom left the corner of preferences screen. Your Affinity iPad apps should update automatically next time you run them. However, you do need to be logged in with the same Apple ID you used to buy them. If the automatic update does not happen for you, go to the iPad Store app and go to Updates. Once you’re there, tap near the top of the screen where it states 'Updates' and then hold, pull down and then release. This should manually refresh the updates page. However, don’t panic if the updates are not available for you yet—Apple sometimes phase roll outs around the world and this can take up to 24 hours.

All Readers This thread is solely for commenting on this announcement. Please do not post bugs or problems that you find when using this version of the software in this thread, instead make a new thread in the V2 Bugs found on iPad section and questions about usage go in the iPad Questions forum.

We are pleased to announce an update for the iPad release of Affinity Photo 2 for iPad, version 2.4.2 The changes in Affinity Photo 2 for iPad 2.4.2 are listed in this FAQ forum post: Those are the changes made since the last release Affinity Photo 2 for iPad 2.4.0 & 2.4.1 To get notified when any new releases are made please follow the latest releases thread by clicking here UPDATING TO THIS VERSION (which is free for all V2 users) The software version can be seen in the bottom left the corner of preferences screen. Your Affinity iPad apps should update automatically next time you run them. However, you do need to be logged in with the same Apple ID you used to buy them. If the automatic update does not happen for you, go to the iPad Store app and go to Updates. Once you’re there, tap near the top of the screen where it states 'Updates' and then hold, pull down and then release. This should manually refresh the updates page. However, don’t panic if the updates are not available for you yet—Apple sometimes phase roll outs around the world and this can take up to 24 hours.

All Readers This thread is solely for commenting on this announcement. Please do not post bugs or problems that you find when using this version of the software in this thread, instead make a new thread in the V2 Bugs found on iPad section and questions about usage go in the iPad Questions forum.

We are pleased to announce an update for the iPad release of Affinity Publisher 2 for iPad, version 2.4.2 The changes in Affinity Publisher 2 for iPad 2.4.2 are listed in this FAQ forum post: Those are the changes made since the last release Affinity Publisher 2 for iPad 2.4.0 & 2.4.1 To get notified when any new releases are made please follow the latest releases thread by clicking here UPDATING TO THIS VERSION (which is free for all V2 users) The software version can be seen in the bottom left the corner of preferences screen. Your Affinity iPad apps should update automatically next time you run them. However, you do need to be logged in with the same Apple ID you used to buy them. If the automatic update does not happen for you, go to the iPad Store app and go to Updates. Once you’re there, tap near the top of the screen where it states 'Updates' and then hold, pull down and then release. This should manually refresh the updates page. However, don’t panic if the updates are not available for you yet—Apple sometimes phase roll outs around the world and this can take up to 24 hours.

Thank you all for your help with this

Thanks, because 2.4.2.2371 removed the help and 2.4.2.2374 put it back I think the usual "small patch" (delta only) process failed.

If we cannot replicate a customer reported issue, and nor can other forum members, we cannot write an adequate report as the recipe is inadequate. If we made an inadequate report there is almost no way for the developers to fix a problem either. Sometimes a problem is so common that we do make a report with a note that we "cannot yet reproduce" but it is very unlikely to be picked up by any developer, but that is only when many customers report the same thing and therefore we are simply missing a key element of the recipe.

We will have another go at fixing this in the next round of betas, hopefully with you next week or the week after. Thanks for your input on this

This post covers the main bug fixes that are included in 2.4.2. The fixes are organised by operating system. (A) Bug fixes which affected all platforms Export Preview does not correctly display results when using Rasterise = Nothing AF-2284 .CR2/CR3 images import with desaturated/washed out colours when switching between RAW engines (B) Bug fixes which affected Desktop (Windows and macOS) Customer .docx file placed within a text frame in a new doc gives "Failed to Save" message. AF-2158 Tables: Update from Selection on Default format enables 'Delete' causing app to crash when deleting format. AF-2142 (C) Bugs fixed which specifically affected Windows Pixel and Pixel Grid gridlines are thicker in v2.4. AF-2167 Attempt to fix RAW files having Artefacts when opened. AF-2178 Crash when changing between Light and Dark UI with stroke panel and unselected curve on page. Crash - adding pages from files and specifying a section to add. Layers panel: layer drop zones broken. AF-2394 Can't undo live filter or adjustment layer creation. AF-2265 CTRL modifier for boolean Add now makes compounds. AF-2432 Grids fail to instantly update on document when modified. AF-2224 Using a keyboard shortcut for Geometry > Add results in a compound shape as if ctrl \+ add was clicked. AF-2444 Builds on arm devices failing to render documents with OpenCL enabled. AF-2173 (D) Bugs fixed which specifically affected macOS Crash when dropping Promised files into a document. AF-2264 Threadlock opening documents on some devices. AF-2264 Crash clicking Regular Expressions with the layer name text field active. AF-2139 Mac Apps crash when an image is dragged and dropped from a Zip file. AF-2264 Certain RAW images render in black and white when developed AF-2179 (E) Bugs fixed which specifically affected iPad "Lessons" tab name changes to "Samples" after opening settings. Affinity Windows applications include the fixes in lists (A)+(B)+(C) (A) Bugs fixes affecting All Apps + (B) Bug fixes affecting desktop Apps + (C) those fixes affecting Windows Affinity macOS applications include the fixes in lists (A)+(B)+(D) (A) Bugs fixes affecting All Apps + (B) Bug fixes affecting desktop Apps + (D) Bug fixes affecting macOS Affinity iPad applications include the fixes in list (A)+(E) (A) Bugs fixes affecting All Apps + (E) Bug fixes affecting iPads. If you have reported a bug and it is not yet fixed, please do not report it again. More fixes will be made in the forthcoming 2.5 beta cycle.

The 2.4.1 update is explained here as it only changes one thing and 2.4.2 will follow shortly including fixes.

Hi All, We have just made a build available of a 2.4.2 beta live - version 2.4.2.2371 - This was created to address issues found after the release of 2.4.0 & 2.4.1 This is now available to you on auto update (now or very soon). The fix list for this build is here We have decided against implementing the macOS help change in this beta cycle, so the installed macOS help has been reinstated

Here's a list of the bugs which have been fixed in the beta build 2.4.2 (2371) (fixes since the post above for 2.4.2.2356) Please reply in this forum to comment on any fixes which are in this list (in particular to let us know if you notice that something we say is fixed isn't!) To report any new bugs please do that against the relevant new feature post, or if unrelated to new functionality in the Other bugs & issues forum. Changes/Bugs affecting all platforms .CR2/CR3 images import with desaturated/washed out colours when switching between RAW engines AF-2212 Bugs affecting Desktop (Windows and macOS) none in this build Bugs affecting Windows Crash whilst dragging Mask and adjustment layers in layer stack . AF-2598 Bugs affecting macOS Certain RAW images render in black and white when developed AF-2179 Bugs affecting iPad none in this build.

Sorry, that's my mistake. Each dev cycle has always taken as long as it needs. Normally beta cycles are more than 6-8 weeks and less than 20 with some time between beta cycles for patching. There's no hard and fast rule how often, how long or how many. There never has been, so nothing has changed.

The testing team have agreed with the Documentation team that this change not yet ready for public release and the installed help will be returning in the next 2.4.2 beta build and the customer release. We do still have plans to move all the software help to be sourced from online content and to enrich it with videos and other improvements, but that will likely come in 2.5 or 2.6. Thanks for your input in this thread it will go some way towards making the eventual change much better for all users

We expect to start 2.5.0 beta during April.

I personally chose to change the name. I nearly called it "Info Bot" but I think "Affinity info bot" is clearer and more authoritative. It is "early in the acquisition process" , but it's nevertheless in the past. Serif/Affinity was acquired by Canva 2 weeks ago, and announced publicly 1 week ago. I think the service agent meant nothing has changed so far. Furthermore nothing is due to change. Beta cycles will be the same as for 2.3 and 2.4, new features, improvements and larger fixes in point releases (x in 2.x.y) and bug fixes to address regressions in patch releases (y in 2.x.y). The 2.5.0 beta cycle will start very soon after 2.4.2 patch is released, likely in April

AI related/specific posts are now here. Obviously they spun off things that were said here but this is not for the discussion of AI

Can you please let this go now

This is still true and moderators will hide disagreement between users, whilst not stopping discussion

They did. The head of Flourish came to Serif recently and recounted a very positive experience when Flourish were purchased by Canva.

Oh dear. We are not completely sure this was 100% resolved so sounds like this 2.4.2 beta is not all of the solution. Thanks for coming back and sharing

@adefemioluwatobi Welcome to the Affinity forums We do not allow users to promote themselves on these forums, so I modified your post. Also a jpeg of your work might show more people what it's like

Actually the dev may have used Safari, not "default" I have checked the code but will ask the dev to confirm and modify my post after Easter