Hi everyone,

A huge amount of contrition here (from Andy), I gaffed…

A little bit of immature code, designed for an upcoming feature, slipped out with the last release (5.2.35) at 9pm last night, and corrupted attachments when sent. Thanks to people reporting it over night, I was able to dive on it the moment I walked into the office, and it’s now resolved in the newly released 5.2.37, which Chrome should have already begun upgrading to.

We’ll add a wider variety of attachments to our QA process to catch this in the future.

Categorised in:

This post was written by AndyM

  • randywood84

    How do we force 5.2.37 to download? I’m still on 5.2.36 and can’t figure out how to force Chrome to update to newest version.