New Error requesting email: (403) Forbidden


#1

We’ve been getting an interesting error on SOME of the OAUTH requests to login from Twitter. Not sure if this is something new or something changed or?

ml: S, pragma: no-cache, Content-Length: 203, Cache-Control: no-cache, no-store, must-revalidate, pre-check=0, post-check=0, Content-Type: application/xml;charset=utf-8, Date: Thu, 14 Jun 2018 19:14:11 GMT, Expires: Tue, 31 Mar 1981 05:00:00 GMT, Last-Modified: Thu, 14 Jun 2018 19:14:11 GMT, Set-Cookie: personalization_id=“An id was returned here==”; Expires=Sat, 13 Jun 2020 19:14:11 GMT; Path=/; Domain=.twitter.com,guest_id=v1-anotherID-; Expires=Sat, 13 Jun 2020 19:14:11 GMT; Path=/; Domain=.twitter.com, Server: tsa_a, status: 403 Forbidden, strict-transport-security: max-age=631138519, x-connection-hash: 8677d631673970b89d59eb78d7137f91, x-content-type-options: nosniff, x-frame-options: SAMEORIGIN, x-response-time: 12, x-transaction: 00bfa5bd00fc44cd, x-twitter-response-tags]: BouncerCompliant, x-ua-compatible: IE=edge,chrome=1, x-xss-protection: 1; mode=block; report=https://twitter.com/i/xss_report, Error requesting email: The remote server returned an error: (403) Forbidden., Forbidden, Forbidden, System.Net.SyncMemoryStream, Response Stream: <?xml version="1.0" encoding="UTF-8"?>Callback URL not approved for this client application. Approved callback URLs can be adjusted in your application settings

Ideas?