Patrick Connor

Here's a list of some of the bugs which have been fixed in the RC build 2.1.1.1847 
Please reply in this forum only 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.
Bugs affecting all platforms
Help updates  PDF imports with unsupported characters for the 'Subject' field, then fails to export out to PDF [AFB-7775]  Crash when enabling document Baseline Grid due to Running Headers on Master Pages [AFB-7762]  Crash applying a Paragraph Style to a Running Header within a small text frame. [AFB-7743]  Non-breaking hyphens no longer render compared to 2.0.4, though does not affect ALL fonts [AFB-7739]  Crash adding pages into a facing page document with flowing text [AFB-7725]  Bugs affecting Desktop (Windows and macOS)
'Title' and 'Description' fields are not read from the XMP sidecar files. [AFP-6194]  Batch Processing RAW files creates incredibly dark results [AFP-6187]  Data Merge sources stored on a Cloud drive can crash the app when deleting data source [AFB-7793]  Bugs affecting Windows
Export dialog correctly handling transparency again [AFP-6199] [AFP-6164]  Cropping in the develop persona does not visually apply crop [AFP-6183]  Changing the Opacity of an object via the Colour panel dropdown fails to visually update the object on the canvas. [AFD-6615]  Fields Panel- changing the contents without pressing enter causes the fields to clear when enter is next pressed in a field [AFB-7746]  Bugs affecting macOS
NIK Collection: Crash when closing app after Colour Efex [AFP-6148] {REQUIRES A RELEASE BUILD} Crash after deleting a template file [AFB-7747]  Bugs affecting iPad
Version number in iPad settings is full version number not just build [PD-671]  Stroke width cannot exceed 100 in any unit in Stroke Panel [AFD-6589]  NOTE: The 2.1.1.1847 iPad betas builds for Designer 2 and Publisher 2 are available in Testflight now and Photo 2 iPad beta 2.1.1.1847 will follow shortly (once Apple wake up in the US and approve it)

Here's a list of some of the bugs which have been fixed in the RC build 2.1.1.1847 
Please reply in this forum only 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.
Bugs affecting all platforms
Help updates  PDF imports with unsupported characters for the 'Subject' field, then fails to export out to PDF [AFB-7775]  Crash when enabling document Baseline Grid due to Running Headers on Master Pages [AFB-7762]  Crash applying a Paragraph Style to a Running Header within a small text frame. [AFB-7743]  Non-breaking hyphens no longer render compared to 2.0.4, though does not affect ALL fonts [AFB-7739]  Crash adding pages into a facing page document with flowing text [AFB-7725]  Bugs affecting Desktop (Windows and macOS)
'Title' and 'Description' fields are not read from the XMP sidecar files. [AFP-6194]  Batch Processing RAW files creates incredibly dark results [AFP-6187]  Data Merge sources stored on a Cloud drive can crash the app when deleting data source [AFB-7793]  Bugs affecting Windows
Export dialog correctly handling transparency again [AFP-6199] [AFP-6164]  Cropping in the develop persona does not visually apply crop [AFP-6183]  Changing the Opacity of an object via the Colour panel dropdown fails to visually update the object on the canvas. [AFD-6615]  Fields Panel- changing the contents without pressing enter causes the fields to clear when enter is next pressed in a field [AFB-7746]  Bugs affecting macOS
NIK Collection: Crash when closing app after Colour Efex [AFP-6148] {REQUIRES A RELEASE BUILD} Crash after deleting a template file [AFB-7747]  Bugs affecting iPad
Version number in iPad settings is full version number not just build [PD-671]  Stroke width cannot exceed 100 in any unit in Stroke Panel [AFD-6589]  NOTE: The 2.1.1.1847 iPad betas builds for Designer 2 and Publisher 2 are available in Testflight now and Photo 2 iPad beta 2.1.1.1847 will follow shortly (once Apple wake up in the US and approve it)

Here's a list of some of the bugs which have been fixed in the RC build 2.1.1.1847 
Please reply in this forum only 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.
Bugs affecting all platforms
Help updates  PDF imports with unsupported characters for the 'Subject' field, then fails to export out to PDF [AFB-7775]  Crash when enabling document Baseline Grid due to Running Headers on Master Pages [AFB-7762]  Crash applying a Paragraph Style to a Running Header within a small text frame. [AFB-7743]  Non-breaking hyphens no longer render compared to 2.0.4, though does not affect ALL fonts [AFB-7739]  Crash adding pages into a facing page document with flowing text [AFB-7725]  Bugs affecting Desktop (Windows and macOS)
'Title' and 'Description' fields are not read from the XMP sidecar files. [AFP-6194]  Batch Processing RAW files creates incredibly dark results [AFP-6187]  Data Merge sources stored on a Cloud drive can crash the app when deleting data source [AFB-7793]  Bugs affecting Windows
Export dialog correctly handling transparency again [AFP-6199] [AFP-6164]  Cropping in the develop persona does not visually apply crop [AFP-6183]  Changing the Opacity of an object via the Colour panel dropdown fails to visually update the object on the canvas. [AFD-6615]  Fields Panel- changing the contents without pressing enter causes the fields to clear when enter is next pressed in a field [AFB-7746]  Bugs affecting macOS
NIK Collection: Crash when closing app after Colour Efex [AFP-6148] {REQUIRES A RELEASE BUILD} Crash after deleting a template file [AFB-7747]  Bugs affecting iPad
Version number in iPad settings is full version number not just build [PD-671]  Stroke width cannot exceed 100 in any unit in Stroke Panel [AFD-6589]  NOTE: The 2.1.1.1847 iPad betas builds for Designer 2 and Publisher 2 are available in Testflight now and Photo 2 iPad beta 2.1.1.1847 will follow shortly (once Apple wake up in the US and approve it)

Following the release of version 2.1.0 of the Affinity suite, we have fixed a number of problems that were discovered after it's release. A full list of the fixes are found in this post and we would appreciate you installing this beta build and confirming that this version works as well for you as 2.1.0 but with those issues addressed. 
We are hoping that no newly introduced bugs are discovered in this 2.1.1 beta and if nothing significant is discovered we are likely to do a full release of 2.1.1 to all customers very soon. Please report any problems you find in this Beta bugs forum
2.1.1.1847 is now available as a beta either as an update from the last beta (2.1.0.1799/1806) or as a full download from the beta entitlement in your account. If you have not already done so please help make our apps better by joining our beta program!
NOTE: The 2.1.1.1847 iPad betas builds for Designer 2 and Publisher 2 are available in Testflight now and Photo 2 iPad beta 2.1.1.1847 will follow shortly (once Apple wake up in the US and approve it)
Thanks
Patrick

Here's a list of some of the bugs which have been fixed in the RC build 2.1.1.1847 
Please reply in this forum only 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.
Bugs affecting all platforms
Help updates  PDF imports with unsupported characters for the 'Subject' field, then fails to export out to PDF [AFB-7775]  Crash when enabling document Baseline Grid due to Running Headers on Master Pages [AFB-7762]  Crash applying a Paragraph Style to a Running Header within a small text frame. [AFB-7743]  Non-breaking hyphens no longer render compared to 2.0.4, though does not affect ALL fonts [AFB-7739]  Crash adding pages into a facing page document with flowing text [AFB-7725]  Bugs affecting Desktop (Windows and macOS)
'Title' and 'Description' fields are not read from the XMP sidecar files. [AFP-6194]  Batch Processing RAW files creates incredibly dark results [AFP-6187]  Data Merge sources stored on a Cloud drive can crash the app when deleting data source [AFB-7793]  Bugs affecting Windows
Export dialog correctly handling transparency again [AFP-6199] [AFP-6164]  Cropping in the develop persona does not visually apply crop [AFP-6183]  Changing the Opacity of an object via the Colour panel dropdown fails to visually update the object on the canvas. [AFD-6615]  Fields Panel- changing the contents without pressing enter causes the fields to clear when enter is next pressed in a field [AFB-7746]  Bugs affecting macOS
NIK Collection: Crash when closing app after Colour Efex [AFP-6148] {REQUIRES A RELEASE BUILD} Crash after deleting a template file [AFB-7747]  Bugs affecting iPad
Version number in iPad settings is full version number not just build [PD-671]  Stroke width cannot exceed 100 in any unit in Stroke Panel [AFD-6589]  NOTE: The 2.1.1.1847 iPad betas builds for Designer 2 and Publisher 2 are available in Testflight now and Photo 2 iPad beta 2.1.1.1847 will follow shortly (once Apple wake up in the US and approve it)

