m.fuelly.com crashing Mobile Safari on fuel-up

[reefdog]

On Mobile Safari, when trying to add a fuel-up (m.fuelly.com), clicking "Next" after selecting a car from the drop-down promptly crashes Safari. If I click "Done" and then manually select the Odometer field, all is well (although the Odometer field resizes itself weirdly), but "Next" consistently and repeatedly crashes Safari.

I have two saved cars, only one of which has a fuel-up so far. I'm on a stock iPhone EDGE (no jailbreak/etc.) running iPhone OS 2.0.1.

Anyone else experience this?

[pb]

Yes, I can confirm this, happens on my iPhone too. What's odd is that if you click "Done" instead of next after selecting your car, there's no crash. (Like you mentioned.) So you could do that until we figure out the problem.

[reefdog]

Thanks pb! Yeah, for now I'm using Done.

[Billie]

on my iPhone, if I try either m.fuelly.com or the normal site... I cannot get anything to load.

It works FINE if I am on WiFi... but when I'm operating with EDGE (on my t-mobile service plan) I get:

HTTP ERROR: $CODE$

$MESSAGE$

RequestURI=/

[pb]

What phone are you using, Billie? Sounds like it's not an iPhone. And have you tried the Google proxy? That might be a better way to access the site depending on the type of phone you have.

[Billie]

I have the original iPhone, not the 3G... running the 2.0.1 firmware (the most recent) and on T-mobile's unlimited Data plan using Edge. It is jailbroken and unlocked, but this wouldn't affect the site. And every other website loads just fine, mobile version or not (USAA.com, engadget, gizmodo, google, every site I can think of)

Whenever I am on WiFi, both sites work fine. But on Edge I get that same weird HTTP error

[Billie]

The directions in the Google Proxy you gave work... but it is not near as pretty or as optimized for the screen as the m.fuelly site is (which I can use on wifi)

[Billie]

As a test, the girlfriends iPhone on the AT&T Edge network connects to the site just fine...

[pb]

This sounds like a T-Mobile issue to me. If you try a search for T-Mobile "HTTP ERROR: $CODE$" you'll find quite a few people talking about it. Doesn't look like there's anything we can do about it on our end. There are some proposed solutions on the phone side here.

[Billie]

Hrm... i guess it does look like a T-mobile issue... but all those people appear to be complaining about T-zones... and i'm not on the T-zones plan... very weird... I guess I will just use the Google Proxy for now.