Closed ivanistheone closed 7 years ago
I can still reproduce; pinging @sursh, @punchagan who I assume have access to the Heroku application
Thanks for filing the issue. I was on a holiday, and unable to look into this further. I will look into what's going on, soon.
@davidbalbert @zachallaun Have there been any API changes for RC?
https://www.recurse.com/api/v1/people/me?access_token=$token
seems to be giving an error.
Thanks for the reports and sorry about this all. We deployed some API updates late last week, which I assume are the culprit. Dave and Zach will investigate as soon as they're in this morning.
This is now fixed! Sorry for the trouble. We made some changes late last week to the way authentication and permissions work with our API (in anticipation of some new ways to access the API), and in doing so accidentally forbade Recursers from doing certain actions that should be allowed.
Thanks for fixing this @zachallaun!
When I go to https://blaggregator.recurse.com/ and I start the OAuth flow, I get sent back to https://blaggregator.recurse.com/complete/hackerschool/?code=613.......&state=J2T..... with the following generic Heroku error displayed in the page:
Please check the logs between 1:45am EDT and 1:57EDT on May 10th.