Bugzilla

I noticed this today as well. Firefox has a cached OAuth token that has expired, but the version of Monitor that is currently in production rejects it with a `404` error rather than a `400` or `401`, so the client never ends up learning that the token is invalid. Signing out and Sync and signing back in causes it to start working again.

I expect things will all start working correctly as soon as https://github.com/mozilla/blurts-server/pull/1138 hits the production servers.  :groovecoder, do we have an ETA on such deployment?

If necessary, we could work around this on the client side in the meantime by special-casing the "Cannot find FXA for that OAuth token" error message and treating it like a `401`. (In fact :mtigley's original patch did this, but I advised against it for future-proofing reasons; I wouldn't be opposed to it for backwards-compatibility reasons though...).

I noticed this today as well. Firefox has a cached OAuth token that has expired, but the version of Monitor that is currently in production rejects it with a `404` error rather than a `400` or `401`, so the client never ends up learning that the token is invalid. Signing out of Sync and signing back in causes it to start working again.

I expect things will all start working correctly as soon as https://github.com/mozilla/blurts-server/pull/1138 hits the production servers.  :groovecoder, do we have an ETA on such deployment?

If necessary, we could work around this on the client side in the meantime by special-casing the "Cannot find FXA for that OAuth token" error message and treating it like a `401`. (In fact :mtigley's original patch did this, but I advised against it for future-proofing reasons; I wouldn't be opposed to it for backwards-compatibility reasons though...).

I noticed this today as well. Firefox has a cached OAuth token that has expired, but the version of Monitor that is currently in production rejects it with a `404` error rather than a `400` or `401`, so the client never ends up learning that the token is invalid. Signing out of Sync and signing back in causes it to start working again.

I expect things will all start working correctly as soon as https://github.com/mozilla/blurts-server/pull/1138 hits the production servers, with no user action required. :groovecoder, do we have an ETA on such deployment?

If necessary, we could work around this on the client side in the meantime by special-casing the "Cannot find FXA for that OAuth token" error message and treating it like a `401`. (In fact :mtigley's original patch did this, but I advised against it for future-proofing reasons; I wouldn't be opposed to it for backwards-compatibility reasons though...).