Sick of updates? Grab a non-Pixel Android phone and you won't have to worry about getting updates.
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 11.2.6 With Fix for Telugu Character Bug That Causes iOS Devices to Crash
- Thread starter MacRumors
- Start date
- Sort by reaction score
Let me guess, you aren't a software engineer and know nothing about coding?
Yep, if you’re tired of getting so many updates from Apple the it’s time to switch platforms. You won’t have to worry about updates, EVER!
Go take Computer Science 101 at your local community college and you will understand.
so much b@tching on this thread; its ridiculous
A jackass sent it to me on Friday and bricked my whole iMessage. It was incredibly annoying.
According to the article, it does _not_ crash the entire system. It crashes apps trying to display the text. So much less exciting than you are saying. And how long has it taken hundreds of millions of users, including at least 100,000 who actually can read and write Telugu, to find this?
**** happens. Some bugs are impossible to find during testing, because they only happen when several completely unrelated things happen at the exact same time.
And an app crash is by far not the most serious thing. Silently changing things, that's serious. Sending messages intended for your girlfriend to your wife instead. Paying $18000 instead of $180.00. That's serious. A crash isn't.
Last edited:
A lot of people appreciate getting timely updates that address bugs and security issues. The bandwidth thing, I can see being an issue if you have a tight quota but otherwise this just feels like griping to gripe.
Some days I think "Wow, that's the most absurd thing to whine about, ever". Then someone else posts something crazier a few posts later. You've really raised the bar though, well done.
Do you need Apple to send out a team to your place of work and do the update for you too? I think it's probably worth you closing the browser and spending some quality time with your emotional support hamster and unwinding for a while.
Last edited:
Android doesn't have these silly bugs and have less frequent updates.
iOS has more of these silly recurring messages, alarm, time zone, etc. bugs but have more frequent updates.
It boils down to if you don't mind living with the DoS for a week whenever the Indian characters appear on the internet wild west and enduring the down time of having to update and reboot iOS again.
Sure it does. A cursory Google search will yield enough results to keep you reading for a few days. As far as less frequent updates go, that's because the Android update process is a train wreck, unless you have a Pixel.
I cannot confirm this on my iPhone 6. All is well. You do know that the auto-brightness toggle was moved to a new location in iOS 11. it is now located at Settings->General->Accessibility->Display Accommodations. Try looking there.
11.2.6 fixes an 'iPod 02-60 Error" error I was getting on my Pioneer 4000NEX Carplay unit. This error started with iOS 11.2.5.
No still there, general->accessibility->display options
Who cares about bug fixes anyway...
As long as we get more Emojis and watchbands, we're all happy.
If we don't get lots more animojis, I'm only going to buy 6 of the 2018 iPhone X's.
Apple needs to release fixes for previous versions of iOS, MacOS, etc that are affected by this.
There are a lot of devices that can't be updated to the newer OS's.
There are a lot of people who for one reason or another don't want the new OS's.
There are a lot of legacy applications that can't be run on the new OS's so people need to keep some devices back on older OS's.
Apple should put a lot more focus on legacy support. It is fairly trivial and well within their budget. Older devices get passed onto those who can't afford the newer devices. This makes for people buying into Apple's garden rather than buying cheaper PCs and Android devices. In the long run, that is very good for Apple.
There are a lot of devices that can't be updated to the newer OS's.
There are a lot of people who for one reason or another don't want the new OS's.
There are a lot of legacy applications that can't be run on the new OS's so people need to keep some devices back on older OS's.
Apple should put a lot more focus on legacy support. It is fairly trivial and well within their budget. Older devices get passed onto those who can't afford the newer devices. This makes for people buying into Apple's garden rather than buying cheaper PCs and Android devices. In the long run, that is very good for Apple.
Apple developed software has always been really bad about handling errors. Just look at iTunes, when you load a cd into iTunes it, by default did/does no error checking. So guess what? Your out on your bike ride and bam, a bunch of static or skipped song. Now with iTunes you can turn on error checking, but in general Apple software fails to handle or even check for a lot of errors. This occurs at all levels.
Couple that with Apple converting all iOS and macOS functionality into daemons and you have the perfect storm. Apple is terrible about API design and with daemons you have no way to notify the user of a problem, because the daemon is not running in user space. The API has to have problem reporting built in. So the daemon just ignores the error. Why? Because Apple is confused and thinks that "it just works", means that in every little crevice they can just ignore errors. This is a rot that has been growing in Apple software for years and it is not going to be solved in a few months of focusing on bug fixes. API design problems are not bugs, they are fundamental design problems. For the most part, I believe that everything that Apple has converted to a daemon has these problems.
I don't think this is a daemon issue. Linux uses daemon all the time and Android doesn't seem to have the Telugu issue.
Literally the first time I've heard this applied so broadly and having worked with it as a iOS dev and nosing around the OS, disageee wholeheartedly. Their APIs are pretty phenomenal as far as design: now whether they work as intended is another question (coughsirikitcough).
Daemons do have the ability to bubble to the user space on iOS. But this particular problem is not rooted in a daemon: every app has its own instance of Core Text that's independent from another, which is why this only crashes apps and not causing resprings this time.
Not saying they're perfect; if we are talking Apple's messaging daemon, for example, that is some crazy bull that grew out of control and has been the root of some high profile exploits (HomeKit and false SMS exploits!).
But the overall the system design is very well done, at least in my opinion.
Last edited:
Gna is the character = Words constructed using this character - Gnanam(Knowledge) , Agnanam (Ignorance), Gnapakam (Memory), Gnani (knowledgable)
This bug can cause a BOOT LOOP rendering the phone UNUSABLE. It is possible for Springboard to crash. As far as I'm concerned, if it is possible for the phone to become unusable, that is pretty serious, but less serious than an exploding battery.
The solution to your problem of sending messages intended for your girlfriend to your wife is to stop cheating on your wife. This is not a programming issue, this is a social issue.
My senior called today and asked me to update to see if the iPhone suddenly synced with iCloud.
Of course not.
A bug that's been going on since day 1 of iOS 11 and still no fix.
Endless of almost useless communication with
Must give this senior credit though, it's not his fault that the software engineer don't know what they are doing at today. I've given up though, use a combo of google and my nas calendar to have a functioning syncing calendar across devices. It works.
Of course not.
A bug that's been going on since day 1 of iOS 11 and still no fix.
Endless of almost useless communication with
Must give this senior credit though, it's not his fault that the software engineer don't know what they are doing at today. I've given up though, use a combo of google and my nas calendar to have a functioning syncing calendar across devices. It works.
Well I have been doing iOS software since the first iPhone and macOS software since before that and there are literally hundreds of things that don't work according to Apple's APIs. I quit filing Apple bug reports because I was spending more time creating bug reports than coding. At one point I had over 25 bug reports that were open and were over a year old, with the oldest maybe 5 years old. I have hundreds that were closed, marked duplicate, but never fixed.
Try figuring out all errors can be thrown in a swift 'try' block. It is nearly impossible. If I can't figure it out, then I am sure the entry level Apple programmers have no clue either. So what do we do, we log the error then give up instead of handling it.
Now I might agree regarding Apple's programming APIs not being the worst around, but Apple's OS level programming has been getting worse and worse the more they moved to daemons. Older more stable OSs had fewer daemons and were more reliable. While I would love to be wrong, I can not think of any other excuse other than Apple is just lazy and hires poor programmers. Which I do not think. With the poor quality of the original iCloud, current Siri, current messages, iTunes, etc., it seem to me that Apple is not vary good at designing network services (and that includes daemons).
Your right though, I have no knowledge that this text bug is daemon related, but it would not surprise me.