If not in a beta, where would you expect these issues to be revealed? I am guessing that Dropbox has roughly 4 stages of "releasing": 1. Something for devs wo

If not in a beta, where would you expect these issues to be revealed? I am guessing that Dropbox has roughly 4 stages of "releasing": 1. Something for devs working on this feature get to see it in action. I would guess this means a few hundred people see this release. 2. A release for dropbox employees. I would guess a few thousand people see this release, and since they work at Dropbox I would guess that 99.9% of them keep these features enabled. 3. A beta release. This is the first time that we are likely to see anyone who actively disables integration features use the product, and even that is probably minimal. 4. Official release. You are extremely unlikely to see people disabling features like this in (1) and (2) unless the feature is so broken they can't use it. In fact they probably encourage people not to disable it so they can get more feedback about how the new integration is working. This leaves (3) the beta release as the most likely spot for this type of bug to pop up. This isn't a non-reversible bug. It doesn't delete your files or do anything that can't be reversed by reverting to an official release of Dropbox or quitting the app, both of which are relatively easy fixes. It also isn't a bug that is likely to be caught by the majority of Dropbox users. Based on my interactions with people, at least 75% of them keep the OS integrations enabled. Only techies even consider disabling it. As a result, this seems like exactly the type of bug that I would expect to see in a beta release, and I can't see any real harm in it making it that far.