destinations.txt simctl_diagnose_log.txt ps.txt simulators.txt previews_diagnostics_summary.txt SerializationErrors.txt This is becoming a common thread with xCode lately. MessageSendFailure: Message send failure for relaunch ================================== | RemoteHumanReadableError |   | ProcessError: Failed to launch widget extension: The operation couldn’t be completed. (CHSErrorDomain error 1050.) The generated debug file is too large to attach.

This started last night, I submitted a new build and Apple reported at the time it was successfully uploaded. No emails back from apple but it never shows up in the appstore connect build section. Is something down at Apple?

Come on Apple, this crap is still down.

Come on Apple this is still down and not working. Your system status says it is, but everyone knows the system is hosed up. Typical these days with your maintenance, you break everything.

An error occurred preventing Xcode from downloading version information from App Store Connect for account "xxxxxxxx". An unexpected error occurred: [<__NSDictionaryM 0x600003ed4fe0> valueForUndefinedKey:]: this class is not key value coding-compliant for the <app name! 5.00.12 (iOS App). I have no idea what the hell is causing this. I have checked all of the links between screens and objects and none are missing. This is a live active version on the store.

I'm really sick of Apple and their BS kickbacks they get from github and the other source control outfits restricting what source control packages we can use inside of XCode. We have used Code Commit with AWS for YEARS! We are not switching but apple's Xcode will not allow us to add it as an account. We used to be able to use it, but Apple took away the GIT account setup so now you have to use one of their kickback outfits. This is complete BS Apple. Even AWS realized how important Code Commit is and made it available to everyone again and pledged full support going forward. How about you get off your collective sixes and do the same. I'd like an explanation on why you took away the one feature that allows us to use what works for us.