One more iPhone bug
Posted on Fri 1 Feb 2008 at 8:16 am PST. Filed under Mobility.
The inevitability of using a complex operating system in your embedded product: more bugs. I’ve found 2-3 bugs so far in this Apple platform, but this one is a funnier one. At around 7:50 AM PST today Yahoo!’s stock was up about 45%, but the iPhone/iPod Touch (including in the latest firmware) show that it’s up 90%.

![]()




8 Comments »
What makes you think that’s a bug and not just bad data? You like to throw around the term “bug,” but if it’s just fetching XML and the XML includes inaccurate info, that doesn’t make it an “iPhone bug.”
Well, I have no way to know if it’s bad XML data, all I know is that the information on the iPhone screen is faulty. That’s all it matters in the end in fact. That’s the life of a consumer product for you.
See the irony that a Yahoo/Microsoft-powered widget running on an apple product is not working?
BTW, Adam, don’t forget that the stock value is correct, only the percentage is wrong. So it’s not clear at all if this is a Y! XML bug.
Hi. Same “bug” on the Dashboard stocks widget.
This is why I stay away from Apple products, i-phone, i-raq
it wouldn’t surprise me if they are behind that as well, the coincidence is too striking
This will be a bg in the financial feed data. Either the data is being displayed verbatim,, or the diff data was incorrect. If it was truely such a fundamental bug in the widget, a lot more stock would be incorrect on a frequent basis. Ergo, this is not a bug in the iphone.
Never heard of EYE-raq, where is that? Is it near ee-raq (Iraq)?
Another bug with safari is when logging into devices that ask for a username/password, if the device doesnt have a user or pass, safari wont let you proceed.
Comments are closed as this blog post is now archived.
Lines, paragraphs break automatically. HTML allowed:
<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <code> <em> <i> <strike> <strong>The URI to TrackBack this blog entry is this. And here is the RSS 2.0 for comments on this post.