It seems that @Anywhere stops processing before reaching the
initialization callback if a user revokes an application's access
through while still "signed into" a connected site.

During initialization, the call to verify_credentials fails with 401
Unauthorized (as expected), but the process does not then go on to
indicate to the browser that the operation failed. Instead, the script
apparently halts without going to the initialization callback and
without unsetting the user's existing twttr_anywhere cookie.

To unsubscribe, reply using "remove me" as the subject.

Reply via email to