Default widget extension not configurable on Mac

I've created a basic Multiplatform Project in Xcode, by going to File > New > Project. I've also included the default widget extension target.

When I run the widget on Mac, and I control-click and choose "Edit Widget" the widget just kinda turns gray and floats over other windows, but does not let me configure anything. We leave the option to use configure with app intents turned on when adding the widget extension target.

When I run the same project on an iPhone simulator, I can configure the widget without any issue.

If someone else has a few minutes, can they see if this repeats for them?

We are running this test because we are seeing the same experience in a real widget we are trying to develop but we can't get it to go into configuration mode on Mac.

Hi Ian,

Have you found any workaround or fix for this issue?

We are seeing essentially the same behavior in a Universal app with shared iOS/macOS WidgetKit code:

  • The widget is fully configurable on iOS.
  • It works correctly on macOS 15.
  • It also worked on macOS 26 a few months ago.
  • On macOS 26.5.2, choosing “Edit Widget” makes the widget turn gray and float above other windows, but the configuration UI never appears.
  • The same widget configures correctly in WidgetKit Simulator.
  • The widget’s URL action still routes correctly to the native Mac app.

We have tested many possible causes, including changing the macOS-only bundle identifier, widget kind, App Intent type/class name, cleaning build data, removing older app copies, reinstalling the TestFlight build, and restarting the Mac. None of these changed the behavior. Disabling or enabling iPhone Widget Mirroring also made no difference.

Our current suspicion is a macOS 26 system-level regression in the WidgetKit/App Intents configuration path, possibly related to the deeper integration of iPhone Widgets and iPhone Mirroring. The fact that the same code works on iOS, macOS 15, and in the Simulator makes an app-logic or packaging problem seem unlikely.

Have you been able to reproduce this on a newer macOS build, or find any workaround?

A Universal app that supports widgets is a very common scenario, so I’m surprised there is so little discussion or documentation about this issue.

I’ve tried every workaround I could think of, but nothing has helped. I was hoping to compare notes with other developers, but you are the only person I’ve found reporting the same problem.

Has anyone tried to see if it works on macOS 27 beta?

Same problem on macOS 27 beta

Default widget extension not configurable on Mac
 
 
Q