Really? "You're holding it wrong!" never happened, right?This would never have happened under Steve Jobs. Not being funny.
Really? "You're holding it wrong!" never happened, right?This would never have happened under Steve Jobs. Not being funny.
What can't be confirmed? That iTunes can't distinguish different versions of the same song and replace it with whatever it have available? Older/newer/concert/remix etc. If it can't then it's not a "match".
iTunes Music can't distinguis different artist using same name, it lists them as one artist.
User error, my ass.
Really? "You're holding it wrong!" never happened, right?
Really? "You're holding it wrong!" never happened, right?
Apple are at fault no matter what. They don't make this stuff clear. In the information vacuum people make assumptions based in how other services work. Anybody who's made this error I don't blame one bit.
I'm not sure I understand your post - the headline states that the deletion glitch is confirmed, and the quoted text says the same thing
Headline: Apple Confirms Music Deletion Glitch...
Quote from Apple: "In an extremely small number of cases users have reported that music files saved on their computer were removed without their permission..."
K.I.S.S. a concept IGNORED by all Apple Developer Geeks.Bugs, bugs, bugs, never ending story of today's Apple...
It doesn't say if that deleted music can ever be recovered - or did I miss that?
But none of those are because of a programming issue.
Probably can be recovered if you use Time Machine. As you should.
If not, can your music be recovered if your MacBook is stolen? Or if it breaks, which one day it will? (I wonder how many people buy a laptop and use it until it breaks).
But it happens.Failure to match correctly isn't the issue at hand here. The issue is matching failures or other issues in the iCloud Library getting written back to the local, primary library, which should never happen, and would be a serious bug.
More like people would simply have given Apple a free pass under Steve Jobs. Products and services were never perfect nor bug free under Steve Jobs. Bad things happen. Live with it.
Bugs, bugs, bugs, never ending story of today's Apple...
That's nice if it works. But sometimes you just can't reproduce it. Because a problem happens only if certain conditions are met that have nothing whatsoever to do with the actual problem. You might have a bug that deletes songs but only if the last album in your library has more than 25 songs. That's probably something that would hit less than 1% of users.But that's a rather hacky approach to it. I believe in trying to find the root cause, even if I have to sit for hours stepping through code. Eventually I do, and it is something very simple and very easily over sighted. The end result in fixing it is much better, nicer, and cleaner, and avoids the constant loading on of needless subroutines to check for something, that is probably as small as someone using I instead of j.
If Apple knew that, it would easy to fix the problem. I've had crashes that would only happen after six o'clock in the afternoon. I've had crashes that would only happen if your hard drive had a name with an odd number of characters. I've had a crash that only happened when you picked one particular shade of blue in a colour picker for some text. There were 256 colours to pick, and one of them crashed. All others worked fine.What unique situations?
So what? There are lots of different ways to lose your music, and people who have their laptops stolen will not come to MacRumors and complain about it. The only way to be save is to have a backup.But none of those are because of a programming issue.
While a lot of people seem to what to laugh at the "Steve would never have allowed this" comments, they seem to forget that Steve DIDN'T allow a lot of issues to be there, and did everything possible to make sure that Apple products were GREAT to use and as reliable as possible. Apple didn't get everything right under his leadership, but they did get things right MOST of the time. It certainly wasn't a situation where almost every software release had major bugs in it like today, or products were released with half finished operating systems (the Apple Watch).That problem came from Steve wanting a revolutionary design for the iPhone 4. This bug is just a result of poor software...
I don't know why people keep laughing at the "Steve would never have allowed this" comments. If you followed Apple under Steve Jobs, surely you realise there's an element of truth to that. Steve cared about making great products, where as Cook only cares about the business side of things.
This video sums up Apple's current situation
How do we know that the people responsible aren't being taken to task for this issue?While that is undoubtedly true, it was also true that releasing obvious bugs was not the way to get on Jobs good side. Cook seems to be very nice and we just don't hear about irrational behavior regarding Cook. I just get the impression that when confronted with a serious bug Cook's response is something like, "Oh well, another bug. Bugs can't be prevented, so how was your holiday?"
That's the difference.
It is possible that a bug deletes files but only under particular circumstances. When you say "unpredictably" you mean "under particular circumstances, but I cannot figure out which circumstances". It is entirely possible that nobody in QA will ever create exactly the circumstances that are needed to reproduce the problem.Bugs happen although ones that unpredictably delete files should never get pass QA.
Glitch? I'm surprised Apple PR didn't spin this as a feature
I'm sorry to hear that. It really does seem you in the constant <1%.Lucky you. Just yesterday iCloud Mail was down for me for hours.