Aaaaaaand it got disabled again.
I just had the same thing happen, JSYK
It may be
this issue, but I'm still finding it hard to understand the Google explanations: specifically the stuff that varies between Chrome, Chrome beta, Chrome developer versions, Chromium, and Canary. There was
this restriction, but that was as of Chrome 33, so I would have expected it to start causing problems earlier.
If this is indeed the issue, then all the solutions on your side are kinda awful. The easiest might be to install a nearly-identical Chrome variant like
Chromium or
Canary. Then the Chrome folks decide that you're an advanced enough user that Google will let you manage your own non-store extensions.
Obviously this isn't ideal. I'm really surprised that there's no advanced-user way, maybe hiding in
chrome://flags or something. FWIW, you can also avoid the restrictions by unpacking the .crx and installing the extension as an "unpacked" folder, but I suspect that will prevent you from getting Salvager beta updates. Or you can switch to Mac or Linux.
So probably the best solution is for us to put the beta version in the Chrome store alongside the regular version, as yed suggested.
It feels like the wrong answer though. My current solution feels wrong too... there ought to be some more Chrome-compliant way to handle beta versions of extensions.
If Google Cast, straight from the folks who make the browser, is any indication, then separate store entries for beta and stable is the way to do it. For automated uploading, this turned up on a quick search.
This guy is using a macro program to automate clicking through the manual upload. I'm looking for something fully scripted, like the
existing release tasks.