Following the release of version 2.1.0 of the Affinity suite, we have fixed a number of problems that were discovered after it's release. A full list of the fixes are found in this post and we would appreciate you installing this beta build and confirming that this version works as well for you as 2.1.0 but with those issues addressed. 
We are hoping that no newly introduced bugs are discovered in this 2.1.1 beta and if nothing significant is discovered we are likely to do a full release of 2.1.1 to all customers very soon. Please report any problems you find in this Beta bugs forum
2.1.1.1847 is now available as a beta either as an update from the last beta (2.1.0.1799/1806) or as a full download from the beta entitlement in your account. If you have not already done so please help make our apps better by joining our beta program!
NOTE: The 2.1.1.1847 iPad betas builds for Designer 2 and Publisher 2 are available in Testflight now and Photo 2 iPad beta 2.1.1.1847 will follow shortly (once Apple wake up in the US and approve it)
Thanks
Patrick

Following the release of version 2.1.0 of the Affinity suite, we have fixed a number of problems that were discovered after it's release. A full list of the fixes are found in this post and we would appreciate you installing this beta build and confirming that this version works as well for you as 2.1.0 but with those issues addressed. 
We are hoping that no newly introduced bugs are discovered in this 2.1.1 beta and if nothing significant is discovered we are likely to do a full release of 2.1.1 to all customers very soon. Please report any problems you find in this Beta bugs forum
2.1.1.1847 is now available as a beta either as an update from the last beta (2.1.0.1799/1806) or as a full download from the beta entitlement in your account. If you have not already done so please help make our apps better by joining our beta program!
NOTE: The 2.1.1.1847 iPad betas builds for Designer 2 and Publisher 2 are available in Testflight now and Photo 2 iPad beta 2.1.1.1847 will follow shortly (once Apple wake up in the US and approve it)
Thanks
Patrick

Following the release of version 2.1.0 of the Affinity suite, we have fixed a number of problems that were discovered after it's release. A full list of the fixes are found in this post and we would appreciate you installing this beta build and confirming that this version works as well for you as 2.1.0 but with those issues addressed. 
We are hoping that no newly introduced bugs are discovered in this 2.1.1 beta and if nothing significant is discovered we are likely to do a full release of 2.1.1 to all customers very soon. Please report any problems you find in this Beta bugs forum
2.1.1.1847 is now available as a beta either as an update from the last beta (2.1.0.1799/1806) or as a full download from the beta entitlement in your account. If you have not already done so please help make our apps better by joining our beta program!
NOTE: The 2.1.1.1847 iPad betas builds for Designer 2 and Publisher 2 are available in Testflight now and Photo 2 iPad beta 2.1.1.1847 will follow shortly (once Apple wake up in the US and approve it)
Thanks
Patrick

Since this is working now I've updated the Nik collection to V6.1.
 

Nik 6.1 update fixes problems with Affinity 2.1.
I've tried it with ColorEfex, Viveza and Silver Efex. All work perfectly with Affinity Photo 2.1
Feel free to upgrade folks! 🙂

Hi @grabuge,
So the issue with the roll up.pdf is the same as mentioned above in that for some unknown reason pixelart printing include a zero width no-break space at the start of most of the metadata fields, denoted by the Hex reference FEFF...

The zoning.pdf has no Subject but again it does have a zero width no-break space which is causing the error when exporting the file...

The workaround for both files is as @Patrick Connor and @Dan C mention above, to go to Window > References > Fields in Publisher (assuming you have Publisher), then mouse click in the Subject field, hit Delete followed by Enter, then both files will export to pdf...
In case you don't have Publisher I've re-exported both pdf files and have attached them here, so hopefully these will work for you but if not just let us know...
roll up export.pdf
zoning export.pdf

Thanks @Hangman that's very helpful information indeed.
@Dan C
Please make an additional bug report on the failure to import these fields correctly, which then exposes the export bug (Note, even if these characters start importing correctly from this sort of file, the export bug will still needs fixing for when these sort of characters are pasted into the fields values for example)

Thanks @Hangman that's very helpful information indeed.
@Dan C
Please make an additional bug report on the failure to import these fields correctly, which then exposes the export bug (Note, even if these characters start importing correctly from this sort of file, the export bug will still needs fixing for when these sort of characters are pasted into the fields values for example)

