Colour management issue with TIFF file using ISO Coated V2 300%

[Hangman]

I'm unsure if it is related but it feels as though it may be, as it seems specific to @Optische Ausrichtung's post here -

I likewise have a CMYK Tiff file that uses the ISO Coated v2 300% (ECI) profile, exported from Affinity Photo. If I open in Affinity Publisher 2.2.0.2005 (Retail or Beta) when I have 'Convert open files to working space' and 'Warn' checked in the Colour Settings, if my Working Profile in Publisher is also set to ISO Coated v2 300% (ECI), the Publisher Assistant still pops up telling me it is converting the image to the Working Profile which in this instant it shouldn't need to as the Working Profile is the same as the image file being opened, but the image is being converted to the Working Profile set prior to setting a new Working Profile (if that makes sense)...

In v1.10.6 the behaviour is correct...

Sample Files

Tiff Files.zip

[Hangman]

Attached is my complete list of ICC profiles, I can confirm that I've not renamed any profiles and that all profiles work as expected in v1.10.6...

Colour Profiles (@Hangman).zip

[IllusionStudio]

Same issue on my designer, but in my case the software choose "japan color 2001 coated".

Please help us soon, I have to send the right files to my printing house immediately.

 

 

[Lee D]

Thanks @Hangman I've created a separate report for the issue but also linked it to the other profile issue as they seem to be related.

[Hangman]

Hi @Lee D,

Many thanks for creating a separate report for this issue and linking it to the other profile issue...

I don't know if you saw this update to the other thread which may or may not be relevant to the specific issue with this particular profile...

[Affinity Info Bot]

The issue "Opening TIFF using ISO Coated V2 300% profile applied" (REF: AF-392) has been fixed by the developers in internal build "2.3.0.2083".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.