Jon P

Option + [ and ] seem to be shortcuts that come from the OS for single/double quotes so override any custom shortcuts they are assigned to. An improvement would be for us to warn these are protected shortcuts when they are being assigned, which I can get logged

Ah yeah, I do indeed suspect this will have a similar root cause to the other issue, but will get it logged just to be sure. Thanks for the clarification

Thanks for the report @anto. It's now been logged that externally modified images aren't being detected.

I can reproduce the app not detected the image is modified, and marking it as such, so auto update modified linked images has no chance to work. I've passed along the bug. The re-linking issue i'm struggling to reproduce in isolation, can you just confirm if you: Move the image to another location - it will be marked as Missing in Resource Manager. Relink the image - nothing happens after you confirm the new folder. Without the other steps, that the re link fails?

The cause is if your document contains hyperlinks to emails/anchors, in the document you uploaded if you remove the hyperlink on RSVP it will export without an error (or export without hyperlinks or tagging enabled). It's logged with us and should hopefully be fixed in a future beta

Thanks @Jane P. Looks like the same issue @MikeTO has with his file, so I'll add it to the report I made for that.

Thanks @steday there's an improvement already in relating to the names of custom fields

Hi, thanks for the report. Can you attach the document here so I can look into this

Thanks @Hangman, I've reproduced and logged that

Crash reports for the betas (and retail if you remove (Beta) from the folder path) are: %userprofile%\.affinity\Photo\2.0 (Beta)\CrashReports

I believe this is what is maybe being referred to, but that's a fix for a crash replacing which is not what is being reported. When replacing multiple PDFs, assuming you are replacing a PDF that has been placed multiple times and choosing the "parent" PDF to replace, all copies are being replaced for me on Mac and Windows. Can you provide a video demonstrating the issue

Thanks, as mentioned in the PM, that file is actually crashing on open for me on Mac and Windows and does so in 2.1, which I've logged. If you can open it and save the resultant file I can look into the hang on autoflow issue.

Hi @PaoloT, I'm not sure which e-mail address you sent it to, but if you can PM me the IDML file it will be confidential and I'll look into this for you.

Hey Mike, I moved this to beta since it was reproduced in the beta and has a crash report, even we are unsure if it's a regression or not. I'm struggling to reproduce from the initial recipe, but the crash report from the other bug you reported and the crash report you provided are crashing in the same area so it's likely it's the same cause, which is logged. If you want to provide a file that crashes when Fix is pressed I can double check. From when I looked into your other report it wasn't related to having multiple table of contents, it was simply having a table of contents with headings that used levels (your initial report is easily reproduced by inserting a new ToC using the default Heading 1 and Heading 2 that's applied to some text and unchecking include as PDF Bookmarks)

So despite being unable to reproduce this, based on another report and the crash dumps you provided, we have logged and subject to testing have a potential fix. Keep an eye on this thread for a bump saying the issue is fixed and let us know if you experience the same crash after that

Are you able to consistently reproduce this or does it seem fine now? I'm curious if you still currently see it if renaming %userprofile%\.affinity\Photo\2.0 (Beta) to 2.0 (Beta) Backup helps with the crashes. If it does, can you send me the backed up folder?

Can you navigate to %userprofile%\.affinity\Photo\2.0 (Beta)\CrashReports\reports and upload any crash reports in this folder (ideally just the ones where the date modified matches the time you experienced the crash)

Thanks for the report @Seneca. I've logged this, as I can't see any obvious reason why it's not pulling in some of the headings

Yup, we've confirmed it's still an issue in Designer/Photo but not Publisher, and will update the issue. Thanks

We think this could be reproducible on M1 and not reproducible on Intel based Macs, as a few of us in QA can reproduce this aswell now. Curious what any other beta testers may find when trying to reproduce this Thanks for the report

This seems to be working fine for me on macOS on 2.2.0.1971, does resetting the app help at all?

The fix for this intentionally ended up allowing users to create fields with the same names as built in fields, but should be preventing duplicate custom field names from being created. I'll log an improvement in regards to no error/toast being shown when it fails to create a duplicate field

Thanks for the report, this is now logged with us

Thanks for the report, this is logged with us

On top of what Mike has asked, if you'd like to provide us with the chapters you are adding we can have a go at reproducing this. You can use this link to keep it private, the file will only be used for testing