-
Notifications
You must be signed in to change notification settings - Fork 9
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
[v4] Upload failed: {"detail":"Invalid token."} #267
Comments
|
I'm seeing the same thing in jonhoo/faktory-rs#52 when using: - name: Upload to codecov.io
uses: codecov/codecov-action@v4
with:
fail_ci_if_error: true
token: ${{ secrets.CODECOV_TOKEN }}
env_vars: OS,RUST Although my job does fail (since I set |
Ah, I think I may have figured out what's wrong, though still confirming. On the codecov.io page, make sure you select the right branch in the "branch context" drop-down near the top. Mine was set to |
Yep, that did the trick! Not sure why the wrong branch was selected originally, nor why the token for |
OK. Update, changed the action to what you suggested; but what i think did the trick was going to codecov.io > {my project} > settings > and using the token in the page. I stupidly was using the Profile > api token. Thank you for the support! |
@rohan-at-sentry, something seems strange here, the token shouldn't have changed. Can you take a look into this? |
So the code that worked for my dev branch is now failing on master. nothing changed (just got merged). https://github.com/kingbuzzman/django-squash/actions/runs/7865828819/job/21459307944#step:7:36 any ideas? -- im contemplating just going back to v3 |
@kingbuzzman I see from your your tests.yml that you've set the codecov token in the yaml. Can you confirm that you've obtained a token correctly? Use this to help. Pl. note, a lot of people do trip up on is copying the |
Yeah that looks correct. Let me dig in more here. I do notice similar errors all the way back from last week https://github.com/kingbuzzman/django-squash/actions/runs/7777959713/job/21206973008#step:7:35 (for example), although that could be related to when you initially opened this issue |
@kingbuzzman I think this is happening because the |
Yup, thats was it. Thank you!! |
closing. |
Migrating to v4 and getting this error on this PR.
under "Upload coverage to Codecov"
I ensured that
secrets.CODECOV_TOKEN
is correct. viaecho "${{ secrets.CODECOV_TOKEN }}" | wc -c
-- got 37 characters, looks good.Funny thing is, it does NOT fail... It should, but doesn't. Im so confused, some guidance would be much appreciated.
The text was updated successfully, but these errors were encountered: