Hi Erin.

Coding around it is actually the correct solution; there's no telling
when a user's account will become suspended or hidden, so your app
needs to be able to deal with it when it happens. You will get an
error code in the response (along with an HTTP 401, I think), so you
can use that as the trigger. If you want to find out whether a user's
account is still active, ask for their current location. If you get
it, it's active.

seth

On Fri, Dec 26, 2008 at 5:22 PM, Erin Sparling <everyplace@...> wrote:
> Hi!
>
> So, one of the users in our db has a banned account, and it's throwing all
> sorts of errors in the app. I've coded around it now, so that the scripts
> don't die when encountering a banned user, but is there a recommended call
> to determine first if a user's account is valid with fireeagle, before
> trying to do things with it?
>
> -erin
>
>