Here's a fun widget dilemma…

Setting iOS 18's .widgetAccentedRenderingMode(.desaturated) on an Image that is the content of a Button with an interactive intent breaks its clickability? 👀

Just me, or am I doing something wrong?

@_Davidsmith?

Switching widgetAccentedRenderingMode to .fullColor resolves the user interaction problem, which is frustrating. It feels like the API is accidentally returning a transformed image view with userInteractionDisabled even when it is not originally set 🫤
I have a sample project and a trivial reproduction case, so I guess I should file it?

FB15124298 on WidgetKit
“Image .widgetAccentedRenderingMode(.accentedDesaturated) prevents user interaction in widget when content of a Button(intent:)”

#radars

@stroughtonsmith Just ran into this (even in iOS 26) and duped! FB19244485
@teaseaque ha. I re-upped mine only yesterday as it wasn't fixed in iOS 26

@stroughtonsmith @teaseaque I found a workaround for now - use `Color.clear` for the Button label and put the accented image as a `.background {}`.

I'm running into other issues though, mainly that `.desaturated` breaks position animations (forcing a cross-fade instead of a slide) and `.accentedDesaturated` causes the images to flash to white during an update

@jayrhynas @stroughtonsmith @teaseaque I found this thread on developer forums with some suggested workarounds ... which don't work anymore on iOS 26 🙈 https://developer.apple.com/forums/thread/763804
Widget link broken by `.desatu… | Apple Developer Forums

@stroughtonsmith How is this still not fixed??? 😵‍💫

@stroughtonsmith perhaps also good candidate for TSI? Since they now require Xcode project to submit anything.

I think the response is much more likely compared to a feedback.

@nemecek_f @stroughtonsmith Is this now the best way to go with these things - even when you're reporting something like this where it is 100% a system bug, and not something they can help you fix directly?
@stroughtonsmith 😔 I've seen exactly the same behavior, I never worked out if there was a workaround. Just changed my design and moved on.
@_Davidsmith I expect you might be able to zstack another view on top of the Image() with a 0.1 opacity? I'll test it out
@stroughtonsmith @_Davidsmith overall I’m a huge fan of SwiftUI and prefer it, but it’s stuff like this that really grinds my gears and has me itching to go play around with UIKit for a little.

@_Davidsmith @stroughtonsmith To be honest that's often how I proceed with SwiftUI weirdness and bugs 😅

Not great vibes from the framework! 😕

@stroughtonsmith @_Davidsmith my favorite thing is that this is still broken in iOS 26 out of beta. There's Feedbacks people have opened on this since before September 24 and it's still happening. In true Apple fashion, I am not expecting them to ever care about this and the workarounds that worked in 18 no longer appear to work in 26.
@stroughtonsmith @_Davidsmith Also reproduced and filed as FB20759311.