-
Notifications
You must be signed in to change notification settings - Fork 298
Creating new version failed: Application error #572
Comments
I went ahead and skipped 1.2.0 and went straight to 2.0.0 since it makes a decent amount of sense anyways, and publishing was successful for 2.0.0. It was only 1.2.0 that refused to publish. |
I'm also running into this issue. I updated language-rdf to v0.4.0 and cannot publish this version:
After that
What can I do? Is there any option to get verbose logging output? |
Any updates on this issue? I'm still unable to publish my updated package. |
I solved it by skipping version v0.4.0 and publishing v0.5.0. |
This appears to still be broken. |
|
Seeing the same. (yes, did login first). Don't think this is just one error, seems to be a catch-all error message for a variety of conditions. |
Error remains. However I could verify that the package was updated (though not every publish action did result in an update). ...and, assuming this did work as I did not question what the pkg manager web UI is saying). Simultaneously package search Web UI returns 5⚛︎0 so, maybe something there? I'll go fish for the apm source if anybody would gallantly point me at it thank you aplenty. |
I have this problem right now |
As do I 🙁 Have tried minor, patch and major as well as specific tag. I also can not unpublish versions properly - I get the same error then. |
I haven’t tried degrading apm yet |
I also tried to run the commands over the API, but I get the same, unhelpful. error back then. I'm starting to wonder if something with the expected package structure has changed. Mine is an old package that I'm updating for the first time in years - so maybe something is supposed to be different now. |
@sadick254 could you - or someone else from the team - shed some light on this please? |
This issue is a blocker for a doc team that needs to upgrade to a package with a bug fix in it: errata-ai/vale-atom#8 |
I'm having the same issue. Using the latest apm running |
Hi. I am not sure, but I think I stumbled across a workaround. it goes like
in other words, 2 steps forward, 1 step back. |
@miyako Thank you for the info, but for some reason this doesn't work for me. I tried pushing to minor updates, received the application error on both, ignored. used
|
Right now I'm completely locked and my package is unusable by anyone. Because the publish failed, it left it in a state that makes it look like there's an update, but it can't be installed. |
in this context you need to remove the "v" the command should be apm unpublish language-mads-6502-asm@0.17.0 |
I'm also having this issue. Replicated on Mac, Windows, and WSL. |
Confirmed here also that @miyako workaround works. (Publish new version, unpublish the old version) |
Hello everyone, trying to publish from |
Can't say the workaround does anything for me. |
Basically, the Atom packages API server has been somewhat unreliable lately, and it has been intermittently returning So, the workaround is to try again a couple of times, hope you don't get a That's what @miyako already said, but I hope this explains why it works and explains what is going on. This is my best understanding of the situation, since there hasn't been an official explanation of the situation given yet, that I've seen. |
I'm currently receiving this error message when attempting to publish the latest update for my package, language-papyrus:
I have used
apm login
to authorise multiple times to ensure I pasted the API key in correctly, but no dice.The text was updated successfully, but these errors were encountered: