App Store Connect, TestFlight, and Xcode Cloud Are Currently Down [Resolved]

[MacRumors]

Apple has updated its Developer System Status page to indicate multiple outages, reflecting developers' struggle to upload new versions of their apps.

Developers have contacted MacRumors to report frustration as their binaries are currently failing to upload with no informative error codes.

Apple's System Status page shows issues with Xcode Cloud, TestFlight and App Store Connect, with the latter experiencing problems with app processing and app upload.

It's not clear what the source of the problem is, but Apple is clearly aware of the situation and will already be working on a fix. We'll update this article when the issues are resolved.

Update: Apple's Developer System Status page says the issues with App Store Connect, TestFlight, and Xcode Cloud have been resolved.

(Thanks, Aniol!)

Article Link: App Store Connect, TestFlight, and Xcode Cloud Are Currently Down [Resolved]

 

[stevet]

“Developers have contacted MacRumors to report frustration as their binaries are currently failing to upload with no informative error codes.”

As a developer, some of my cohorts seem pretentious and very needy.

 

[slashlos]

I'll bite; what is the URL for the tabular display shown, much easier to grasp; maybe there's a pie chart too ?

 

[bsbeamer]

Several issues with iCloud as well, but they seem to be resolving fairly quickly.

 

[gank41]

I'll bite; what is the URL for the tabular display shown, much easier to grasp; maybe there's a pie chart too ?

Dev Status is here:

System Status - Apple Developer

developer.apple.com

Regular Status is here:

Apple - Support - System Status

Status for all planned and unplanned events for Apple Services.

www.apple.com

 

[t0rqx]

What bothers me with these status pages. They only show something is wrong, when the whole world already knows before the system does.

 

[ct2k7]

“Developers have contacted MacRumors to report frustration as their binaries are currently failing to upload with no informative error codes.”

As a developer, some of my cohorts seem pretentious and very needy.

As a consumer of services.. (or even producer), providing information to remedy the situation is good...

Unless you're a developer that is happy with no content if something goes wrong.

 

[Kaze9]

AAAAAAAhhhhhhh. This makes sense now. I was trying to upload a new build via Transporter last night and was getting a weird error. It was about this time too. Very confusing for a new dev like me to not know what was going on.

 

[slicktromboner]

Square was down at the exact same time. Tried to buy a burger and fries and they couldn’t take a payment.

From all indications, Square uses Google for their cloud provider, so I guess Apple does too for iCloud, lol.

 

[stevet]

As a consumer of services.. (or even producer), providing information to remedy the situation is good...

Unless you're a developer that is happy with no content if something goes wrong.

As a developer who uses the internet all day I know things go down from time to time. Expecting 100% uptime is ridiculous. Let Apple know and give them some time to fix it and stop complaining like a spoiled child online.

 

[ct2k7]

As a developer who uses the internet all day I know things go down from time to time. Expecting 100% uptime is ridiculous. Let Apple know and give them some time to fix it and stop complaining like a spoiled child online.

Seems like you aren’t a good developer to be honest, developers tend to expect services respond with meaningful data, which in this case, it did not.

I’m shifting the conversation to availability rather than “uptime”, as the latter is meaningless to engineers and developers working on highly available systems (which your comment shows that you likely not have).

No one is being spoiled or petulant. Think different.

 

[stevet]

Seems like you aren’t a good developer to be honest, developers tend to expect services respond with meaningful data, which in this case, it did not.

I’m shifting the conversation to availability rather than “uptime”, as the latter is meaningless to engineers and developers working on highly available systems (which your comment shows that you likely not have).

No one is being spoiled or petulant. Think different.

Seems like I’m not a good developer because I expect things won’t work 100% of the time? Laughable. Let me guess you’re one of the developers that runs to the internet to complain instead of sending in a bug report, right?

 

[ct2k7]

Seems like I’m not a good developer because I expect things won’t work 100% of the time? Laughable. Let me guess you’re one of the developers that runs to the internet to complain instead of sending in a bug report, right?

I’m a developer that sends useful data to clients. If that means telling users that a service I own is in a degraded state and not meeting SLOs, so be it.

But yes, I’ve worked on large systems in both the financial and non financial services sector. I’ve built APIs we’ve varying requirements for developers. One universal requirement is simple that a service returns errors with useful metadata when such a condition occurs.

Not sure why you think that’s unacceptable and that developers should just accept a service failing with no details.

Either way, it’s clear that in your career, you haven’t had much exposure to designing and managing systems in production.

 

[stevet]

<clipped self inflating info>


Either way, it’s clear that in your career, you haven’t had much exposure to designing and managing systems in production.

Haha, so that means apple hasn’t either based on your assessment and comments. Hilarious.

 

[ct2k7]

Haha, so that means apple hasn’t either based on your assessment and comments. Hilarious.

Having worked with and for Apple in the past, their services organisations leaves a lot to be desired. So yes, that is my assessment.

If you are providing a service, and you can’t tell your customers why you can’t provide the service, prepare to lose those customers.

 

[stevet]

Having worked with and for Apple in the past, their services organisations leaves a lot to be desired. So yes, that is my assessment.

If you are providing a service, and you can’t tell your customers why you can’t provide the service, prepare to lose those customers.

And yet you’re still a customer along with 816M other people. Practice what you preach and quit all their services and join some other companies who tells you exactly why they have outages. You’ll be looking for that company for a long time.

 

[ct2k7]

And yet you’re still a customer along with 816M other people. Practice what you preach and quit all their services and join some other companies who tells you exactly why they have outages. You’ll be looking for that company for a long time.

I don’t use Apple Developer Services anymore.

Ever checked GCP or AWS status pages? They tend to give more details than Apple’s.