111–120 of 237 posts
As a non-English speaker I can really relate to this. I think the real mistake was Apple allowing to enter a non-ASCII password in the first place. E.g. on macOS the password fields have been locked to English character set, and I'm not sure why it changed on iOS.
No that's obviously crazy!
I think the biggest lesson here is to back up. The reason for losing access to the phone is amazingly dumb but it could have fallen down the stairs for basically the same effect. And do your could backups cross-provider. You never know what the "big players" are going to pull, and your lifetime customer value is less than the cost of a single support call.
The biggest lesson here is don't buy Apple products. Steve Jobs would be rolling in his grave if he could see the software quality of the products that Apple releases today.
lol, nah he wouldn't. He would of upgraded his coffin to plush and got a big screen to watch the money roll in.
I recommend reading up on his 80/90's antics. All he cared about was money and that the world was crafted by him.
He was widely known for intense bullying, lacking empathy, and ruthless manipulation, combined with a "productive narcissism" that fueled his obsessive drive for perfection.
Majority of California based companies employee English only or English and Spanish speakers possibly with some Indian language as well. This leads to lots of problems when you are bilingual or bilingual in other languages such as German in French. Neither Apple nor Microsoft under this sort of language swapping well. Never mind rarer languages like Czech or Greek.
I'm a little impressed with Google. Recently the assistant started understanding when I speak Portuguese or when my wife switches to it in a text message. I hadn't had that experience before, the assistants would pick one language and mispronounce the other. Alexa has an experimental bilingual mode but it's nerfed by its general failure to understand well.
> Byrne was hoping that the next update, 26.4.1, would introduce a fix for this, but its release this week has not helped. Even if Apple restores the háček in a future update, wouldn't he still need to unlock the iPhone to install it?
You can always reboot to recovery and install an update that way.
Earlier quoted context omitted.
The biggest lesson here is don't buy Apple products. Steve Jobs would be rolling in his grave if he could see the software quality of the products that Apple releases today.
> Steve Jobs would be rolling in his grave if he could see the software quality of the products that Apple releases today. lol, nah he wouldn't. He would of upgraded his coffin to plush and got a big screen to watch the money roll in. I recommend reading up on his 80/90's antics. All he cared about was money and that the world was crafted by him. He was widely known for intense bullying, lacking empathy, and ruthless…
Earlier quoted context omitted.
Regardless, why should a Vietnamese person be forced to restrict their password to ASCII? If you want to sell your devices in a country, the least you can do is to adopt to the local market. I get that Western cultural dominance makes this hard for some, but I think it should be the bare minimum.
because it is common sense
I used to have an emoji password for my Android phone, and had the exact same issue after a reset! It's an odd but pretty terrible failure mode for locking oneself out...
You say locking oneself out, but I decline to consider any situation where a password can be set but not later entered as one where the user bears even a modicum of fault.
> During in-house testing, which involved taking an iPhone 16 from iOS 18.5 to iOS 26.4.1, The Register found that Apple has kept the háček in the Czech keyboard, but removed the ability to use it in a custom alphanumeric passcode. The OS will not allow users to input the háček as a character. The key's animation triggers, as does the keyboard's key-tap sound, but the character is not entered into the string. Sounds…
Seems like a front-end bug? So just access the API directly, or ask someone who knows how to do that? Plenty of iOS-focused reverse engineers out there.
How? The article states: > For the same reason, plugging in an external keyboard is also a no-go since freshly updated iPhones are placed in what's known as a Before First Unlock state, which prevents wired accessories from working until the passcode is entered. The user can't even enter their passcode, how do you expect them to perform code execution?