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.
All Devices iOS 13.4 Beta 3 ― Bug Fixes, Changes, and Improvements
- Thread starter Banglazed
- WikiPost WikiPost
- Start date
- Sort by reaction score
- Status
I thought it installed faster on my three devices.
But, so far, everything seems to have slowed down. Hopefully things will speed back up soon.
Works on my XR as well. But then so does Mail, so maybe I just a magic phone!
Apple’s priority is to sell hardware. So the primary purpose of this release will be to support the new PowerBeats and perhaps the rumoured upgraded iPads. Any bug fixes will just be icing on the cake if there’s spare time and engineering capacity. The imperative is to not delay hardware shipments.
You probably don't check national news from the UK, but you might have seen this coverage from a familiar source...
Apple Working on Fix for iPhone XR Users Experiencing Issues on UK's O2 Network
Apple has confirmed that the iPhone XR is not working as it should on the O2 network in the U.K., reports BBC News. "We are aware of an issue...www.macrumors.com
So my takeaway from this is that Apple learned about it and worked on it/ fixed it. That’s a far different story than they did nothing, which was the clear import of the post to which I was responding.
Bugs are going to happen. Millions of lines of code and dozens of supported SKUs.
Let’s not create false narratives that they aren’t doing anything about when apparently they were.
I take it you had @Stuey3D under observation since last July? He claimed to have encountered the bug during the Beta cycle. As of January (in the article) it was still not fixed. It took until 13.3.1 to fix it.
I'm actually not sure why I'm bothering to write this because your takeaway from both the news article and the the post you were replying to is pretty odd. Unless you've confused Stuet3D with the previous poster to which you replied, since he replied to that...
@Stuey3D didn't say they did nothing... it doesn't even need paraphrasing, it's clear as day.
"this was only just fixed on 13.3.1
If it takes Apple 6 months to fix a major bug that prevents a mobile phone from working as a mobile phone, I dont trust them to fix anything in a timely manner."
Bugs are going to happen, but they should be triaged and one where "Customers have been unable to make and receive calls and send and receive text messages, as well as get a reliable 4G internet connection for using apps on the go." should be high up the priority list. It's not about fixing them when you get around to it.
Yes. I think that's fine, as u and ü aren't the same letter and there is no ü key to swipe over. I've gotten used to it.
In what direction?
ProMax on 13.3.1 - fw to rMB 2015, IPP 11 (13.3.1) and IPP 12.9 (13.4 pb3)
The IPP 12.9 does not get any non-iOS messages. The 11 IPP gets all.
If all of you (a significant minority) are that torqued up about this, just move on to Android and stop acting like the world is coming to an end because your complex computing device doesn’t always do what you want it to do.
Can you expand on that?
IPP 12.9 G2 on latest beta - mine actually delete. Or at least they are no longer in the delete or original folders.
Ahh if only it were that simple 'eh.
The problem is that Apple created an ecosystem that once upon a time worked well but now in recent releases are having a nightmare with, and as someone who has been in that ecosystem since the first gen iPhone I am pretty heavily invested in it. If I were to go to Android I'd loose:
iMessage
Facetime
AirDrop
Carplay (my stereo doesnt support android auto)
The ability to remote administer my daughters iPad through screentime
iCloud Photos
iCloud file storage
Airplay
and probably a bunch of other things I've forgotten, however the point is that myself my family and a lot of other family and friends also use these things and in the case of iMessage and Facetime there is no easy replacement on an Android phone that wouldn't require my friends and family having to mess about with other apps and services just to replace functionality that is built into the phone.
So yeah when my iPhone fails to work on my network and I report the issue to Apple on the public beta (which is the whole point of the public beta's) with a bunch of log files, and regular updates to said report, and the report also having a tag saying more than 10 reports of the same issue. Its kind of a big deal, so taking nearly 6 months to fix it is a joke and that is a bug effecting the main function of the phone. And As i was saying it was a big enough bug to hit the national news, it should never have gotten that far and even if it did accidently hit 13.0 releases there should have been a 13.0.1 to fix a critical bug of that nature soon as the software hit the public. iOS13 has been a shoddy joke of a release with the amount that is wrong with it, it makes iOS 11 look like the pillar of stability by comparison.
And I'm not sure why you seem to be defending Apple's recent shoddy software, you have to admit the quality just isn't there anymore
I think his very valid point though is that YOU had that issue and it obviously did not affect the majority of O2 users. The article only makes claim to a few tweets about it. As far as it making national news, on any slow news day, a couple of whiners tweeting about their phones not working is a "story."
It was a bug. Turning the phone off and on again seemed to fix it temporarily. O2 was probably part of the problem. I don't doubt for one second that if it was an issue that affected a large number of people with that one phone on that one network, Apple would have issued a fix within a week. It obviously wasn't that big of an issue.
Wow. Who weed in your cornflakes? Sorry if I’ve embarrassed you in some way by highlighting the mistakes you made!
[automerge]1582856448[/automerge]
A network, it should be highlighted, that had an iPhone exclusivity deal until 2009. They’ve had iPhones on their network since 2007 - and worked with Apple in the first instance - so it’s pretty shameful if a relatively new device has a bug like that. It’s not as if it’s a new network. 12 years.
Last edited:
I think it’s been more than adequately pointed out here by others that the O2 issue was reported by relatively few. So, no “ mistakes” here.
Frankly, between this thread and the AirPods Pro firmware thread, I am just sick of the whining. My experience is not perfect, either. The difference however is that I don’t expect it to be perfect. I am thrilled that I have a handheld device as capable as my 11 Pro is. If it has occasional hiccups, I’m not going to come here and cry about it.
It’s been conjectured, not pointed out. No evidence provided. I invite you to return to my previous post and see the mistakes you did make in understanding.
Or return to the theme to your own recent post. If you don’t like the whining switch to another thread and no longer follow this one! The marketplace is quite sterile! You won’t get much whining in there.
Does anyone else have an issue installing the iOS 13.4 Beta Ipswich using iTunes? When I select the file and click ok, nothing seems to happen and I cannot use it to restore with in iTunes.
So shoddy software with glaring issues is alright with you?
Do you think £750 phone that doesn’t function as a phone because the network freezes or looses signal is cool? And this want just a once in while occurrence, sometimes it happened multiple times a day randomly. Thankfully I don’t have any sick relatives or anything or I might not have been contactable, but for others I suspect that was a much bigger concern when their phone ceases to work properly as a phone.
As for only a few with the issue I’d get your point if it was the Daily Mail, The Sun or any other tabloid as they tend to jump on the few tweets make a story bandwagon but it was the BBC that reported it and they don’t tend to report just on a couple of Tweets.
I had fed back this issue to both O2 and Apple during the 13.0 beta phase, others also reported this issue and it was ignored for nearly 6 months when finally a press release was made because a lot of people obviously had this issue.
If it was a minor issue that only affected a few people do you think they would have gone to the press?
I don’t!
They would have quietly bundled the fix in with an update and labelled it as “bug fixes” the fact that they felt the need to release a press statement and Apple specifically lists a fix on the 13.3.1 update as “Fixes iPhone XR Signal issues on the O2 network” suggests to me this was a massive deal.
My original point was though don’t expect any of these bugs you are reporting to get fixed any time soon, as if they can allow a show stopper like this to not only get released to the general public but take nearly 6 months to fix it, don’t expect your mail bugs etc from 13.0 to get fixed anytime soon.
Hi Sal!
Yes it is. You may encounter a bug or 2, but your experience should generally be fine. And if you’re unlucky enough to encounter a more significant bug, you will be able to revert back. Just make sure to have an encrypted backup archived before installing the beta.
Has anybody else out there experienced issues with audio within Home Videos not playing, happens on both newly built iPad Pro 11 inch and iPhone 11 Pro Max, have tried removing them all and re-syncing still no fix
Have logged it with Apple again but have had to revert to VLC to play content
Other files such as music and Apple TV programs play fine, just happens with Home Videos
Have logged it with Apple again but have had to revert to VLC to play content
Other files such as music and Apple TV programs play fine, just happens with Home Videos
I think that's a Notifications problem in general and not specific to mail. It happens 50% of the time with Apple Reminders also. Most often when I mark something completed from the lock screen, the other location based reminders will vanish. Additionally, marking them completed on my watch (Series 2) often doesn't change the iPhone notification's existence.
Last edited: