Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
- Status
TheYayAreaLiving 🎗️
Suspended
Happy Monday!
I can't believe it's May already. Just about a month left before WWDC kicks off.
Hoping for a new build/update gets drop sometime this week. I hope everyone is going to have a wonderful work.
I can't believe it's May already. Just about a month left before WWDC kicks off.
Hoping for a new build/update gets drop sometime this week. I hope everyone is going to have a wonderful work.
I wouldn't be surprised to see 15.4.2 this week or next. It feels like 15.5 may still be a little ways out and the last public update was March 31st.
What is this obsession with 15.4.2? As I pointed out last week 15.4.1 was released to deal with a security flaw. Absent another such flaw, why would they release an interstitial release when 15.5 will likely be released in 3 weeks, 4 at most? This isn’t wallpaper: they don’t have to fix every issue continuously.
They should. We pay for that, among other things. Perhaps they should adopt the Windows update cycle.
Dont make the software support just long in time. Make it much more frequent. It that means working on weekends, or no rest at all so be it.
We needs our adrenaline rush, after all...
In a more serious note, Apple, please, show a little more care for your music streaming service. Its so bug ridden right now.
Remember when Safari tab syncing was broken for a few months and that turns out to be because they were doing a huge rewrite of the whole syncing backend?.
I hope now its the same case with Icloud Music Library, for example. Metadata changes not sticking/reverting has been an issue for months now, and the worse thing its that it has been acknowledged by Apple Care.
I think this is tongue-in-cheek, so I will refrain from a response.
Of course it is, up until the "in a more serious note" part yes. Don't know why you have to refrain yourself, though.
You explained the other day (and I agreed with you), why an IOS 15.4.2 release didnt make sense from a logical, software development point of view and yet, given Apple tendency for leaving bugs "alive" for months, some of us hope for another ASAP update to specifically fix them (in my case, pertaining Apple Music) even if it breaks Apple usual calendar of software releases. That´s all. It´s a wish.
I am not entirely sure, though, of why insisting on this means that we are "obsessed" with software updates.
Last edited:
iOS 15.4.1.1 when
Could be another way yes, with the Apple Music fixes that are already incorporated to the latest 15.5 beta build. I should not have to wait until memorial day. Its a paid service, after all.
The “obsession” comment refers to the insistence by some here that there needs to be a 15.4.2, not to updates in general.
We here all like updates. That’s why we’re here.
My point is that updates need to have some basis and not just be updates for the sake of updates. Minor (X.x.x) updates tend to be issued for discrete, and usually significant reasons. Examples would include major bugs or bugs that affect large numbers of people. Major security issues or potential zero day exploits would also be among the reasons for a minor update.
Every release - public and beta - has issues. And many of those issues are addressed in subsequent, planned releases. Some sooner, some later. But Apple is not going to drop everything for every bug every time. That’s what I think it is being asked to do here. And I don’t see any reasonable basis for it.
Because if your not on the beta train, what's there to speculate about? 😂😆
(I hear ya buddy)
Then I suppose that Apple needs to start considering fixing bugs in their core apps (music, safari, mail), without having to update the whole OS for it. Surely an app update would be more convenient and feasible for these cases.
Also, I think that Icloud Music Library been essentially broken for several weeks (and again, this is something currently acknowledged by Apple), would qualify as a major bug for me (not of the OS but of Apple Music), and i consider it completely unacceptable for a paid service.
But your are right, you dont need to update the whole OS for that. Just issue an update for the music app.
I noticed that Music was fixed for me after the update last week, so maybe it was "fixed" for the majority of people and is only an issue now for the minority?
Worth dropping them a message to say you don't feel happy about paying for a service that is a little half baked recently. They will check out your claim is legit with you on the phone and then probably, happened to me, offered 3 months free.
Worth a shot right. Ease the wound.
Also what steps have you taken to fix? or you just updated and thats it?
I would try:
• Logged out of iCloud and back in.
• Re-install just the iOS using the IPSW file.
• Encrypted back up restore - last resort
• Call Apple
No steps taken since Apple Care told me on the phone that they are aware of the issue and working on a fix.
Yes, the latest 15.5 and Monterey beta fix everything Apple Music related, but I personally do not use beta software, nor do I intent to.
Got it....sooooooo...you know the fix is coming...and as noted above, the issue doesn't actually "break" Apple Music or make it unusable.
If it did, a fix would be issued the next day if possible as Apple did when they did accidentally break it in CarPlay. It was a universal issue that crashed the app when opening on CarPlay (you could still open on the phone and make it work). Fix was pushed out the next morning.
I know. This all started because I supported the sentiment of a fellow Macrumors participant that wished that 15.4.2 were released before 15.5, and I responded that I think it was appropiate to do so. @gwhizkids explained why he didnt share that view, and I ended suggesting that perhaps Apple should considering releasing bug fix software updates of their core system apps instead of tie them to general OS updates. That way we wouldnt have to wait so much for bugfixes.
Yep...so, a few things:
1) This is the wrong thread for this conversation...hah (and I'm just as guilty as you, but I tend to forget where I am in here sometimes.)
2) Totally agree with everything @gwhizkids said regarding the minor update release, but that also means that as I clarified, the issue is neither a security issue OR a widespread issue/one that affects the use of the app. It is an annoyance at best. While it seems like it should be a no brainer to release a x.x.1 update to fix it, there is a marketing/optics issue around that as well (probably the main reason they don't do it).
3) With all of that being said...I have no speculation on the next release right now.
Yep...so, a few things:
1) This is the wrong thread for this conversation...hah (and I'm just as guilty as you, but I tend to forget where I am in here sometimes.)
2) Totally agree with everything @gwhizkids said regarding the minor update release, but that also means that as I clarified, the issue is neither a security issue OR a widespread issue/one that affects the use of the app. It is an annoyance at best. While it seems like it should be a no brainer to release a x.x.1 update to fix it, there is a marketing/optics issue around that as well (probably the main reason they don't do it).
3) With all of that being said...I have no speculation on the next release right now.
In your defense, I do think this is the right place as we are indeed speculating on the need for a hypothetical 15.4.2.
But I am done with this topic now. On to 15.5!