Since the new layout of the website we have issues signing our extensions.
Files we we’re able to sign previously without any issues, now wont pass anymore.
We don’t get much more information from the site than :
It was not possible to sign the extension, please try again.
Any insights anyone?
When I try to sign my extension, the website open a modale asking to click on “download package”. but nothing append . running the process several time I catch the javascript log error
VM151:1 Uncaught (in promise) SyntaxError: “undefined” is not valid JSON
at JSON.parse ()
at h (group-home.4679bd01.js:228:9688)
at group-home.4679bd01.js:228:9380
at Array.filter ()
at u (group-home.4679bd01.js:228:9326)
I get the same JS error, the moment i load the signing page
Same, issues here. Version’s that previously got signed without any issue, also won’t get signed anymore…
Haven’t got anything to work so far.
the extension warehouse got a facelift to look like the 3dw last week, on the 26-27
maybe it broke a link / file somewhere ?
Thank you for highlighting this. I will make sure that the relevant team are aware.
Thank you!
Any timeline on this issue?
I’m afraid I don’t have one just yet. I can assure you this was raised with the relevant engineering team though. I will chase this again for you today to see if I can get any form of update.
Thanks a lot for getting back to me. It’s just a very unfortunate time to have issues now, since we are in the middle of an update sequence 
Unfortunately…Still nothing. Same errors, no feedback.
I tried without encryption, that gives a little more detailed error, stating that some Folder isn’t empty.
A status update or some help when the mistake is on our side, would be greatly appreciated!
Hi Peewee,
We do understand your frustration. As mentioned before our engineering team are aware of the problem and are investigating this as a matter of urgency.
Kind regards,
Craig
I’ll try to be patient 
Just checking back now and then
Why do you both? It’s just another hoop to jump through to change text from unsigned to signed in Manage extensions. We gave up on that after the first go because it didn’t change anything for our users.
Is it fixed yet?? We have an important update, and our customers really can’t wait any longer…
We also have a problem with this issue and customers are getting upset with us for not releasing the new version with the critical bugfix we made. They expected an update a week ago and want to know what we are doing about the issue we have with signing. So top priority for this issue would very much be appreciated!
Hello everyone!
We’ve just deployed and update that appears to resolve this issue. Could you please test it out and let us know how it goes?
Thank you!
Thank you Martin, it goes well now.
Thank you Martin, seems to work correct now.