Tom Lachecki

You may need to do a Reset operation. I would try it this way:
Shutdown and restart your iPad. Start one Affinity V2 application. I suggest Publisher 2. Leave the others stopped. As the application starts, it will display a Splash Screen. With 1 finger, double-tap on the Splash Screen. This will give you a Clear User Data dialog. In that dialog, turn off the first option (Reset User Defaults), turn on the second option (Reset Assets), and turn on the 2nd from the end option (Reset Account Data (inc. Synced Content)). Press the Clear button. Open Account, select everything you want to install, and wait until it has finished downloading and installing. Then you can manually install your other Assets. Two more hints:
If you want to have your manually installed content in all 3 apps, there's a Preference, in General, to Link New Content Categories. Turn it on. Then you'll only have to install it once. If you tap the Publisher icon at the top left of the app's Home Screen, you'll find an Import Content action. This should allow you to select and import multiple .afassets files at one time (or any other kind of content, such as .afbrushes).

Thank you Walt.farrell, that did the trick. You saved my bacon. I used your extra hints too and they were a big help and time saver. It use to take me forever to reinstall my assets. 

IMPORTANT UPDATE for anyone still using Affinity V1 - 
Versions 1.10.6 of the Affinity suite have been released, which resolve these .NET Windows crashes.
Please see the below link for information on how to download and install these updates:
With the Affinity updates installed, you can now un-hide any previous Windows updates you have paused and install these without concern.

@CHerbst Welcome to the forums and sorry for the delay.
Would you be able to provide me a download link to the images you're using so I can test with them. Also if you just open one of the .CR3 files in the Develop persona and switch to the Lens panel, has a lens profile been auto applied and is it correct? As I want to make sure the data/info in part of the files metadata first.

I did a quick test before posting and the LUTs did move. I've got 15,000 installed on my work pc so I'll check tomorrow when I'm back in the office. I did log an improvement suggestion to be able to drag-drop folders of downloaded content which would auto-create the categories from folder names so I'll give that a nudge too. 

Hi @dradept
This has now been passed over to the devs for further investigation.

Yes, thank you - that helped me understand that things work diffenretly with the Universal License... I was fully expecting it would work like all Apple apps, iOS and Mac, work, you just hit restore in an app.
I am all set now, thanks for your help!

Hi @Pikzels, this is the automatic brightness adjustment issue—please see https://forum.affinity.serif.com/index.php?/topic/152108-m1-mac-monterey-affinity-photo-etc-now-has-the-wheel-of-death-quite-a-lot/page/2/#comments and I also did a video demonstrating how to fix it here:
 
Affinity Designer is exempt from the issue because by default it still uses an OpenGL view. The issue is with the Metal view used in Affinity Photo (querying the maximum EDR/HDR brightness for the 32-bit preview panel). Disabling "Automatically adjust brightness" in the macOS system preferences will fix the issue. Hope that helps!
 

FWIW, https://en.wikipedia.org/wiki/IPTC_Information_Interchange_Model suggests the IIM encoding format is still widely supported so hopefully AP will someday do that too.

Tom, thanks for the detailed reply.   

I think what you're saying is that the IPTC/IIM format is in some sense deprecated, however many photographers are heavily invested in it because our portfolios now go back many years, and we've submitted to stock sites in the past.  It may be that at some point there's a bullet we'll need to bite;  but we'd need some tool or batch operation to convert the metadata in hundreds of existing files.   I've done a bit of searching but haven't found such a tool. 
Reading the "older" format and writing a "newer" format might be fine - as long as the sites where I sell images will read the newer format.  Some of those sites are woefully out-of-date and receive only cursory updates.  I guess we'll find out, eventually.  
 

Hi @Nightshade,
This indicates a problem with the data file used for this service. Looking in the "user" folder (visible at the far right of your screenshot), is there a file named ws.dat? If so, please close the app, rename the file to ws.dat.bak, then re-open the app and try again.
If this fixes the problem, would you be willing to send over the ws.dat.bak file for analysis if we provide a Dropbox link?
If not, please provide the full path to the Application Support directory shown so we can work out why that data file isn't being created properly.
Thanks

