Jeffery, This is valid criticism. This bug came as a surprise to us as well. We otherwise would have given developers fair warning. Unfortunately there is no easy fix, and like a bad heart-break, time may be the only answer.
In short, the problem is with the user data cache. To get the extended information into that cache, the user object must either expire or be invalidated through some user initiated update. The expiry on the cache is rather long and you will find that inactive accounts will have abbreviated data for up to 2 weeks. This is obviously sub-optimal, as Matt would say. Doug Williams Twitter API Support http://twitter.com/dougw On Thu, Apr 2, 2009 at 12:27 PM, Jeffrey Greenberg < jeffreygreenb...@gmail.com> wrote: > > Doug, > Grumble: just to say it, this wasn't handled well at all. The fact > that this field disappears whether due to caching or through a coding > error has the same result of completely breaking my app. > > How long will it take for this issue to clear up? Days? How many > exactly? and after X days will further requests be populated > correctly? > > thx, > jeffrey > http://www.tweettronics.com >
