Yes true my coworkers and I surely don't have the full picture on the status change of the job
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.
Apple Releases iOS 13.1.2 and iPadOS 13.1.2 with Fixes for Camera, iCloud Backup, HomePod Shortcut, and Flashlight Bugs
- Thread starter MacRumors
- Start date
- Sort by reaction score
Yes true my coworkers and I surely don't have the full picture on the status change of the job
That would be fine but it just does not work like this. For a complex software like iOS it's just impossible to do quick releases. Without proper testing (which requires weeks), some bug fixes will turn into new bugs. At certain (super fast) release rate, the rate of bug creation exceeds the rate of bug fixing.
When Forstall got fired, I remember reading many key members of the iOS team, who were loyal to him, left.
Got some sources to back this up, or is it just conjecture? Seems to me Apple knew exactly what they needed to do and wasn’t a haphazard release schedule.
I am also hearing impaired, though (lucky for me) I'm able to cope with off-the-shelf Bluetooth devices. I tried, fruitlessly, during the iOS 10 years to argue with Apple's Exec Team customer relations folks that there is an ADA compliance issue with their policy of refusing to allow impaired users to downgrade and skip updates (once the SHSH signing window closes). They disagreed. But early iOS 10 was also a Bluetooth nightmare, so much that I completely skipped iOS 11. I jumped to iOS 12.3, but it isn't as stable as iOS 10.3, I'm back to my headset often disconnecting or the Bluetooth stack resetting during calls or iOS just deciding not to route calls via Bluetooth randomly. For as much as Apple likes to toot their horn about their Accessibility chops, their obvious failure to test Bluetooth adequately calls into question their commitment to the hearing impaired community. It isn't like Bluetooth is a nascent technology… the Sony Walkman phone I had before getting the very first iPhone worked perfectly, 100% of the time with the multiple Bluetooth headsets I owned, and that was over a decade ago… the iPhones have been consistently troublesome each and every year. EACH. AND. EVERY. YEAR.
Yes I have - decades of software development. Believe me, Apple did not plan for these rapid releases. They would never do this if iOS did not have so many critical bugs. And here is some anecdotal evidence: Touch issues after 13.1.1 on 11 pro. People are reporting new issues with every patch release. Just check iPhone section of MR forums.
Agree completely. iOS gets so much more complex and advanced every year, but many here inist on comparing the number of bugs to work out to five year old software.
I understand your plight, even more as new updates arrive. I’m seeing that many of the problems the deaf community is facing these days are with the Bluetooth stack and it makes me wonder if the folks who maintain the Bluetooth standard would be better informed if they took some time to speak with folks who rely on hearing aids and cochlear implants. I would love to find a way to contact Apple and tell them that I use cochlear implants and would be happy to volunteer with their accommodations team to improve things for the hearing impaired/deaf community.
Mine involves the app Yonomi to control my Harmony hub. So I can tell Siri to turn on the office TV or to turn on the Xbox. I'll play around a bit more tonight. I'll make a couple more test ones too.
Everyone is voicing their opinion about updates. Just laughing...
Honestly iOS13 build has been amazing. Overall the experience over iOS12.4.1 has been well snappier and animation speeds seems slightly faster. The updates only address a small portion of issues that "some users" are experiencing and not "all users". From quicker FACEID to opening apps iOS13 has been a solid upgrade.
Honestly iOS13 build has been amazing. Overall the experience over iOS12.4.1 has been well snappier and animation speeds seems slightly faster. The updates only address a small portion of issues that "some users" are experiencing and not "all users". From quicker FACEID to opening apps iOS13 has been a solid upgrade.
If the release was really amazing (as you think) Apple would not need to rush with release patches. Apparently they are aware that users are having tons of issues.
my iphone 7 didn't show any of the problems that 13.1.2 supposedly fixed, but now with the update my apps crash routinely, and ive not done anything to my phone but update
I offered Apple Exec the same… as long as they provided me a tester unit iPhone SE (the model I have) to install iOS beta builds on to test. They told me to go buy one. LOL. Could get pay-go SEs for $129 at Target, and I had AppleCare and—at the time—a nonfunctional telephone because the Bluetooth stack would consistently crash when accepting a call with every headset I owned, meaning no headset answering, but Apple refused to provide a refurbished iPhone SE that I was willing to return on demand. It was at that moment that I realized that some of their Accessibility self-congratulating was undue. (And that was from conversations with Exec Team liaisons, not some Tier 1/2/3 AppleCare support personnel!) Bluetooth and audio path routing simply shouldn't be the moving target it has been each and every release for the past 5 years, just makes no sense… unless Apple just doesn't do proper QA. Which—given my experiences, and given that I have a Notes list of unit tests -I- now perform on a tester iPhone 6s prior to upgrading to any new iOS version and routinely find regressions—must be the case.
(I'll add: three years ago when I was struggling with iOS 10, and interfacing rather consistently with Apple Support, it was frustrating then that I never was able/allowed to interface directly with engineering. I had open Apple Support cases, open Bug Reporter radars, and a liaison with the Exec Team, but I never ONCE got any kind of test plan back from engineering, or even any kind of direct interaction at all. I was the one making test plans up, documenting them, and passing them back into the "black hole" that is Apple. And consistently, I would be told when a new release was dropped to test, but not that my issue had been addressed! It was more like, "Have you tested on [new] release?" "No… was my issue specifically addressed?" "Don't know, you'll need to test." How is that any way to run a computer company?? And, often, it either wasn't addressed—meaning it was a good thing I didn't update my daily-driver iPhone or I'd have lost my telephone—or it was partially addressed such that I caused me to have to generate a NEW issue all over again with Support and Bug Reporter. And then, I'd often get my radar bounced back as "works as intended" or asking for such a voluminous amount of debug information that it was clearly intended to make me do all the leg-work. It was infuriating to the point I gave up. Which doesn't help me, you, the community, or even Apple. But that was -their- system. And, from all evidence, still is.)
Last edited:
Wowsers, that’s astounding. I can’t help but wonder if you caught someone on a bad day.. one bad apple doesn’t spoil the whole bunch.
So no real proof other than your claim of decades of software development, which seems like 90% of macrumors. New bugs in every release? That’s a given.
Seriously... I will say Apple's execution of this update has been less than stellar, but overall the substance of the actual update itself has been fantastic. I love all the new features, both big and small.
Yeah I completely skipped Yosemite due to all of the WiFi issues it had, very slow ping, etc. If Catalina has a bunch of issues I may skip it as well.
My phone is running warmer than usual - -especially the back top just near the camera lens. I'm not even doing anything, it's just sitting on my desk.
And battery is draining much faster since this latest 13.1.2 update late last night. It can't be still "indexing??"
I'm on XS Max. Anyone else? Ugh!
And battery is draining much faster since this latest 13.1.2 update late last night. It can't be still "indexing??"
I'm on XS Max. Anyone else? Ugh!
Apple: HomePod Shortcuts now work.
Real Life: HomePod Shortcuts do NOT work.
I have no idea why sites like Macrumors etc haven't picked up on how Siri Shortcuts simply does not work on Apple Watch or HomePod right now. It's a joke, really.
Real Life: HomePod Shortcuts do NOT work.
I have no idea why sites like Macrumors etc haven't picked up on how Siri Shortcuts simply does not work on Apple Watch or HomePod right now. It's a joke, really.
Come on. iOS 12 was a real mess. This has been, apart from the mail app, the most stable beta even from beta 6. All releases were pretty good for me.
This pace of updates, while annoying to execute, is good. You can handle 5 minutes without the phone while it updates?
[automerge]1569981079[/automerge]
It just means the devs work weekends. Should we discourage that?
This pace of updates, while annoying to execute, is good. You can handle 5 minutes without the phone while it updates?
[automerge]1569981079[/automerge]
It just means the devs work weekends. Should we discourage that?
And my rebuttal is this:
Lenovo Yoga 3 runs perfectly on 1903 for me. Perhaps YOU'RE not as good as you think.
OTOH iOS 13 ran like garbage on my XS Max. Rolled back to 12.4.1. Bliss
At least Android updates usually don't neuter half of the phone.
They're typically very solid and don't cause any problems somewhere else.