Its been months since iOS26 has been released and this bug is still present. Very disappointing.

Similar issue here. Hope it gets fixed with IOS 26.1.

It seems like this only works when the shape or image is close to the edge of the screen. for example this works: var body: some View { VStack{ Spacer() Color.yellow .padding() .background(Color.red, in: .rect(corners: .concentric)) .padding(20) .frame(height: 300) } .ignoresSafeArea() } but this does not: var body: some View { VStack{ Color.yellow .padding() .background(Color.red, in: .rect(corners: .concentric)) .padding(20) .frame(height: 300) } .ignoresSafeArea() } Is this the intended behavior or is this a bug?

This is happening to me too right now.

I started getting this error too even though nothing had changed for me either.

Thanks for replying. I built the app as a multiSystem app so the widgets should work on the MacOS without have to create a Mac specific extension. After some research I found that the problem isn't the exclusivity but there is a bug with widgets that use AppIntentConfiguration on macOS, which other people are having issues with as found here: https://developer.apple.com/forums/thread/765020?login=true&page=1#824567022

I'm still having the issue.

Thank you for your recommendation of reading about App Groups. I decided to try creating separate targets for IOS and MacOS with separate app groups for each platform. It seemed to work till I realized that widget extensions will be an issue. I can't use the same widget extension between both platforms because of the app group issue. And I can't create multiple widget extensions because it seems like there can be only one widget bundle. I'll have to look into the platform-specific .entitlements like you mentioned, but I fear that I will still run into the same widget extension problem mentioned above even with platform specific .entitlement files.