Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Bugs Apple loves

bugsappleloves.com

Post reply on HN
Print view View original

151–160 of 550 posts

Re: Bugs Apple loves

#151

Post by ulbu »

BitsAndObjects wrote: post #33

Trying to type this comment on an iPhone and that very last issue, text selection, is so so real. It’s probably the single biggest thing I hate about this phone that makes me consider switching back to Android (I was on Android for 12 years before trying out an iPhone for 3 years atm, and in general, on average, I can’t tell the difference… they both have strengths and flaws. Text selection is a pretty massive flaw o…

you can enable cursor control by holding space, and then you can move to selection mode by touching anywhere else on the keyboard.

Re: Bugs Apple loves

#152

Post by ulbu »

nicwolff wrote: post #137
BitsAndObjects wrote: post #33

Trying to type this comment on an iPhone and that very last issue, text selection, is so so real. It’s probably the single biggest thing I hate about this phone that makes me consider switching back to Android (I was on Android for 12 years before trying out an iPhone for 3 years atm, and in general, on average, I can’t tell the difference… they both have strengths and flaws. Text selection is a pretty massive flaw o…

And they had it solved! 3D Touch worked perfectly – you pushed the screen hard to get a cursor, moved it to the start of the selection, and pushed hard again to drag to the end. They killed it because "not all iPhones had the hardware to support it" or something.

you can still make selections using the keyboard without 3d touch.

Re: Bugs Apple loves

#154

Post by simojo »

Had a similar thought today while marking up pdfs with my iPad. Half of the time I'm fighting with Files' ability to persist my changes after it frequently crashes. Why market it as an iPad if marking up pdfs is so scuffed? this has been happening for years, it's like Apple's desire to add new features tops the desire to fix long lived bugs.

Re: Bugs Apple loves

#155

Post by nneonneo »

I have a fun one: my iPhone (12 Pro) refuses to acknowledge that it has eSIM functionality, even though the hardware exists.

I'm fairly sure I know what the problem is! It was restored from a backup taken on an iPhone X that had two physical SIM slots (Chinese version). The new phone now seems to think it has two physical SIM slots: it shows an IMEI2 in About, but any attempt to use the eSIM functionality just fails (scanning a code does "nothing"; no "add" button is visible, etc.).

If this was an Android phone, I'd root it and just fix the offending network configuration file. I believe it's possible to tamper with a backup of the phone to fix the issue, but this would mean a full backup+restore cycle and some specialized tooling to go mucking with the backup.

I filed a Radar on it ages ago, but I'm assuming nobody ever picked it up.

Re: Bugs Apple loves

#156

Post by einr »

aisuxmorethanhn wrote: post #65

A bug that’s persisted for 10 years at least is in the Music app. When you lose Wi-Fi the app will skip to the next song over and over and eventually freeze up.

On iOS, it’s not just Wifi but cellular too. I tried switching from Spotify (got tired of their constantly deteriorating UI/UX) but this was a dealbreaker. You can’t listen to albums in the car because if the phone loses coverage at the wrong time it just… skips songs? HOW does this get through testing and persist for so long?

So I cancelled Apple Music and reluctantly went back to Spotify. At least in Spotify, music playback is functional.

Re: Bugs Apple loves

#157

Post by ycombinator_acc »

ulbu wrote: post #151
BitsAndObjects wrote: post #33

Trying to type this comment on an iPhone and that very last issue, text selection, is so so real. It’s probably the single biggest thing I hate about this phone that makes me consider switching back to Android (I was on Android for 12 years before trying out an iPhone for 3 years atm, and in general, on average, I can’t tell the difference… they both have strengths and flaws. Text selection is a pretty massive flaw o…

you can enable cursor control by holding space, and then you can move to selection mode by touching anywhere else on the keyboard.

You have to be very precise with your finger drags because it loves snapping back to the original position. Gbroard doesn’t suffer from this. Part of the reason is it doesn’t do the “free-floating” cursor thing - which I’ve never understood the point of anyway. It’s fancy but useless in 99% of cases on a phone.

Re: Bugs Apple loves

#158

Post by hamstergene »

appplication wrote: post #101

This is missing the most annoying one for me: when I type a search term into safari and it randomly interprets it as an address that it can’t resolve. E.g. “how to bake cookies” gets resolved to how%20to%20bake%20cookies (which safari tries to resolve via DNS or whatever instead of piping it to the search provider). Even better, it’s entirely nondeterministic, though it does seem to be due to some race condition with…

I personally reported that around time when Mac OS X 10.9 (first non-cat) came out and immediately saw it marked as duplicate. So at least 13 years and counting.

Re: Bugs Apple loves

#159

Post by panny »

Tim Cook is "stepping down" soon. Do you think his replacement will fix these things? I stopped using Apple stuff shortly after Steve Jobs died. Linus is still alive, but I wonder where I'll move once he is gone.

Re: Bugs Apple loves

#160

Post by cyode »

I’ve encountered several of these, but (at least on iOS 26.2), I can’t reproduce the typo one.

> Autocorrect Won't Take No For An Answer. You fixed it. It unfixed it. You fixed it again. It unfixed it again.

My experience is after the system makes the first autocorrection, the word is underlined, allowing me to revert to the original spelling. Then subsequent instances of the word aren't autocorrected.

It’s true though that if I leave the context and enter the same unrecognized term elsewhere, it’s the same grind. The only fix for this is to spotlight search for “Text Replacement” settings page to essentially add it to the iPhone’s dictionary. Clunky, but personally only have had to do this twice.

Post reply on HN