An ISO number can be given on a number of different scales, ISO Speed being one and Standard Output Sensitivity being another.
If a high ISO Speed were found in the XMP (working around the upper bound for the field in EXIF data) we would be able to report it.
So for the most part I think we're showing the correct values in the correct place here, except that we could hide the out-of-bounds, placeholder ISO Speed value of 65535.

An ISO number can be given on a number of different scales, ISO Speed being one and Standard Output Sensitivity being another.
If a high ISO Speed were found in the XMP (working around the upper bound for the field in EXIF data) we would be able to report it.
So for the most part I think we're showing the correct values in the correct place here, except that we could hide the out-of-bounds, placeholder ISO Speed value of 65535.

Hello @branden.123 and welcome to the forums.
Sorry to say, but u have to pay again for the second account.
 

Cannot imagine why APub would have an issue with this file.
Who needs a correct XREF table?
Why would you need a correct contents reference for a PDF file you want to edit (not just display)?
Silly requirement.
Fun fact: the recovered/repaired PDF did open in APub.
Isn't that amazing!
 

I am attaching a free PDF called “Affinity Photo from Ten Thousand Feet.” This is a 41 page book that explains many of the concepts and questions that forum members ask frequently.
Much of the information is based on presentations given to my local photography club. Some of it is based on a series of articles written for the club’s newsletter. Much of the book is newly written material, based on years of working to understand digital photography, how color works, and how Affinity Photo fits into that picture.
Please enjoy the book. All I ask in return is that you look it over and leave a comment.
Affinity_Photo_from_Ten_Thousand_Feet.pdf

@William Overington, I'm pretty sure that Processing is a much more suited tool for your proposed use case than any of the Affinity programs. It's not Pascal, but programmable non the less.
BTW, I first learned about Processing in Brendan Dawes excellent book “Analog In, Digital Out” (2006).

Hi EBT!
If you want to have enduring access to the additional stuff from Affinity (Assets, Brushes, Fonts...), copy this config-file to the following path: C:\Users\YourName\AppData\Roaming\Affinity\Photo\1.0\ or, if your apps are from the Microsoft Store: C:\Users\YourName\AppData\Roaming\Affinity\Photo\1.0(Store)\ (for the other apps, replace "Photo" by "Publisher" or "Designer").
AppData is a hiiden folder, so if you haven't already done it, you need to make it visible in the Explorer. Click on "View" on the top of the Explorer and set a hook at something like "Hidden Elements" or so on the right side (don't know how it is called in english. Then the folder "AppData" should appear.
If you start your apps after that, you should be able to sign in/register.

Great! That worked.The complete path is
%AppData%\Roaming\Affinity\Photo\1.0\
or
%AppData%\Roaming\Affinity\Photo\1.0(Store)\ for the apps from the Microsoft Store. But after I placed the config files there it works now.
Thanks a lot!!!

This looks like text with an outwardly aligned white outline.

Afraid not. It is true that most LCP profiles are those that ship with Adobe products. If you have access to those, and wish to use them, you should of course be sure to abide by Adobe's licensing restrictions/terms & conditions. There may be some "custom" lens profiles online in LCP format, though most are usually found in the LensFun XML format.

Thank you so much for the fix. I’ve updated to 1.10.2 and looks like the brushes are sticking this time 👏👏👏

Hello @dialynn and welcome to the forums.
If you have purshased the software at the Microsoft store you don't need a key. You need only to download and install the software from the Microsoft store.
If you have registered the publisher with Serif and no longer know the account details, contact affinity@serif.com.
 

Because, from experimentation, Publisher is using the first 4096 bytes of the file to determine the file encoding. If nothing in the first 4096 bytes requires UTF-8 encoding, then Publisher is assuming the file to be using ANSI encoding rather than UTF-8, and interprets the rest of the file in ANSI mode rather than UTF-8 mode.
The first é, which is the first UTF-8 encoded character, is at position 4523 in that file. Therefore Publisher has decided the file is ANSI-encoded.
Edit: And any changes that shorten the file and bring that first é into the first 4096 characters will resolve the problem. As would adding some UTF-8 character to some other location, such as within the header line at the top of the file.

Make sure you click on the image to get the real image (not the "thumbnail") before you download it. You should see significantly more metadata that way.