2014-09-29, 21:09
Version 1.0.16
Changes:
On my REPO.
Most likely, everyone who updated to the new version will have to re-authorize the addon when the current users token expires (you may have already gotten errors because of this) - there will be a dialog asking if you want to re-authorize when this happens. Sorry about that, but I guess that's what my private repository is for. You get the newest updates, as well as all the newest bugs. But you also get that warm fuzzy feeling of helping the the rest of the users have a stable addon by being a (perhaps unsuspecting) beta tester
Changes:
- Updated OAuth module because it was accidently overwriting the refresh token on refresh thereby making the next refresh impossible.
On my REPO.
Most likely, everyone who updated to the new version will have to re-authorize the addon when the current users token expires (you may have already gotten errors because of this) - there will be a dialog asking if you want to re-authorize when this happens. Sorry about that, but I guess that's what my private repository is for. You get the newest updates, as well as all the newest bugs. But you also get that warm fuzzy feeling of helping the the rest of the users have a stable addon by being a (perhaps unsuspecting) beta tester