I have same issue :(

Hello Quinn, Thank you for the suggestion. After unchecking the Mac Catalyst capability everything did come in place. Now we can create the correct provisioning profile. The strange thing is that we did not change this setting since our last successful submission to the App Store. Any way, thank you very much for helping to figure this out. Best regards, Sergey Nikitin

We are experiencing the same issue in another way. Our Catalyst app is distributed without the 'maccatalyst' prefix. Unfortunately, the previous provisioning profile that was working has expired. When generating the new one, the 'maccatalyst.' prefix is being added automatically. Is there any way to fix this?