Closed
Description
New Issue Checklist
- I am not disclosing a vulnerability.
- I am not just asking a question.
- I have searched through existing issues.
- I can reproduce the issue with the latest version of Parse Server.
Issue Description
Currently, the OAuth test fails due to an issue with the Twitter API endpoint that is used for testing a failed OAuth response.
The response is an incorrectly formatted JSON string, so parsing fails.
This happened at least once some time ago, so the endpoint to test against has been changed. If this keeps happening with the Twitter API, we may change to an OAuth API endpoint of another provider for testing.
Steps to reproduce
Run test
GET https://api.twitter.com/1.1/account/settings.json
Actual Outcome
{"errors":"{\"message\":\"Could not authenticate you\",\"code\":32}"}
Expected Outcome
{
"errors": [
{
"code": 32,
"message": "Could not authenticate you."
}
]
}
Failing Test Case / Pull Request
- 🤩 I submitted a PR with a fix and a test case.
- 🧐 I submitted a PR with a failing test case.
Environment
Server
- Parse Server version:
master1594afe - Operating system:
n/a - Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc):
n/a
Database
- System (MongoDB or Postgres):
n/a - Database version:
n/a - Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc):
n/a
Client
- SDK (iOS, Android, JavaScript, PHP, Unity, etc):
n/a - SDK version:
n/a
Logs
(none)