Hi @Dan C and @Patrick Connor,
So, it turns out the cause of the pdf export bug is quite straightforward... it's caused when using either a zero width no-break space and/or accented characters in the Subject field of an Affinity Publisher document...
Taking a look at the pdf template file metadata for the files uploaded by @Thomas Serafini which were downloaded from pixartprinting, when you look at the Subject entry, (shown as Template in Acrobat), the template itself uses Hex code to define the majority of fields...
At the start of most fields, i.e., Creator, Title, Author and Subject, the Hex code starts with FEFF which is the Hex code for a zero width no-break space. When included in the Subject field of an Affinity Publisher document you will see The file could not be created error message when attempting to export an opened pdf file.
Note 1: This only affects the Subject field in Publisher, other fields using zero width no-break space or accented characters are not affected...
Note 2: On macOS, if the Subject field is populated with either a zero width no-break space or accented character, when the exported pdf is opened in Publisher the Subject field appears to be empty, I'm assuming on Windows this is where the two empty (rectangle) characters are displayed?

Note 3: Please excuse the apparent 'pauses' during the screen recording, this is down to fans kicking in (something to do with the excessive UK heatwave we're enjoying at the moment, read 20°C or maybe just poor QT performance on Intel Macs in general)... 🌞

zero width pdf bug.mp4  

If you are a new arrival to this thread and have found that it is locked but still want to show your support for Affinity on Linux, simply like this post

No problem at all!
Inspecting the files in Acrobat, it appears as though these PDFs were created by 'PixartPrinting S.P.A' in an application that was not Affinity, hence the PDF library used is not Affinitys.
I too am curious as to the users exact workflow, as I have imported their PDF into Publisher 2.0.4, where the Fields are not imported, then saved the .afpub file and opened this in 2.1.0. This file then exports as expected in 2.1.0, as the Subject Field was never imported

Be aware that the default behaviour for 'Searching' has changed to be context aware - when viewing an existing thread the search will default to 'This Topic' which may cause some confusion or empty results. You can change the area you're searching before you search from the dropdown under the 'More Search Options > Content Type' setting as previous.

yes hence the wording "when viewing an existing thread the search will default to 'This Topic'"

This was just a quick one that I decided to do for a futurism section on reddit a little while back. Really could do with a couple of adjustments that I will do sometime. Shock horror the AI crowd piled in proclaiming it was generated which seems to be the way now if it’s more complicated than a stick man. No point in trying to argue your case on there as they always know best.

Patrick, thanks for your calm replies to this heated thread, and add to it another calm request from a long-time user who's just getting started in a new application of their design skills, and would really appreciate the addition of DXF export and the accompanying reduction of trips to other packages as midway hops in a never-ending sea of unitless formats and differing interpretations of fine detail my work now entails.
---
For all of you slinging fierce barbs at people you don't know or slinging them right back at other people you also don't know, it's not a good look. You know little about other's situations, or how they may have come to the point they're at. As an example, I've paid for and used both versions of all three of these wonderful apps, typeset a full book for a friend as a starter project, used it as my 'home solution' for years because it was (and remains) affordable and excellent, and only recently picked up laser cutting and CNC routing. It's at this point that I now need DXF, so free trials or paid trials or demo versions or anything else wouldn't work for my particular situation, now would I have known about this in advance (because of a lack of concurrence of events called 'time' or 'life'). I'm here now, asking for a thing that does exist but doesn't exists here, and trying to do so in a respectful and kind manner. I've also found solutions to all the issues which are being presented, but none of them are easy or pretty, so I still think it's a valid ask. Plus, by asking, developers such as Patrick and others at Serif get better information about how people both use their products, and wish to use their products. 
Bottom line: I'm here now, and would like to request this feature please, for all the good reasons stated before, and it's not 100% critical but it is a real and major factor in my workflow.
Honestly have no idea where the vitriol is coming from, other than 'the internet', 'these days', and 'people'. Did I miss 'feature request'? How does that even work? Sheesh.
Lastly, for any of you working with equipment you own or manage directly, try Lightburn, and try using PDF as an intermediary. It's certainly not CAD, but as a workflow it is simple and maintains scale correctly. Results in my experience have been indistinguishable, however it obviously requires paid software and a small amount of testing, so it might not work in all situations. Hopefully it will help some, and if not, create a bit of interesting vitriol itself for daring to be… suggested. *wink, wink*

This is not a bug, @BBG3, but the way the Affinity applications are designed to work. The formatting characteristics of the first character apply to the bullet/number, too.
To avoid that, note that in the Bullets and Numbering settings (Paragraph panel, or Paragraph Text Style) there is a field for a Character Text Style that will be applied to the Bullet/Number. So:
Define a Character Text Style for the Bullet/Number that you want to use. Specify that Character Teat Style in the Bullets and Numbering section of the Paragraph panel or the Paragraph Text Style you're using for the text. Then format the first character of the text as you want it. (I'm away from the computer, and can't provide a screenshot at the moment. The field (though not its usage) is described in the Help, though not shown. https://affinity.help/designer2/en-US.lproj/pages/Panels/paragraphPanel.html

Dan:
I do believe there is something that Affinity can do to help  prevent this from occurring. A simple statement "Please note: do not mix installers between MSIX and MSI for Affinity software (Designer, Photo, and/or Publisher) on Windows systems as this will cause activation problems and require removal and clean installation." inserted in the circled area might help prevent this. Thanks for your help,
 
Kevin

If someone in the Scripting development team at Affinity could answer me this, it would be great.
In other applications I use, that allow for scripting (mainly, Cinema 4D and VizRT), besides being able to create scripts that can be executed from a menu listing (Cinema 4D, only), I can also attach a kind of a "tag" to an object that runs scripting code in real time, whenever the scene/document is changed/refreshed.
That way, I can perform scripting operations on the object that the "tag" is attached and also on its children.
Will Affinity scripting abilities only allow for scripts that can be invoked from a menu or will we have a new type of "tag" to attach to our "layers/objects" that can allow us to add abilities/behaviours to any "layer/object"?
Something like my mockup...
 

With the roll out of Affinity Designer/Photo/Publisher for Windows version 2.0.4, Serif are making available Unsandboxed installers (also known here as MSI/EXE installers). These installers will be made for all future V2 release builds going forward and will autoupdate from within the application (checking for updates on each run, like the sandboxed version does)
Serif do not recommend or support mixtures of MSIX and MSI on the same computer. You should only use either all sandboxed or all unsandboxed,  particularly if you have more than one Affinity V2 application installed.
You can now download (and install) Windows unsandboxed MSI/EXE installer files (as well as Windows sandboxed MSIX installer files) from these store pages.
1. From the  V2 Universal Download page
 

Click on the words "Looking for Windows MSI installers?"
 

2. Individual V2 application Download pages, found here
Affinity Designer 2
Affinity Photo 2
Affinity Publisher 2
Click on "Also available EXE (size MB)" 

3. LICENCES AND DOWNLOADS pages in your account
 

Click on the words "Looking for Windows MSI installers?"

2.1.0 Bug Fixes
This post covers the main bug fixes that are included in 2.1.0. The bug fixes are organised by operating system.
(A) Bug fixes which affected all platforms 
App occasionally hangs when zooming Boolean Operations improved resulting in many fixes AFFonts can now be streamed from Affinity Store Improved Kerning support - GPOS type 8 chaining contextual lookups now supported.  Opening some files caused the app to crash Hang can occur when deleting object styles Warp Group exported to PDF results in clipped objects Shape Builder Tool instant crash hitting return on Symbols [Designer] All keyboard input broken after altering table line/fill settings [Publisher] .GPR (GoPro RAW) files fail to open with 'File Type Not Supported' error Metadata Panel - EXIF 'Date Shot' field incorrectly re-applies the local OS time offset for images lacking timezone data [Photo] Transform Origin is moved after adjusting the height/width of an object or flipping it Canon multiple exposure RAW file loads with pink overlay when using Serif LABs Line Objects report X/Y values incorrectly in the Transform Panel Improved Linear DNG processing [Photo] Drawing a new table does not take selected font into account [Publisher] Object changes page based on centre of bounding box and not cursor position [Publisher] Stock Panel - Pixabay has lost the vector option Some specific lens profile changes [Photo] Updated Libraw to 0.21.1 release Many other fixes Translation Improvements Help file improvements (B) Bug fixes which affected Desktop (Windows and macOS)
Being prompted to save TIFF with layers or Save As even though only contains Background layer [Photo] Inconsistent behaviour when renaming and undoing renaming of swatches, warning shown in UI is not always applicable Sidenotes set 'Towards / Away from Spine' that are long enough to cover one another are hidden, or displayed on the last page incorrectly Copying non-destructive RAW layer and pasting into a separate document renders the RAW layer invisible in the original RAW file Typographic apostrophe OR certain other characters followed by an accented character pastes incorrectly into external apps Deleting a (shared) [brush/asset] category in App 1 while editing a styles name in App 2 can crash App 2 Pixel Brush Tool fails to output if using Accumulation or Flow Jitter when its not 100% File size in master doc increasing inexplicably with linked files Unable to scroll or use the arrows on the White Balance field in Develop Persona Brush accumulation fixed Opening and closing chapters in a book can leave the files locked and read only and stops book from being able to save, or close. Crash data merging if the source contains Cyrillic text Non Live Filters are prompting the app to ask if the user wants to save a TIFF with layers or flattened Fix for document specific crashes and hangs on load & print Changing the DPI of a document using any unit, other than pixels, cause the page to change size Tabbing in many dialogs/panels improved Spanish Hyphenation Dictionary updated Docx import improvements PDF Export fixes PSD Import fixes Knife tool improvements including Straight Line mode  Many other desktop fixes (C) Bugs fixed which specifically affected Windows
Preferences, User Interface, Light UI: UI Brightness and Text Contrast sliders reset to defaults when we restart the app Cannot change document DPI  Export Preview: WebP and JPEG XL formats do not zoom with the shortcut Export Preview: Some formats do not zoom with the shortcut RAW files open underexposed / dark [Photo] Font Manager - Fonts disappear after selecting substitute V2 MSI build doesn't currently work with Roaming Profiles Crash using Shape Builder with ' Clean up unused curves ' enabled Crash when using the Shape Builder tool, crash when marquee selecting with Shape Builder, crash when selecting Shape Builder tool Develop Persona: Opening 2x raw files at once doesn't save changes/edits after developing DAUB W&W - Bristles crashes app when selected from dropdown Long delay when calling the Edit Brush dialog. Performance improvements for problems encountered when using the application for a long time. Many other Windows specific fixes (D) Bugs fixed which specifically affected macOS
App attempts to reconnect to disconnected SMB share on launch [threads] New textured intensity brushes do not repeat with portrait images  Zooming in/out on a document (for example with Live Perspective) can intermittently cause a crash on (M1/M2) MacBooks Export Persona hang in Open and Save Panel Process when Exporting Slices Text Frame panel Unit control inches Grammarly for Desktop causes Publisher to crash when accessing the Find and Replace Panel Frequency Separation, destructive Gaussian Blur and High Pass: corruption/thin coloured lines Typing in certain fields removes the initial character Searching Stock Studio with no internet connection crashes apps, but should show a 'Connection Failed' error It was no longer possible to drag and drop layers/objects between documents. Live filters with blend mode treat 0% opacity as 100% Find and Replace fails to highlight special characters Many other macOS specific fixes (E) Bugs fixed which specifically affected iPad
Fonts installed from creative cloud show on context toolbar with name in Chinese  Anti-aliasing is broken with iPad System Settings > Display > Display Zoom > 'More Space' enabled UI could keep reappearing even after you entered full screen mode. Searching Stock Studio with no internet connection crashes apps Rulers don't stay hidden in preview mode & Hide rulers in full screen.  Brush Panel corruption can occur with multiple brush kits installed Blur Live filters: setting Radius to negative values crashes app. No Text Capitalisations options (etc) on iPad [Publisher] Live filters with blend mode treat 0% opacity as 100% If a document is closed on the iPad whilst editing an embedded file it will cause the document to fail to open again Searching Stock Studio with no internet connection crashes apps, but should show a 'Connection Failed' error No PDF options when opening a PDF file Drop down menus with checkable options no longer auto close UI improvements to Preferences/Settings Many other iPadOS specific fixes 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. These list are just the highlights of the many (300+) fixes made during the recent 2.1.0 beta cycle, which are listed in full in this post .
If you have reported a bug and it is not yet fixed, please do not worry or report it again. More fixes will be made in the forthcoming 2.2 beta cycle.