Inconsistent HTTP errors for expired auth token?

[isaacd8k]

When making API requests using the FB client and an expired auth token, different REST endpoints return different error messages. For example:

List Projects

When calling client.projects.list(), we get a nicely formatted http 401 error as described in the docs like so:

{
name: "List Projects",
message: "UNAUTHORIZED",
code: "401"
}

Get Identity

In the exact same scenario, when calling client.users.me(), we receive an error as follows:

{
name: "Get Identity",
message: "This action requires authentication to continue",
code: "unauthenticated"
}

Is this a different error and by design? I notice "unauthenticated" rather than "unauthorized".

We were expecting a response as in the first example, i.e. an HTTP status code in the code field, but if this is by design perhaps we can add the "unauthenticated" code check to our HTTP handlers.

See MRE here

[amcintosh]

Hi.
The SDK error handling is not particularly consistent across different domains (auth, accounting, projects, etc.).
We are planning to address this in the next little bit, but for now the differing error responses is expected.

[isaacd8k]

Ok thanks for the heads up 👍🏼