-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
403 (forbidden) response #598
Comments
Is it possible it's failing because the message is strictly a url? I know this used to work, but it's been a while since I've used it. Edit: It's not because it's a URL. https://github.com/LizardByte/.github/actions/runs/10104499754/job/27943571270#step:2:3 |
I found the issue by using noweh/[email protected]
My app was not "assigned" to any "project". |
@ReenigneArcher I'm not sure if there's anything to be done here, as we're not currently using this action there may be a change in the twitter API that we may have missed. Can you help me understand what that may be? |
The issue was simply that my app in twitter was not associated to my project in twitter. I think logging the response when there's an error could be helpful like the other action does. This helped me immediately identify the issue. |
Understood, thanks for clairfying 👌 |
I get a 403 response when trying to use this action.
I have regenerated all keys, tokens, etc and the result is the same. I am not hitting any API rate limits as I almost never used the API, and haven't used it in the past several months. Any ideas?
The text was updated successfully, but these errors were encountered: