Workaround a crash in macOS tahoe 26 / xcode 16.4+

[ArthurBrussee]

Objective

Workaround a crash in macOS tahoe 26, and newer xcode versions.

Fixes #19625, and see #19567

Solution

Disable debug assertions in objc2 untl winit has a new release enabling a more precise workaround.

Testing

cargo run --example breakout goes from crashing to working fine on the macOS tahoe beta.

Alternative

A beta is a beta so maybe it's just not supported and we should just wait for the winit update. madsmtm/objc2#765 (comment) implies that an incoming xcode update has the same issue however so it might be more urgent.

[BD103]

As a small note: the advisories CI failure is unrelated to this PR, so it can be ignored.

[BD103]

I think this should be included in 0.17. It's a small change, and we don't want to crash on platforms we will need to support in the future

[ArthurBrussee]

CI is clean now after the minimp3 removal :)

[BD103]

I'm not able to test it locally, but the change and comments look good. Note that this is something all projects that depend on Bevy will need to do in order to avoid crashing.

We should probably open up a follow-up issue for this that is blocked on Winit's next release, but beyond that it looks good!

[alice-i-cecile]

Hey @mockersf how much do you hate this?

[mockersf]

A lot. This doesn't fix anything because profiles are not used from libraries

https://doc.rust-lang.org/cargo/reference/profiles.html#profiles

Cargo only looks at the profile settings in the Cargo.toml manifest at the root of the workspace. Profile settings defined in dependencies will be ignored.

[mockersf]

@madsmtm do you know if a winit 0.30.12 patch with rust-windowing/winit#4302 is planned?

[robert-wallis]

I made a PR to add this to winit v0.30.x rust-windowing/winit#4301 in winit. It's been merged to master rust-windowing/winit#4302, but my v0.30x PR was closed a few weeks ago because it needed to go to master first

[kchibisov]

I made a PR to add this to winit v0.30.x rust-windowing/winit#4301 in winit. It's been merged to master rust-windowing/winit#4302, but my v0.30x PR was closed a few weeks ago because it needed to go to master first

If you pull objc with the feature needed in the Cargo.toml in bevy you don't need anything from upstream. Like the bug is fixed by enabling feature on the crate, so you can do so in bevy without any need from a winit side. That's just how it always worked in rust with such things.

objc2 = { version = "0.5.2", features = ["relax-sign-encoding"] }

Just add this and (and also for 0.6 version I guess if it's in tree) for macOS in bevy where e.g. winit is pulled and you have it fixed.

[mockersf]

If you pull objc with the feature needed in the Cargo.toml in bevy you don't need anything from upstream.

I would prefer to not add a direct dependency on objc in Bevy. As it's something we depend through winit, it means keeping versions in sync, triggering unused dependency checks, ...

Also, having the update in a winit patch means it will work in previous versions of Bevy that depends on the 0.30, so Bevy 0.16, 0.15 and 0.14, without Bevy having to release patches for all those versions

[kchibisov]

If you can wait (until I have time to cut a release), then yes, that would be better, it just felt with that spam that urgent action is required, which I've provided.

[mockersf]

macOS 26 will release at the earliest in September, so not that urgent. The sooner the patch is the better, but no need to rush