0

I have a few extension on the Chrome Web Store. The problem I have is that in another on of my extensions, I screwed up with an update, and it ruined the application unless it was reinstalled, unbeknownst to my user base. I want to test compatibility between versions, and my original idea went like so:

  • Package current version into .crx
  • Package new version into .crx using .pem from the current version
  • Install current version in Chrome
  • Install the new version over it as an update

This no longer works because Chrome disabled the updating extensions not installed from the Chrome web store. What way is there to test version compatibility before launch?

Xan
  • 74,770
  • 16
  • 179
  • 206
fwjggYUKGFTYucfty
  • 136
  • 1
  • 2
  • 12
  • How could it require a reinstall instead of just pushing another update? – Daniel Herr Sep 18 '16 at 22:29
  • @DanielHerr because I could have made a mistake in the code, that messes up the extension upon an update. I need a way to test the update from the current version to the new one without actually distributing the update. – fwjggYUKGFTYucfty Sep 19 '16 at 01:49

1 Answers1

0

You can try out to mark the published extension as either unlisted or trusted testers. Its discussed on this StackOverflow question

Community
  • 1
  • 1
adjuremods
  • 2,938
  • 2
  • 12
  • 17