I’ve had so many users message me about this today. It’s been down for several hours now, and judging past response times for downtimes, the time it’s taking is so much more in comparison. Really hoping for an imminent resolution. I’m in the process of integrating Apple Weather and so this is the worst possible timing.

I would also add due to today’s close proximity to the date announced that the API will shut down, a lot of users are jumping to the incorrect conclusion — understandably — that this is not a temporary issue but permanent. I’m getting refund requests as a result. This is hurting reputation and business. The damage can be terminal if this isn’t addressed urgently. I know there’s been acknowledgement that it’s being reviewed, but it’s highly concerning how many hours it’s been and still no fix (especially considering previous downtimes were usually insignificant). I’m sure the problem must be serious, otherwise it would have been fixed already. And that’s why I’m worried that the potential solution may be expensive, and given it’s less than 2 weeks since the API’s actual closure, that it may be decided that it’s not worth it. I really hope this isn’t the case, because if it is, I — and I bet many others — are in danger of severe consequences.

It was quite reassuring for the Apple frameworks engineer to reply to this thread a couple of days ago. Given no acknowledgement neither here nor status.darksky.net is quite concerning because it’s been probably a couple of hours now at least (based on my user reports). I know it’s the morning now Eastern Time, but I would expect this to be monitored 24/7. Fingers crossed.

Is this still down for everyone? Appears to be for me.

Anyone from Apple care to comment? I mean another difference between now and Dark Sky (even at the very end under Apple’s stewardship) is there was at least acknowledgement from the team about downtimes. This happened till the very end when there were two relatively long downtimes in the last week or so of DS API. That seems to no longer be the case? Surely it’s the same team then vs now?

Any updates on this? I’m facing the first at the moment. If no progress Apple side, any workarounds you’ve successfully figured out?

Oh that’s great news. But if you can spare a moment to confirm what what this means practically speaking. Do I need to build on 14.2 for this to work, or does the user need to be on 14.2? Or both? I assume user needs to be on 14.2 but then what about users who are not? They’re out of luck? Sorry for taking more of your time. Semi-related, as a possible workaround, I’m trying to get all songs for albums in library and then working my way from there. Did you try similar?

I think you (and I) may be one of the few people working with MusicKit and macOS, so it would be a big help if there were direct means to remain in contact. Would love to share what I’ve built. I’m http://mas.to/@bardi.

This might help: https://stackoverflow.com/questions/78123958/swiftdata-synced-to-icloud-with-one-to-many-relationship-between-2-models-result