3.1.0.220 Shall Live On In Infamy

gboulton · September 9, 2019, 12:21pm

It would seem I shall never rid myself of 3.1.0.220

3.1.0.213 always showed .220 as an available update when checking for updates…now .226 and .232 say I’m on the latest version, .220

It’s like a cheesy 80s slasher flick…the bad guy never dies! (Tell the truth, Jared and Ken…you’re just prepping for the upcoming AHS season, aren’t you?)

Ken · September 9, 2019, 2:10pm

That’s a bummer… something still messed up in the database. Will look shortly.

Jared · September 9, 2019, 2:30pm

It has been nuked from space. If you continue to see it let me know.

Jared

gboulton · September 9, 2019, 3:04pm

Wellll…

.232 now says this when I check for updates

Progress, I guess?

Jared · September 10, 2019, 1:52am

should be more better now.

Thanks!
Jared

gboulton · September 10, 2019, 11:33am

Man, I hate to be Debbie Downer, but…

Jared · September 10, 2019, 1:28pm

Do you have this option checked? (although if you’re on the beta “channel” you shouldn’t need it…)

gboulton · September 10, 2019, 4:48pm

Yes, that option is checked.

dnube · September 10, 2019, 5:12pm

Yes - getting same thing (restarted app after setting this checkbox to ‘on’ for include beta). Shows 3.0.3.169 as latest.

However, this is nothing I’m bothered about …

DaveNL

gboulton · September 10, 2019, 9:41pm

Not really anything to be bothered about on the end user side…but if an update check is returning/retrieving incorrect information, and/or “disabled” versions, it’s probably something the devs should be aware of.