this is a great observation, i was also wondering why everyone said to override buildMenuWithBuilder: in app delegate, when the app delegate documentation shows no such function to override. buildMenuWithBuilder: was never called for me either.you found the answer: very old iOS apps built from old Xcode starter templates have app delegate subclassed from NSObject, but that should be changed to subclass the app delegate from UIResponder now for Mac Catalyst menu operations: old code commented out:@interface appDelegate : /*NSObject*/UIResponder <UIApplicationDelegate, UITabBarControllerDelegate> {tab bar controller stuff is optional of course depending on your app

same problem here. did you make any progress on this? the catalyst conversion of the code to run on mac seemed to go really well, butcode signing / uploading = confusing as usual when they change things.

same issue here: cannot create new macOS app in app store connect

interesting, i was able to find a way to get past that particular error after a lot of trial and error.when i have time to trace what i did, i will post it. but maybe i wont until i can get the app fully uploaded to avoid misleading people. hints seem to involve using Apple Distribution certificate (not MacOS distrib cert) for both the macOS provisiong profile and also the iOS provisioning profile (the same certificate), and, creating a "mac installer certificate" and downloading it to my mac and using that in the archive upload process. i didnt know about the mac installer cert requirement, that seems new. now... i cannot create a new mac app store entry, so not out of the woods yet. others are having this problem:https://forums.developer.apple.com/thread/127608update: creating a mac app store entry has been fixed earlier in the week (problem on apple side)

apparently you also need a mac bundler certificate created and downloaded to your system and selected in the uploader panel during the upload process? (e.g. when the uploader re-signs you app).

update Jan 6 3:30pm EST: now I am able to create a macOS app in the app connect system, but only for a catalyst.com.etc mac name (e.g. for mac catalyst, the porting iPad app to MacOS system). it doesnt seem to recognize my regular mac app IDs I created.

same problem here, xcode11.3 seems to be missing ios13.3 device support fileswe tried the trick of copying 13.2 support folder and renaming it to13.3, but it didnt work this timeactually it did work when i tried it on a different machine, what i did was make a symbolic link from 13.2 (actual folder) to 13.3cd /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupportln -s 13.2 13.3check it:ls -l 13.3lrwxr-xr-x 1 user staff 4 Jan 11 13:13 13.3 -> 13.2restart xcode and retry run on device

even though this is an old post, i ran into the same issue, and this and other posts have helped: you have to make sure you select the iPad app id and then the Mac checkbox will show up as options. checking this checkbox on the iPad app id will make the "maccatalyst." prefixed app id be available when creating provisioning profiles. if you select a Mac app id, the checkbox doesnt show. also after checking this box, you then have to re-generate your provisioning profiles (as you do every time an app id internal settings are changed). any old profiles w/ this id will be marked as invalid or something similar.note also when creating the profile for the mac catalyst app for distribution to the mac app store, you have to use an Apple Distribution certificate, not a Mac Distribution certificate to generate the mac distribution provisioning profile (e.g. Not like old mac app signing for the mac app store). you may be able to sign the app w/ the mac cert + distrib profile on your local machine, but just try to upload it...that won't work. that was confusing.

well finally started working the other day, now the issue again: builds go up, but don't even show up in Processing (they just disappear)

same here, builds upload but never even show up in "Processing" mode in itunes connect

one thing i noticed, i had some old UIWebView references in some libraries. those seem to now go beyond causing warnings of being obsolete and are now Errors of being obsolete. once i removed the UIWebView references (which i was not using anyway), the build went thru.

same here. i only want to allow iMessage. did you find any resolution?

if anybody from Apple is listening, the same issue is happening again. builds go up then disappear. not showing as Processing or in Activity list.

found the problem: if you have a UIWebView referenced in a cocoapods module, even if you are not displaying any UIWebViews, the build goes up but you get an email saying it is bad and it doesnt show up in Activity at all.

I found that I had a reference to UIWebView in a cocoapods module. You may have UIWebView in a package.json module (npm or yarn module?) Even though I didnt use UIWebView or anything calling it, Apple has a problem with it. The app makes it up during upload, but then you get an email saying that the upload failed, and it never goes into processing mode on itunes connect / app store connect. When I remove the .m files that have the UIWebView from the build (e.g. remove from build target), it worked. However, that was a lucky fix. In some cases if you remove .m files from target, the app might not build, and you have to do more to remove the referencers of UIWebView.