Jon P

Thank you. The file opened. Thank you for removing the linked cover page. Life saver. 

This was actually already logged, I just missed it on the known issues. It actually does sort, but you need to refresh the table to see the sort (which can be done by changing the target type between anchors/paragraph). Should hopefully be fixed in the next beta
I'll look at getting this added as an improvement

This is indeed a Mac only issue, I've reproduced and logged it
Thanks for the report

Correct. A second attempt always seems to work, whenever I've had the problem.
File is uploading, but will take awhile. I'll let you know when it's complete.

Hey walt,
If you want to upload the .dmp here I can have a look.
I assume you can't reproduce it and it ran up the second time without issue?

Thanks for the report, I've reproduced this and logged it

Thanks for the report, I've reproduced this and logged it

Hi @dcarvalho84,
Indeed, nothing was logged so there hasn't been a fix. I have however just reproduced it thanks to the video you provided, so it's now logged with us and should hopefully be addressed in a future beta.
Thanks for the video!

Is that maybe related to the AFB-7315 bug on Macs?

Hi Mike,
I've logged the fact an e-mail with ?subject=test at the end isn't viewed as being valid, as that is indeed a regression
I'll see if we can validate as text is entered, as it's currently possible to get something "invalid" accepted if you update it and click "OK" before tab, so that seems like a bug to me
Edit: Worth noting, you can create a URL with mailto:test@email.com?subject=test as a way around the first issue
Thanks

On Windows, if you don't have a Layer selected, then F2 (for example) can be assigned to something else and it should work for whatever you assign it to, then go back to renaming a layer when a layer is selected.
On Mac this doesn't seem to be the case so I can get that logged

On Windows, if you don't have a Layer selected, then F2 (for example) can be assigned to something else and it should work for whatever you assign it to, then go back to renaming a layer when a layer is selected.
On Mac this doesn't seem to be the case so I can get that logged

A couple of comments:
It appears the agreement to send Analytics applies to the entire suite. So once you agree in one app you are not asked in the others. At this time, it appears that once you have agreed, you cannot opt-out. Is that a beta thing (as sending crash reports was in the old betas), or is opt-out coming later?
(Only tested this on iPad so far.)

While testing a different issue, I recreated the "links removed" warning and this document is so basic that it might be useful for figuring out when objects aren't being cleaned up.
The only objects I created in this document are pages and master-based text frames. I'm fairly certain I didn't delete any text frames from a page before saving but I did add, move, and delete single pages and two-page spreads.
master frames.afpub

@Entrepreneur, so basically the image of the van is corrupt and this is causing the Affinity Designer file to freeze when exporting to PDF. There are two instances of the van image in your file, so I've replaced both instances with an Affinity Photo file (both layers are now highlighted in green in the Layers Panel) which is Placed in your document so you can still edit it, if required, by selecting the Placed image layer and clicking Edit Document in the Context Toolbar.
See if the attached file now works for you when exporting to PDF...
ARVONTALAPPU.afdesignVan.afphoto

Ah, I didn't go that extra step. Yes, I'm seeing the same results as you.
Thanks

So we have a recipe and a potential fix for this already. As I understand the next major beta will resolve this issue. If you still encounter it in that beta please tag me and I'll get your files to investigate further.
Apologies for the inconvenience, it is a bit of a hard bug to workaround.

So we have a recipe and a potential fix for this already. As I understand the next major beta will resolve this issue. If you still encounter it in that beta please tag me and I'll get your files to investigate further.
Apologies for the inconvenience, it is a bit of a hard bug to workaround.

So this was added a short while ago (2.x), basically we sometimes get reports with files that crash on open. When we investigate them we find there's links to broken/corrupt objects (or objects that just don't exist), and that's the cause of the crash.
We are still trying to find recipes that can create these types of situations, but for now we identify these objects, and instead of crashing, clean them up when we load the document, and leave this message letting the user know that has happened.
Nothing should look different in the document, as the objects removed were broken anyway.
It's probably worth noting that links here doesn't as much refer to resource manager type links, it's more of an internal link
If you find during your work you are saving, re-opening and seeing this message a lot, then let us know and hopefully we can find the recipe that triggers the message the next time the document is loaded

So this was added a short while ago (2.x), basically we sometimes get reports with files that crash on open. When we investigate them we find there's links to broken/corrupt objects (or objects that just don't exist), and that's the cause of the crash.
We are still trying to find recipes that can create these types of situations, but for now we identify these objects, and instead of crashing, clean them up when we load the document, and leave this message letting the user know that has happened.
Nothing should look different in the document, as the objects removed were broken anyway.
It's probably worth noting that links here doesn't as much refer to resource manager type links, it's more of an internal link
If you find during your work you are saving, re-opening and seeing this message a lot, then let us know and hopefully we can find the recipe that triggers the message the next time the document is loaded

So this was added a short while ago (2.x), basically we sometimes get reports with files that crash on open. When we investigate them we find there's links to broken/corrupt objects (or objects that just don't exist), and that's the cause of the crash.
We are still trying to find recipes that can create these types of situations, but for now we identify these objects, and instead of crashing, clean them up when we load the document, and leave this message letting the user know that has happened.
Nothing should look different in the document, as the objects removed were broken anyway.
It's probably worth noting that links here doesn't as much refer to resource manager type links, it's more of an internal link
If you find during your work you are saving, re-opening and seeing this message a lot, then let us know and hopefully we can find the recipe that triggers the message the next time the document is loaded

I've responded in your other thread

Thanks Jon, I've uploaded the file to the Dropbox link, hopefully that is useful in diagnosis

Hi,
It's hard for me to tell if anything has been lost, but the attached file should hopefully open for you
1637313505__MG_0440PaintAF-r.afphoto

Thanks for the report, I've reproduced and logged this