Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

Apple Warns That Restoring From Backup Can Cause Apple Music Bug on New iPads and iPhone 13 Models

Once again, another reason, if you have a production device, or are using a device for real work, don't jump on the day 1 bandwagon....

Stay back, wait at least until the .1 release....some wise words...I am still on Big Sur and iOS 14 because I knew something like this would happen with iOS 15 when it was released...
 
  • Disagree
Reactions: dylanthomas
anshuvorty said:
Once again, another reason, if you have a production device, or are using a device for real work, don't jump on the day 1 bandwagon....

Stay back, wait at least until the .1 release....some wise words...I am still on Big Sur and iOS 14 because I knew something like this would happen with iOS 15 when it was released...
Click to expand...

This bug is literally fixed in the .0 release. The released iOS 15.0 does not have this bug.
 
I have a 12 Pro Max and since I updated to iOS 15 I cannot play some radio channels from Apple Music. It does not work anymore. So annoying. I need to plays my favorite radios through a third party app! Fix this Apple!!!
 
cmaier said:
The point is, their stable release doesn‘t have the very problem we are talking about. The release on the shipped phones is not the stable release - it’s a release that corresponds to the developer beta from about 2 weeks ago.

What this story shows is that the *release* is fine, but the beta is not. So what’s the problem?
Click to expand...
If that is the case, then it’s Apple’s fault for installing beta software on production devices.
 
  • Haha
Reactions: Shirasaki
BuddyTronic said:
Well, whatever is what I would say.

I'm wondering if there was a bug in Apple Music or whatever iTunes you want to call it, previously.

I have a total mess of my music.

About the only thing that works nicely is if I call out for a song and artist or song and album, using Siri.

Lots of headaches with Apple "iTunes" legacy stuff.


IN A NUTSHELL:

Apple needs to go through the use cases of it's customers and see what a real human might be doing to arrange his or her music. It might take you 30 seconds or less to find a problem with the interface. Fix that please. It's a mess.

You say there are "bugs" coming if I update from backup? Well there was bugs before, so why would I care? Seriously.
Click to expand...
Exactly!

I'm receiving my new iPhone today and I can't imagine how I would be able to tell the new bugs in Apple Music from the old.
 
upandown said:
Why Apple? Why is this okay?
Click to expand...
Because they just don’t care anymore.
They have gone from being known as the company where “it just works” to every device being littered with bugs.
I’m hoping Tim Cooks replacement has more of a Steve Jobs type attitude and doesn’t accept this kind of crap.
 
  • Like
Reactions: Alex_Mac
singularity0993 said:
The point is, Apple software quality is declining. Their “stable” releases are no longer as stable as they used to be, and no longer meets customer expectations.
Click to expand...
Exactly that. Every year their software is getting worse and worse with more bugs. The improvements they make are incredible but they need to keep on top of the issues they keep creating.
 
  • Like
Reactions: Alex_Mac
So annoying. I am tempted to set the new phone up as a new iPhone but will that carry over my health data and will it lost my activity records with my Apple Watch? What’s the best way to get this data to a new iPhone?
 
I got one of the new iPad Minis and updated the software and still have the issue. My music is set to sync but it's not working. I've got a couple of random albums that came through when I set up the Mini but they're not what I have in iCloud/on my other Apple devices.
 
teflocarbon said:
I got my 13 Pro Max today, it had iOS 15 with an update available out of the box. I updated and had no issues with Apple Music. I didn’t test it prior to the update. I did have an issue with all my apps going into other but it resolved itself after 15 minutes or so.
Click to expand...
So setup as new, then erase and then restore from backup right?
 
jbachandouris said:
Update the NEW device? That makes zero sense.
Click to expand...
It makes perfect sense. Additional issues - this bug plus security issues - have been found since iOS was signed off and the phones have been being manufactured, boxed shrink wrapped and shipped.

I’d rather they released the update than sit on it for a week or three!
 
  • Like
Reactions: severe and WhiteHawk
Since you're prompted to install updates during setup these days, I can't see an issue with just doing the update when prompted then continuing with the setup as normal. Shouldn't be any need to do the update after setting up as new and then restoring it again post-update.
 
OS X Dude said:
Since you're prompted to install updates during setup these days, I can't see an issue with just doing the update when prompted then continuing with the setup as normal. Shouldn't be any need to do the update after setting up as new and then restoring it again post-update.
Click to expand...
I didn’t see a prompt to do a software update during the set up
 
anshuvorty said:
Once again, another reason, if you have a production device, or are using a device for real work, don't jump on the day 1 bandwagon....

Stay back, wait at least until the .1 release....some wise words...I am still on Big Sur and iOS 14 because I knew something like this would happen with iOS 15 when it was released...
Click to expand...
Well there's always some major bugs on day 1.

My 13 Pro has been delivered, by the time I get it out the box in a week or so, I am sure Apple will have issued a .1 patch, in addition to the update that is already available.
 
This update brings iOS on iPhone 13 Pro from 19A341 (Pre-RC) to 19A346 which is the final version of iOS 15.
 
So must we power up the new device, skip through setup, run the update, erase, THEN restore from backup? OR, can you unbox, setup\restore from backup, THEN install the update. Article doesn't really say one way or the other.
 
rotlex said:
So must we power up the new device, skip through setup, run the update, erase, THEN restore from backup? OR, can you unbox, setup\restore from backup, THEN install the update. Article doesn't really say one way or the other.
Click to expand...
Easiest way would be to turn it on, DFU it and restore via Finder/iTunes. Once done, then set up.
 
  • Like
Reactions: rotlex
All these bugs make me think that maybe Apple thought that, fortunately, they hired engineers who agree to work for a little $$$, but they really get a lot more $$$$ from someone, for example, from Google and do the work on the wrong side.
 
  • Like
Reactions: snek
rotlex said:
So must we power up the new device, skip through setup, run the update, erase, THEN restore from backup? OR, can you unbox, setup\restore from backup, THEN install the update. Article doesn't really say one way or the other.
Click to expand...
The first way you described is the way to go.
 
  • Like
Reactions: rotlex
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back