Live data from Hacker News

iOS holding my phone number hostage = the worst bug I’ve ever experienced

blog.benjaminste.in

231–237 of 237 posts

Re: iOS holding my phone number hostage = the worst bug I’ve ever experienced

#231
post #228

Earlier quoted context omitted.

> One, this is not a question of competing brands. That's a question of technology and not liberty, which is the point of the comment you replied to; if OP choose free software, it doesn't matter which "brand" he chose, there are a number of free application that do the same job. I call BS. If OP choose free software we could AS WELL have had the same exact problem. It's a software bug -- the client caching the remot…

If it was an open protocol, he would have access to apps that implement it on his phone. And even if that weren't the case, he would have the ability to write an implementation. The difference here is that a sufficiently competent person cannot reliably replicate the experience.

The problem at this point is with the other friends and family who make use of this software. Great, he writes a new implementation of this protocol that prevents _his_ client from improperly caching routing information. This still doesn't fix the problem of the software on other peoples' phones.

Re: iOS holding my phone number hostage = the worst bug I’ve ever experienced

#232
I've had similar problems when switching between Android & iOS devices over the years with both T-Mobile and AT&T. It was a bit perplexing the first couple times it happened. Then I got used to the drill.

The solution, at least in my situation, was to call the carrier. Apple wasn't at fault.

Both T-Mobile and AT&T would fail to complete all steps required for the transfer, and therefore still showed the old device as the active one. A simple call resolved the issue.

In a couple instances, AT&T & T-Mobile would resolve the issue. Then I'd see the same behavior again weeks later. Sure enough, they had reverted to the old device on my profile. Calling them again resolved the issue.

Re: iOS holding my phone number hostage = the worst bug I’ve ever experienced

#235

Earlier quoted context omitted.

Apparently it doesn't have much priority on their list considering the problem has been around for two years. If you think about how fast the mobile landscape has changed, this is no excuse for Apple

2 years? 2 years is nothing. There are thousands upon thousands of open bug repots on Apple products older than 2 years.

Bugs are often sorted according to priority. It's clear that Apple doesn't care enough to prioritize this problem.

Re: iOS holding my phone number hostage = the worst bug I’ve ever experienced

#236
post #30

Just think, if you hadn't used a proprietary messaging solution as your default contact method, you'd be able to easily control how you receive the messages. Maybe stuff like this happening is a good thing as it drills home the point the 'crazy free software lunatics' have been going on about for some time. Having this kind of thing happen to someone makes the stuff FSF+co says a bit more relevant and ultimately help…

The whole problem is that no one tries to use iMessage, the texts just get automatically converted and sent over that system when you are both on apple devices. I was a huge apple fan when they were the underdog, but they are getting a little too big now. iO$ is still the best target operating system for developers, I just wish I didn't like apple's products so much.

Re: iOS holding my phone number hostage = the worst bug I’ve ever experienced

#237
post #75

What is the radar number for this bug? You did file a bug report, right? http://bugreport.apple.com If not... you should do so. If you give people the radar number they can duplicate it at that same site and raise its priority.

crickets...
Post reply on HN