This issue started on 10/9/2017 after a release from Facebook. We will be deploying a fix for this in our 7.35.0 release on 10/15/2017.