I also think this is an amazing update. So many good things, and so much attention to details!
I will test a bit more but for now I can also add that in general using colors is a bit confusing at the moment. I wouldn’t be able to explain at the moment what are different color popovers for. So I agree with @Ash to maybe add some button to the color popover and some other affordance to color section in Inspector for a better experience.
I think I’ve found a bug/inconsistency.
If I create an artboard, add a fill colour, convert it to a symbol and set “include fills as content”. The fill colour does not appear in the overrides. Look at the following use case, I have two shades of blue here and a border on the artboard:
So in a case like this, I don’t have full control over my symbol if I don’t use a shape as a background, which is the use case the new artboard styles are supposed to address right now?
Hey all, glad to hear you like the new update so far! Thanks for taking the time to comment.
@samvermette There’s not an exact date yet, but we’re happy with the progress we’re making. Once we know more, we’ll let the community know.
@Ash Regarding A: That’s a good point; I’ll see what we can do. Regarding B: It would be nice to have, but it’s probably not within our scope for now, unfortunately.
@wwwedran Looking forward to reading your thoughts later!
Good catch! It’s definitely something we’re planning to implement, but we haven’t gotten around to it yet.
Makes sense, it isn’t a huge deal, just a nice to have 
Are there plans to extend the recent styling improvements for artboards to groups, or to introduce support for nested artboards? One challenge I encounter in Sketch compared to Figma is the sheer number of layers, partly because background layers are required. This also adds complexity to managing smart layouts. If background properties could be set on the container, it would not only reduce the number of layers but also make layouts more intuitive to work with.
In short: yes! What you’re describing will ship in this release alongside Stacks (neither are in the beta yet, but hopefully will be soon). Feels very necessary to do this if we’re doing Stacks, and that’s the reason it’s taking a bit longer to get this over the line than we’d originally planned.
Hey folks, quick note that the latest beta update drops support for macOS 13 Ventura. We need to drop OS support periodically to allow us to adopt new frameworks and technologies. We’ll always aim to cover the latest version of macOS and the previous version.
A post was split to a new topic: Blur applied to smart animate prototype transitions crashes Sketch
I took the liberty to split the last post from Vedran into a new one, in the Share an issue category. See you there!
A couple of inconsistencies with 102 I thought I’d bring up.
The inline symbol/group symbol “send to symbol page” inconsistency is more pronounced now that it’s more conducive to skip background shapes when creating symbols - if you create a symbol, the options presented to you should be consistent whether it’s a group or an artboard. I’ve gone on about this before at length here "Send symbol to symbols page" inconsistency
Also if I add a layer style to an artboard that is later used as a symbol, it feels like the layer style should be available as an override.
Once the 102 release version is out, will I be able to open documents that I created in the 102 beta app? Right now I get an error message upon trying to open 102 beta documents with the 101.8 release version of Sketch.
Documents you create and open with this version of Sketch may not be compatible with older versions of Sketch. For real-time collaboration, everyone should use the same version of Sketch.
Source
Yes.
Yes I’m aware of that, but it’s not what I asked. The upcoming release version of 102 would be newer than the current 102 beta, not older. I also don’t need real-time collaboration with certain files created with 102 beta.
I answered your question. I just provided the link and quote for context, since v102 incorporates breaking changes to the .sketch file format. The real-time part of the quote was just part of the banner notice from the link, so I included it.
I guess I should note that beta software is unfinished, and by virtue of that fact compatibility with future versions of that software cannot be assured, even by the developers. That said, it’s standard practice to attempt to ensure compatibility between files of a beta and production version of a software, unless explicitly stated otherwise.
Ok, thanks!
Hey @JuurGroove, what @Phy mentions here is correct. Our aim is that documents in the 102 beta open and work smoothly with final release. There are lot of moving parts, though, including features we’re yet to add to the beta. So, there’s no 100% guarantee. What I can say is that we’re also affected by migrations from one version to another internally, so it’s in our interests to make this painless as well!
Are you saying you’re still going to add even more new features to the current 102 beta before its official release? It’s been almost 5 months since the last whole number release of Sketch…
That’s the plan right now, yes. It will make more sense why we’re bundling together what we’re bundling together when the time comes (and it’s really not far away now). One of the reasons is to avoid more version-version incompatibility, like we’ve just been discussing.
And believe me, no-one is more aware of the timeline than the marketing team that likes talking about new things. 
It’s a longer timeline than we would have liked, but we think it’s worth the wait and we hope everyone else will feel the same!
Very excited for some of the things I presume will be hitting beta soon. I think 102 will eclipse 100 and 101 in terms of features, improvements and a show of intent. It’s going to be awesome. If stacks end up in 102, you should put a good chunk of marketing spend against it 
