SUMo still reporting Dropbox beta update when no betas allowed

[OldNavyGuy]

Now it's with version 159.3.5805

https://www.dropboxforum.com/t5/user/vi ... -id/308787

As before...

Dropbox makes it clear on its site which release is a beta, and which is stable.

The "Allow Beta versions" box is unchecked in SUMo.

Not sure why this keeps occurring.

[Kyle_Katarn]

Fixed, thanks

[OldNavyGuy]

Still happening...

Now it's with version 159.3.5865

https://www.dropboxforum.com/t5/user/vi ... -id/308787

[Kyle_Katarn]

Fixed, thanks

[OldNavyGuy]

Thanks.

Why does it keep breaking?

[Kyle_Katarn]

Only when a new beta is out until it gets reported and I manually flag it.

[OldNavyGuy]

That doesn't sound too good...

So are you saying there is no way on your end to tell that the Dropbox release is a beta?

It's pretty clear on the Dropbox site...

[Kyle_Katarn]

Yes but it's manual tagging on my server which sometimes may time some time... and goes super fast after user reports here

[OldNavyGuy]

That wastes a users time by -

1. Finally discovering that the update is in fact a beta (when the software has the option to not include betas).

2. Reporting it.

Seems like there needs to be a change in your process.

Users should not do the job the software is supposed to do.

[Kyle_Katarn]

It's not based on user reports, but classification is accelerated if user reports. SUMo globally has a low false positive rate