Just a normal Tuesday using the OS made by the same company that brought you the truly amazing technical wizardry behind Deep Fusion and AirPods Pro…

All of the issues below are from up-to-date systems running Catalina and iOS 13 that I discovered before 11am on a normal Tuesday morning.

First, the Mac App Store.

Remember. This is the storefront Apple expects developers to base our livelihoods on and hand over 30% to use.

Let’s check in on Photos.

“10,376 Photos, 942 Videos” vs “10,773 Photos, 1,135 Videos”. No idea which one is correct. Both devices have been powered on and online for days – including overnight.

Take a photo on iOS and watch it sync to other iOS devices near-instantly. Never appears on Catalina.

Now, Music.app.

Since upgrading to Catalina, I simply cannot sign in on this Mac. Restart the machine. Sign out / in of iCloud in System Preferences. Restart again. Repeat. Nothing. Just silent failures.

I know my password is correct because if I purposely enter I bad one I get this.

But exactly how fucked is Music.app overall you ask? It’s this fucked…

And also perpetually-spinning-progress-indicator fucked…

It’s also they-even-broke-the-sign-up-page fucked….

As well as can’t-display-the-price fucked…

Now, I know what you may be saying. Surely this is just the result of a bad HTTP request when Music.app fetched the template data, right? Sure. Probably. But it persists across reboots.

So, while Music.app is walking around with its pants down in this seemingly-permanent fucked state, is it displaying any real data at all? You betcha!

First off, “###!###” is not the title of a playlist I’ve ever created. Secondly, those aren’t any albums I’ve ever listened to. So, 🤷‍♀️

And just to round out this totally normal Catalina Tuesday morning, here’s a final surprise that actually doesn’t relate to Apple’s inability to operate a web service.

It’s just a text editor that’s been installed on my Mac since Mojave and has been working fine since upgrading to Catalina a month ago. But this morning? Nope. Just not gonna run. I should probably contact my Administrator like macOS suggests.

iCloud and services failings like this happen to myself and tons of other folks I know All. The. Time. I’ve seen wonky behavior like this for years on macOS. How can this stuff not be solid? Services revenue is literally the company’s new financial focus.

A Growing Chorus

I mean, when the folks you go to for some free, developer-friendly podcast PR start turning on you…

From a conversation with another developer friend:

And then there’s this piece from Warner Crocker:

Look I get it. These are big complex systems and sometimes things need to be worked out. So, I’ll grant some leeway for that. But I also get this. Apple has more resources at its disposal than most other companies and it needs to figure this stuff out. It should be embarrassing, but apparently it isn’t embarrassing enough to martial enough of those resources to fix iCloud, which is a system that Apple is relying on more and more as the backbone for services that connect these devices.

iCloud Security Codes

None of this stuff makes sense to normal users and is, frustratingly, never explained in detail anywhere for those of us who want to understand and know more.

Could they not add a “Learn More” option? Where’s the iOS equivalent of the macOS Help button?

In the past, iOS has even prompted my to enter the password for my Mac’s local user account. Again, as a developer, I kinda get and understand what’s happening, but even I’m still slightly confused about exactly what data is protected behind my macOS password vs my iOS PIN vs my iCloud Security Code, etc.

via James Kuang