Jon P

Thanks for the report, this is already logged with us

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

Hi @dcarvalho84, I'm struggling to reproduce this following your steps. Are you able to attach the file you are printing (to pdf) and some screenshots of the exact print settings you are using to see if that helps?

Hi @Jiri Cvrk, welcome to the beta. This forum is for reporting issues that do affect the beta, but that don't affect 2.0.4. Looking into your history I see this is related to a report about a bug in 2.0.4. I'll lock this thread Thanks

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

This is already logged with us, thanks for the report.

I've logged the fact this hangs, Hangmans workaround is correct and working for me Thanks for the report

This is already logged with us, thanks for the report

Hi @MikeTO, Do you find you still get the warning after re-saving the recovered file? I recovered it in the same way you did and still got the warning, but once I alter the file and re-save it, it seems fine on subsequent loads

@Mr. Doodlezz Unfortunately, we don't know what caused the problem as such, if we did we would be wanting to fix the cause, not just repair the issue on file load. I've just double checked though, and you shouldn't ever be losing any visible objects in your documents, it's mostly an internal thing. Basically we are removing a link to an object that no longer seems to exist. Either we clean it up when we load the document or it would cause a crash which is what was previously being reported. Again, if you or anyone else find they are seeing this message appear consistently let us know, as if we can understand what causes it to break in the first place we can fix the cause. It's still something we are investigating.

If, after opening the file and the message appearing, saving and re opening the causes the message to re appear, can you please provide the file here for us to investigate

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

@alhagrafisk The crash report and file seem to be the same as the above issue, so should be covered by any potential fix. This sounds like a different issue however, do you have a crash report from this recipe? Is the new document blank that you create? Can you confirm what OS you are doing this on? This isn't really my area unfortunately, I would suggest creating a new post in the customer service forum, or e-mailing affinity@serif.com

@alhagrafisk Are you able to upload your file to the dropbox link in my original reply, I'll double check it looks like the same crash and get the file added to the report if so

@RevenantI split your comment into a new thread. If you can upload the file that's crashing I can see if it crashes on my end and is the same as the issue you originally posted in. If you "Saved As" the original should still exist and hopefully open for you, if not I would maybe attempt renaming any folders/linked resources that are in the file to break the links and see if that helps the file open

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

I've responded in your other thread

That was what I meant yes, it seems similar to the report (and the crash report seems the same). If it's possible for you to also upload the file to that dropbox link I can get it added to the report

We have an issue logged similar to this, but are you able to upload your file here so I check if it's the same as what we have logged? Do you have linked remote resources from iCloud?

This should be fixed in the 2.0.3 build

Thanks, I thought I was going to need to ask for the linked files to also be sent but even without them this is crashing when opening on iPad. I'm also finding that opening resource manager when opening this on Mac is triggering a crash. I've logged this, thanks for the report If you link your files locally, or embed them (when you've opened it without a crash) is that preventing a crash when opening it back on the iPad?

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

Hi @poleeto, I've responded to your other thread, if you can provide us the file I can look into it