Claude31 thanks for the reply. You are correct. This is what I did. However I have some logic in the button's IBAction which then requires me to use performSegueWithIdentifier. This code snippet may clarify why... - (IBAction)cancelButtonPressed:(id)sender { if (self.objectId != nil) { [self performSegueWithIdentifier:@"cancelSaveExisting" sender:nil]; } else { [self performSegueWithIdentifier:@"cancelCreate" sender:nil]; } } I use the same viewcontroller for creating an object based on user input as well as when they want to edit that data. Either than that, everything you mentioned is the same.

Turns out I had the unwind segue in the wrong class. My bad. I just needed to step away for awhile and come at it with fresh eyes.

It appears that App Store Connect - App Processing is having issues again. The System status page says -1 performance. What I would like to know is if this is the cause of my issue or is there something new that was introduced that I need to address that occurred in the past day? An update to how App Store Connect Distribution works???

So I've confirmed I'm signed into the correct Apple ID. I actually have four developer accounts but they are all showing as signed in, in Xcode. In the Signing & Capabilities page in my project I have it set to the correct Team (which is an organization team of which my account is the admin holder of). Again, nothing here has changed since 2 days ago. Just all of a sudden it's having issues today. I tried going to your link for "Contact Us!". I had someone call me but unfortunately the agent had not encountered this error before. Therefore this may need to be escalated to another team. But, she said she would send me an email to provide more details on everything that I'm seeing and evaluate from there. On a side note, I was able to upload my app using "Transporter" as I discovered thats a new app. But it is still giving me the same error on xCode. So while I believe your initial thoughts are correct that this may be an apple ID issue but I am unable to trace down the issue as everything appears to be setup correctly. There's also no way to "Sign out and and Sign back in" option to see if that would clear it up.

I just ran into this as well. It's a key design we have in our app currently so this has halted our development. Is there a fix in 15.2 planned?