[Brian]

Took a bit, but we've contacted the appropriate folks at Google, negotiated a deal that should prevent this from happening again, and the fix should be in the next update. We don't have an ETA for that release, but it's on the way.