Well, it got unfixed. Something is goofed up here.

I submitted this version of the app to the App Store. It passed. I also purchased my app so I could run the purchased app when the new version came out. It came out today and the app launched on my Mac. I still need this to be fixed as development is hindered.

I got an answer from Apple on this. I think I shouldn't have posted this to begin with.

You should call Apple about this. https://developer.apple.com/contact/#!/topic/select

Where can I find the definition of the error codes?

I generated a profile and used that instead of the automatic profile and it still doesn't launch under Destination Mac (Designed for iPad).

Apple's answer is below this line. Some screenshots are always required. Even though your app will not run on those devices, it will still be displayed and just say it is not downloadable on that device. Also, 5.5 screenshots are used for scaling up and down depending on the users device and what screenshots the developer has or has not provided. For a list of required screenshots, you can visit the link below: https://developer.apple.com/help/app-store-connect/reference/screenshot-specifications

And yes, I tried to change the bundle id and then back. The changed id worked, but the correct one doesn't.

My feedback number for this go around is FB13225056.

The issue has been fixed for me in Xcode 15.1 Beta.

I found the issue. For some reason, I had an App Group entitlement that was unnecessary. I removed it and it now launches.

Check out this link to manually generate a provisioning profile. https://developer.apple.com/help/account/manage-profiles/create-a-development-provisioning-profile/ However, many of us find it much easier to let Xcode automatically generate the provisioning profile. See the image below.

Just in case you didn't see my comment. That image is not of a website. That image is of Xcode. You should have Xcode.

I want the look of the app to be compatible with the Apple Vision Pro, so I have decided to create an Apple Vision destination with the visionOS SDK. It took some work for this to happen, but it looks nicer than the iPad app looks on the simulator.

@Bruckner I let Xcode generate the models from Core Data models. That is what resulted.