Jon P

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 @Hangman that's been logged with us through that thread.
I've logged an improvement about also adding it to the Layers dropdown, which would allow it to be assigned a shortcut

My bad, for some reason show toolbar was disabled after updating to the the new beta!! 🤣

Ok next time this happen I'll check the console

I'm going to have to do some work to reduce the file size. I haven't optimized my images for print yet and my resources are 13GB in total. So it may take me a while to create a package I can get to you.

Thanks, I've reproduced that and logged it

I've noticed this before @walt.farrell.
I've not been able to suss out what causes it, besides a bit of guesswork that some times we crash and it's not caught by the handler, and the crashpad handler process ends up not closing, and a new one is created on next run up.

Hi @Pasquien,
This is unfortunately a known bug in v2.0.4 and is caused by linked files returning a 0 px x 0 px Original size and subsequently a 0 px x 0 px Placed size in the document as seen here on the Frontpage Master of your file with the Linked Affinity Designer file toebakstapper.afdesign...

If you haven't already downloaded the v2.1 Beta then I've rebuilt your file for you (attached below) which you should be able to open again in v2.0.4. You will need to relink your graphics and place the Affinity Designer file again on the Frontpage Master checking that it's Original and Placed sizes are correctly reflected in Resource Manager.
Please give the rebuilt file a thorough onceover to make sure everything is correctly rebuilt as this is a manual process...
I hope that helps...
toebakstapper (rebuilt).afpub

Thanks for the update, had a chat with Matt about it yesterday and he advised he was helping you troubleshoot it, so glad you got to the bottom of it.
I'll see if I can reproduce the issue and then we can hopefully log/fix it to prevent it happening again.

Thanks for the update, had a chat with Matt about it yesterday and he advised he was helping you troubleshoot it, so glad you got to the bottom of it.
I'll see if I can reproduce the issue and then we can hopefully log/fix it to prevent it happening again.

Thanks for the post, this is something we are aware of and it's already fixed internally.

Thanks for the report.
I've logged this, but in the future if an issue affects retail please post it in the Bugs forum, this forum is for issues that are specific to the Beta.

Apologies this got missed, we've got an improvement logged to simulate overprint in the app

Good spot, I've reproduced and logged this

Thanks @walt.farrell,
Turns out this should be fixed in the latest beta, so if OP is still getting this in 2.1.0.1736 let me know

Thanks for the file and video @siapec. It's simply deselecting the text that's triggering it.
We've reproduced and logged it

Hi folks,
I thought I'd give you a quick progress update and let you see some of things we've been working on at Serif Labs.  We now have a scripting core that we're reasonably happy with and have put together a little test area where we can run Javascript code, so I thought I'd show you some of that. Things to note:
This is all VERY early, like pre-pre-pre-alpha. The JS API is extremely fluid and is constantly changing. This is not how the Affinity suite will run scripts and plugins; it is just a sandbox window for internal testing. There is still a huge amount of work to be done. I can't provide any timescales for when scripting will be publicly released, for Beta or Retail. Constructive feedback is welcomed, but I won't be able to answer all questions - see previous points. I'm not claiming any of these examples are particularly useful on their own; they're just to demonstrate some basic scripting functionality. Re Javascript async - yes, we support it, I've just not recorded anything yet. The sleep calls are there for screen-recording purposes only. Here are some demos as low-res gifs. If you want to take a closer look, movs are attached.
Create a Mandelbrot image

Some dodgy physics

Insert a dragon curve

"Emojification" (translation?) of text

Create a grid of colours
 
Select and hide based on hue

Replay a document's edit history

mandelbrot.mov
balls.mov
dragon.mov
grid.mov
hue.mov
replay.mov
emoji.mov

Hi @Dennison,
Thanks a lot for the new crash report, it was very helpful.
We've looked into this and we think we know what the issue is, and hopefully will have a fix for this in the next beta.
However I think you can fix this now on your end. If you navigate to the Appearance Panel (the one that Paul asked for a screenshot of in the first page of this thread) and change the Apple Highlight Colour to something other than Red, and then back to Red, this should hopefully get the beta running for you.
Let me know if that's not the case, either way the next beta should hopefully not crash on run up even without doing the above

Hi Jon.  Thank you for this - yes the Beta now opens on my device.  Thank you for your work on this - I really appreciate the work everyone is doing to make this app the BEST.  As you can tell from the size of the files, this app is my workhorse.

I've deleted - downloaded and reinstalled the "latest" Beta from the website. Still crashes as it opens.  Here is the Crash Report - this one clearly says 2.1.0.1732.  Maybe this morning I downloaded before 1732 was available.
Beta 1732 Crash report March22.docx

Hi @dcarvalho84,
This is something we are aware of, we hopefully should have some tweaks in this area in the next beta build that is made available.
Thanks for the report

Sorry, Been busy for a while. I tried to crash it again, but it appears the latest update has fixed the problem.

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

Hi @AcreativeMotif,
Welcome to the forums.
This file is opening fine for me, which suggests it's one of the links to your files that's causing the crash on your end.
There was a file which had a link to the root of dropbox which I've removed (this was your front cover).
If this still crashes on open for you, I would advise to rename the CARTERDEVGROUP folder in your dropbox. This will "break" all the links so they load as missing (so it's in a similar state to my machine which is opening the file). If you then re-link all the files to the renamed folder your document should look the same as before and hopefully be fixed
Built Environment DEI Analysis University of Washington HFS-rs.afpub

You might try loading it again, but first rename the folder containing your Linked resources, so they are missing. If that works, it helps us figure out the issue, and also gives you a start on a workaround if it happens again.