Skip to content
This repository has been archived by the owner on Dec 15, 2022. It is now read-only.

Cannot publish package - authentication problem #949

Open
asiloisad opened this issue May 6, 2022 · 4 comments
Open

Cannot publish package - authentication problem #949

asiloisad opened this issue May 6, 2022 · 4 comments

Comments

@asiloisad
Copy link

hi,

I am the author of the package pdf-viewer. About two weeks after the apm publish patch command I got the information Creating new version failed: Requires authentication. Please update your token if you haven't done so recently. To fix the problem I went to https://github.com/settings/applications and revoked all permissions for Atom, then logged back into https://atom.io/account again granting permissions, then with the apm login command I entered a new token into apm console. I repeated this action many times, unfortunately it did not solve my problem. Do you have any idea how I can solve this?

console output for apm publish patch::

Preparing and tagging a new version done
Pushing v0.1.17 tag done
Publishing [email protected] failed
Creating new version failed: Requires authentication. Please update your token if you haven't done so recently.

the result of apm publish patch is the new package version is updated in github, it can be install by apm install bacadra/atom-pdf-viewer, but is isn't available in atom package store.

@asiloisad
Copy link
Author

has any one similar problem now?

@marat-gainullin
Copy link

Hi.
I have the similar problem. The command apm publish patch gives me the following:

Preparing and tagging a new version done
Pushing v0.2.4 tag done
Publishing [email protected] failed
Creating new version failed: Application error

I did that authentication/token stuff according to the docs, but with no luck.
Such error is mensioned in early bug reports in 2015. It seems, that it is back now.

@alpyre
Copy link

alpyre commented May 24, 2022

Same here. I cannot publish the latest state of my package with the exact same error:
Creating new version failed: Requires authentication. Please update your token if you haven't done so recently

I've tried generating a new token and re-entering my credentials to git but the problem persists.

@asiloisad
Copy link
Author

asiloisad commented May 24, 2022

the same as @alpyre. 3 weeks has passed, but the problem is unresolved.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants