Wow, thanks Seth of the FE team. :) You guys really do respond quick.
Alright then, I could live with the temporary clunky-ness in my code knowing that there's a fix on the way.
Cheers!
Alright then, I could live with the temporary clunky-ness in my code knowing that there's a fix on the way.
Cheers!
On Fri, Sep 26, 2008 at 9:57 AM, Seth Fitzsimmons <seth@...> wrote:
(Not obvious from the email address, but I'm on the FE team and am
usually the one to answer technical questions on the list.)
So far the forum has worked pretty well for reporting problems. I
usually point our internal bug tracker at individual posts on the
mailing list along with some context.
Bouncing to the US and back would work. Not ideal, and really quite
clunky, but effective until I can get the bug fixed on our end. I'll
post back to the list once I get it fixed so you can de-kludge your
code.
seth
On Thu, Sep 25, 2008 at 6:48 PM, Romeo Olympia <romeo.olympia@...> wrote:
> Thanks, Seth for confirming the bug as well. I'm new here so can you please
> tell me if there's a bug reporting mechanism in place. Or is it just this
> forum for now hoping that some of the good guys in Yahoo!'s FE team would
> see this post?
>
> I could probably work around this by doing one extra update API call just to
> reset the location to somewhere in the US. And then do the actual update
> with my real location (in HK) after. But that just seems too clunky to me.
>
> Thanks!
>
> On Fri, Sep 26, 2008 at 4:38 AM, Seth Fitzsimmons <seth@...> wrote:
>>
>> Hi Romeo.
>>
>> This is the first I've seen of that bug, but it's definitely a bug.
>> Thanks for the steps to reproduce!
>>
>> It will be a problem any time you move within an area with poor
>> geographic coverage (provided you stay within the same
>> smallest-place-we-know-of).
>>
>> seth
>>
>> On Wed, Sep 24, 2008 at 5:26 AM, junjun572 <romeo.olympia@...>
>> wrote:
>> > Hello,
>> >
>> > I have an updater client that uses lon/lat value pairs to update its
>> > location in Fire Eagle. I'm seeing problems when updating for places in
>> > Hong
>> > Kong (and maybe other places outside the US?). This is reproducible
>> > using
>> > the following sequence of steps:
>> >
>> > (1) Terrace Dr, New York
>> > lat=40.773357
>> > lon=-73.971977
>> > Result of Update in Fire Eagle: OK
>> >
>> > (2) 34th Street, New York
>> > lat=40.751774
>> > lon=-73.992233
>> > Result of Update in Fire Eagle: OK
>> > ** This works properly in the US as expected. I could keep on supplying
>> > lon/lat pairs and the updates go smoothly.
>> >
>> > (3) Mongkok, Hong Kong
>> > lat=22.321093
>> > lon=114.180565
>> > Result of Update in Fire Eagle: OK, but place description just shows
>> > general/wide area without street or district info.
>> > ** The first time the location is set to HK from some other country
>> > (such as
>> > US in step 2), it works. The map shows the correct place.
>> >
>> > (4) Central, Hong Kong (different district from Step 3)
>> > lat=22.281848
>> > lon=114.161167
>> > Result of Update in Fire Eagle: Failed. "My Location" in Fire Eagle map
>> > still shows the one from step 3. Place description is still the same
>> > general
>> > area as step 3. Timestamp updated though.
>> > ** This is the subsequent update within HK. It will keep on failing
>> > until
>> > you set it to the US again. Practically, you're only allowed one update
>> > in
>> > HK then. :(
>> >
>> > I've gone thru some of the threads in this forum but can't find much.
>> > Has
>> > this problem been reported before? If so, would greatly appreciate it if
>> > you
>> > could give me a link.
>> >
>> > Thanks in advance!
>> >
>> > Romeo
>> >
>> >
>> >
>
>