That has not been the case for so long. Just like you can buy a chocolate bar for 10 cents at your corner store.Apple: It just works. 🙄
That has not been the case for so long. Just like you can buy a chocolate bar for 10 cents at your corner store.Apple: It just works. 🙄
This came out two days ago and addresses the widget issue IIRC.View attachment 1848570Today couple of minutes back I had. A small updatefor my iPhone 13 pro. The build number changed from 19A341 to 19A346. Though it didn’t fix the watch unlock.Didn find anything in the news.
Talk about a rollercoaster…“the GF and I are talking about not upgrading until the holidays.”
There was a rumor a month or so back that was indeed what they were doing. Not sure if that is related to this, but it's a fair assumption.My theory is that Apple tried to get Face ID working with masks, but gave up on it, but in the process it messed up unlock with Apple Watch.
Some is the correct term.Affecting “some” IPhone 13 users or all??
Because during that period, the focus was catching predators….Didn’t they have a spare iPhone and Apple Watch to test this? I wonder why do they have a couple of months for “beta testing” and this happens
lol you had me until you said holidays.Now I get that this software is more complicated these days and I get it takes more to get it right. Nevertheless.....there was a time not too long ago when I HAD to have the latest iPhone on launch day. There was also a time not too long ago when the newest iOS was released, pretty much in full, a few days before the new iPhones were released.
Now....it's just different. More and more bugs, more and more features get delayed, and my drive to upgrade just isn't as strong as it once was. My 11PM still works like a champ, and, to be honest, the Pixel 4a takes such amazing photos that now the GF and I are talking about not upgrading until the holidays.
Again, I know I'm being Captain Obvious here and this is just me and my use case, I just think it's wise to wait until this is all ironed out.
As many have said, perhaps switching to every other year release cycles for iOS might not be the worst idea.
Okay buy an Android phone then and enjoy one complimentary software update.I bet if you type the phrase "will be fixed in an upcoming update" into Apple's new Translate feature it will come back as "you are wearing it wrong"!
Apple has become a joke with their total lack of programming skills. If you are an unemployed software developer who can't find a company willing to hire you because you suck at it, then apply at Apple, they will hire you.
This isn't just with Apple. It is just the Agile software development these days. I was the same with you. But like I said, its not just Apple. I am no longer looking forward to the newest Windows feature updates or Windows 11. Or newest Visual Studio. Or newest Adobe programs. I have been through bad upgrades after bad upgrades after bad upgrades long enough where I no longer look forward to always being on the latest.Now I get that this software is more complicated these days and I get it takes more to get it right. Nevertheless.....there was a time not too long ago when I HAD to have the latest iPhone on launch day. There was also a time not too long ago when the newest iOS was released, pretty much in full, a few days before the new iPhones were released.
Now....it's just different. More and more bugs, more and more features get delayed, and my drive to upgrade just isn't as strong as it once was. My 11PM still works like a champ, and, to be honest, the Pixel 4a takes such amazing photos that now the GF and I are talking about not upgrading until the holidays.
Again, I know I'm being Captain Obvious here and this is just me and my use case, I just think it's wise to wait until this is all ironed out.
As many have said, perhaps switching to every other year release cycles for iOS might not be the worst idea.
Are you saying working from home is the cause for this? Because Apple (and Microsoft and Adobe and many others) have been suffering for years lately on these regular updates.Ah, some more of that amazing "work from home" they claimed to have as the reason for allowing them to continue to work from home showing its face again. Yikes.
Didn’t they have a spare iPhone and Apple Watch to test this? I wonder why do they have a couple of months for “beta testing” and this happens
View attachment 1848570Today couple of minutes back I had. A small updatefor my iPhone 13 pro. The build number changed from 19A341 to 19A346. Though it didn’t fix the watch unlock.Didn find anything in the news.
As a software developer, I don’t really understand how this bug wasn’t caught. It affects everyone, no? I can understand bugs that get through that affect a percentage of the user base — but how was this not caught? Certainly there wasn’t a last minute untested change that they just lobbed out the day before. This is odd to me. The widget issue too… but I don’t think that affected everyone.
There are many users on the forums without this problem, and it is widely known that the ones affected are much more likely to report.Didn’t they have a spare iPhone and Apple Watch to test this? I wonder why do they have a couple of months for “beta testing” and this happens
When apple was pushing for a return to office, many of the employees cited how productive they were and how much work they got done while working at home as reason to continue being allowed to work from home. Clearly with all of the bugs in the software, they weren't as productive as they claim.What?
I'm not arguing they haven't been suffering, but Apple seems to have gotten worse lately with this (Microsoft and Adobe have been terrible in this regard for a long time).Are you saying working from home is the cause for this? Because Apple (and Microsoft and Adobe and many others) have been suffering for years lately on these regular updates.