Provisioning profile failed qualification. Profile doesn't support App Groups.

even with the already uploaded binary, cannot get it to be reviewed...

The status of your app has changed to Invalid Binary.

Please correct the following issues and upload a new binary to App Store Connect.

ITMS-90286: Invalid code signing entitlements - Your application bundle’s signature contains code signing entitlements that aren’t supported on macOS. Specifically, the “[group.com.

I just tried uploading my app from Xcode 16 and it worked.

But I still need to be able to upload my apps to App Store Connect from macOS Ventura and Xcode 16...

It must be some bug on Apple side...

App groups are more complicated than you might think. I have a bunch of backstory to this in App Groups: macOS vs iOS: Fight!.

Note that the story has changed in the last few days, and I’m not sure which side of that cutoff you were on. If you continue to have problems, please post the details here and I can take a look.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

as of now, you have to disable the automatic sign management, and create a separate provisioning profile for your mac app and import it onto xcode.

this way, I temporarily resolved the issue.

It’s better to reply as a reply, rather than in the comments; see Quinn’s Top Ten DevForums Tips for this and other titbits.

It's not clear what has changed

At the top of App Groups: macOS vs iOS: Fight! there’s an IMPORTANT callout that talks about the recent change.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

..

Thanks @eskimo @DTS Engineer, really appreciate all the work you do here, it shouldn't be up to just you to handle so much dev interaction!

So, on the IMPORTANT callout (might be nice to stick on date on that btw rather than at the bottom in revision history where it's not clear what has changed), it just says that it's now possible to do something with XCode or manually, but it doesn't say anything about breaking existing provisioning profiles which seems to have occurred.

Is that a bug or did I miss some notice about this?

PS. Would be great to learn about what's changing behind the scenes with this from a technical point of view, its motivation and what your plans are on this going forward.

You have to read between the lines of App Groups: macOS vs iOS: Fight!. It describes a whole bunch of problems caused by the fact that macOS-style app group IDs are not authorised by a provisioning profile. These include build problems but also runtime problems. At the time I wrote that I couldn’t come out and say that we’re planning to fix this by converging on iOS-style app group IDs, because I’m not allowed to talk about The Future™. However, with Xcode 16.3 beta, the future is now (-:

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"