Skip to content

AbstractProvider.getUserInfo throws an 'Unexpected end of JSON input' message in case of LinkedIn HTTP 429 error  #1297

Description

@sfodor

Version of FoalTS: 4.5.1

Not sure if it is bug, but the 'Unexpected end of JSON input' error message was a bit misleading for me when we had some issues with LinkedIn social API.

It seems reason is that the code first gets the json body before the response.ok is checked.
image

I'm wondering if having the http status in the TokenError would be a better solution.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions