Are you waiting for a bug fix/patch? I tried to restore from backup and it didn't seem to work... Do you have any workarounds?
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.
iPhone Expect IOS 13.1.3 Soon
- Thread starter Darkhorse1
- Start date
- Sort by reaction score
Are you waiting for a bug fix/patch? I tried to restore from backup and it didn't seem to work... Do you have any workarounds?
iOS 13 has been a huge bug fest for me on both my iPhone 7 Plus and my iPad Air 2. The worst being a complete loss of network functionality and being unable to reset network settings (hangs) on my iPhone which required me to wipe my iPhone and set it up as new.
Other things I’ve seen since upgrading (off the top of my head so I may be missing some things):
1. Having Bluetooth enabled causing severe packet loss on other iOS devices on my Wifi network (2.4 and 5 Ghz). Restarting the offending device temporarily fixes the issue. This doesn’t affect non-Apple devices.
2. Missing notifications. I lost all reminder notifications on my iPhone for awhile, but they came back. Other notifications come and go on my iphone and iPad.
3. No sent mail sound on iPad. It’s set, it just never plays. Edit: It appears Apple changed things so the sound doesn’t play when do not disturb is enabled.
4. Weird screen glitches on iPad where screen is squashed sometimes in apps. Fortunately this can be fixed by going to home screen and back into the app.
5. When an app updates on iPad, it’s icon in the recently used section of the dock stops working until the app is moved to the dock and back to the home screen or the iPad is restarted. Tapping it does nothing.
6. Notes randomly don’t sync until app is killed and reopened.
7. Same thing with up next list in TV app and some shows just never appear on my iPhone.
8. Apps slower to load at times.
Other things I’ve seen since upgrading (off the top of my head so I may be missing some things):
1. Having Bluetooth enabled causing severe packet loss on other iOS devices on my Wifi network (2.4 and 5 Ghz). Restarting the offending device temporarily fixes the issue. This doesn’t affect non-Apple devices.
2. Missing notifications. I lost all reminder notifications on my iPhone for awhile, but they came back. Other notifications come and go on my iphone and iPad.
3. No sent mail sound on iPad. It’s set, it just never plays. Edit: It appears Apple changed things so the sound doesn’t play when do not disturb is enabled.
4. Weird screen glitches on iPad where screen is squashed sometimes in apps. Fortunately this can be fixed by going to home screen and back into the app.
5. When an app updates on iPad, it’s icon in the recently used section of the dock stops working until the app is moved to the dock and back to the home screen or the iPad is restarted. Tapping it does nothing.
6. Notes randomly don’t sync until app is killed and reopened.
7. Same thing with up next list in TV app and some shows just never appear on my iPhone.
8. Apps slower to load at times.
Last edited:
I pulled out my iPad Mini 2 and iPhone 6 and they're running 12.4.2. It's a nuisance when I enter information on my iPhone 7+ and it doesn't sync so I have to go over to my Mac and type it in over again. Stuff syncs properly on my devices that can't run 13. So no, not any really good workarounds. I just have to wait for these bugs to get fixed. I can use my old stuff for some things but I'd rather use my new stuff.
I have the feeling that they have really destroyed their operating systems. So many bugs and issues are not normal in my opinion. They should rewrite all OS‘s new.
Software is a very complex business and that's not practical.
Quality is a process and Apple's process is sorely broken right now. Unfortunately there's a lot of that going around the industry. It's definitely not just Apple.
Apple’s business model seems broken.
The idea of having every new piece of hardware and software being released in the fall.
The timing schedule and allocating resources is not working.
In 30+ years owning Macs its only gotten worse. OS X was never ready on day one, more like at the end of each version.
Microsoft is beginning to realize they can’t rely on automated testing tools as much and they needed to invest in people to do more of the testing.
Yes it is hugely complex. I have a hunch even the compilers have their own weaknesses.
Hopefully more people and more time to do their jobs. Can you imagine ending the yearly churning out new iOS and phone?
The idea of having every new piece of hardware and software being released in the fall.
The timing schedule and allocating resources is not working.
In 30+ years owning Macs its only gotten worse. OS X was never ready on day one, more like at the end of each version.
Microsoft is beginning to realize they can’t rely on automated testing tools as much and they needed to invest in people to do more of the testing.
Yes it is hugely complex. I have a hunch even the compilers have their own weaknesses.
Hopefully more people and more time to do their jobs. Can you imagine ending the yearly churning out new iOS and phone?
At this point, I'd trade quality over new features. Yes, I can work around problems but I like to have confidence in the products that I buy, that they will work.
What’s annoying is everyone thought Apple turned around when iOS 12 came out and it was nearly perfect. Apple put a lot of focus into bug fixes and stability for iOS 12. For iOS 13 it’s was like they simply didn’t care at all. I mean when the U.S. Government warns its employees to not install a major iOS update, you know something is very wrong with Apple’s QA process.
Quality is not rewarded in software. Financial rewards go to developing new features; not ensuring the quality of the new or old features. So software engineers treat development and quality accordingly. You can push engineers to focus on quality using a big stick and it will get better temporarily but they will just go back to the usual metrics once the push is over.
I would disagree here. I am leading Software Development team and I work in software company. Our philosophy is putting quality and stability on the first place. Yes customers want new features every day. However customers also appreciate good quality products. So yes software companies do put quality high enough.
What happened with iOS is something that happens in quite other software companies though. Lack of plan. It is pretty evident that things were rushed. They either changed a lot of things in the last moment or did not size properly the amount of work that was needed for this version. It is evident that this version was not thoroughly tested and is premature. They released it like that because they did not have a good way to provide a stable version with lesser features. Meaning everything was merged and interconnected and they had no option to quickly extract what is working from what is not working.
I also would not be surprised if they focused on some features too much and delayed the delivery of the final version for regressing testing. As a result not everything was tested thoroughly and is now being tested by the end users/customers.
I’m also a software engineer and I agree with all this, but it applies to software companies, which Apple strictly is not.
In a normal software company the release of iOS 13 would have been pushed back at least a month (possibly two) to stabilize it, but because Apple ties their new yearly hardware releases to new software that wasn’t possible. Apple was not going to push back the release of the iPhone 11, so they released what I would consider alpha software as a release version and was forced to quickly release 3 patches in less than 10 days to fix major bugs. What makes things worse is that Apple did pull a bunch of features (iCloud sharing for one) from the 13.0 and 13.1 releases and still managed to release a buggy mess.
Are you working in a large company or a small company? Stuff is a lot different in very large companies. There's a lot of complicated politics and the power is with development, not the quality folks.
Good point that Apple is not pure software company. That is indeed true. I also agree with the fact that they would not push back the release of a version because it is tied to new phone. That is completely true. However it also means better planning. Like very strict one. Also better testing practices.
What I am trying to say is that if you know that this is your schedule and it is strictly to be followed you need to plan better to make sure that you fit in those restrictions and to have good risk management.
[automerge]1570901559[/automerge]
Bigger company. However we have dedicated teams to quality (DEV and testing) and they have KPIs to follow. This way we focus on both quality and features development.
A 1-year schedule is pretty aggressive for very large complex projects.
Yes it depends on the project I agree
. We do 6 weeks release and it is pretty intensive. Obviously we are not talking about such projects. Our business model is different. We deliver new features every 6 weeks. While the project is smaller it is really intensive because we do also patches after every release. Sometimes to be honest I would prefer to work on a bigger project like that than to follow such intensive release process. That being said we also have bigger projects that last 2 years. We are just on the finish line of such one. We still however delivered the features incrementally and allowed users to play with the system fully communicating that it is only for demo purposes.
So yes I know what it means to plan such huge projects but I still it is possible if you have proper project management.
Fairly certain things like that are done with many major updates for pretty much all kinds of OSs and software by not just the US government but many companies, usually having nothing to do with any particular quality type of concerns and simply related to overall IT policies where they want to test things out in their particular environments with their particular software and processes to make sure everything is fine before they let all the employees update.
Are you talking like 20,000 developers big? 5,000? 500?
I agree on better planning but there's so much stuff that goes on - competitive situations where you have to add a feature, people going on vacation or maternity leave which can be disruptive or losing people to other companies that have a lot of experience with a code or test base.
Our security vendors take 6-9 months to update their software after a new macOS release so we have to wait for quite some time before upgrading. This isn't so bad if the release is really buggy like Catalina. I usually set aside significant time to upgrade my systems as I want full backups. I usually like to create the new OS on an external SSD to play around with it before moving to it.
I am talking over 15000. Of course the company is doing a lot of different stuff. Different units, departments etc. Not every team is working on the same product or same component.
I agree with you. You will never find the perfect plan. However there is huge difference between producing version with bugs, producing version with one major bug and version with numerous major bugs. Currently iOS 13 falls into the latter category. IMO to produce something like that, not just one thing has gone wrong, the overall plan was missing. And based on what I have gathered this is not the first time either. iOS 11 seems to have similar history. This shows that company is also not learning from their mistakes and improve.
Also agree with you that sometimes marketing or sales could force R&D to rush Development. It is not just R&D fault for sure. It does seem that certain features have not been though through and have been added the last minute.
[automerge]1570903427[/automerge]
I tend to agree here. Obviously it depends on the company. In my case our company conducted iOS 13 tests. Obviously not good enough because I received the notification on Thursday that I can install and I did. Not a good decision as it was not working. Nevertheless my point stands. Big companies do test OSes before upgrading their employees to it.
In hindsight I can categorically state that I would have stayed on 12.4.2 if I had known how bad things were. I really wanted iPadOS but a better UI is not worth the reliability problems. My kids and wife are on 12.4 and I've heard no complaints from them about their devices.
One odd thing is that my iPhone 7+ has battery issues and the battery is new. My iPad doesn't have battery issues. My belief is that there's a voice/text issue with the phone spending more power trying to talk to the tower. I am running the phone on Low Power mode and that gets my battery life back to being decent. But I shouldn't need to have to do that.
I would have stayed with iOS 12 too! I did mistake this time - relied only on the test conducted on the company and the feedback in the iPad forum. Next year I will read in this forum before upgrading.
Is the iPad cellular? If it is not your theory might be correct!
The iPad is WiFi Only. I saw a thread on voice-drop issues this morning and wondered if there are issues in the voice call software. I'm also reading about battery issues on the iPhone 11 which is really unexpected given the much bigger battery on it.
For now I don't have issues with the battery on my iPad as well. It is WIFI only. I do sense a bit more battery drain on my iPhone though but I need to monitor it a bit more to confirm.
When is this “soon” going to happen?
I suspect you are gonna say “told you so” when it gets released, even if it happens month after you said.
I suspect you are gonna say “told you so” when it gets released, even if it happens month after you said.
Seems like we are well over “within the next week”.