Note that there are some explanatory texts on larger screens.

plurals
  1. POLinq to Twitter Authenticated But Getting 215 "Bad Authentication Data"
    primarykey
    data
    text
    <p>I have been using Linq to Twitter for Authenticating with OAuth for the Twitter API 1.1. I set my credentials and then pass them to Linq to Twitter which states I that isAuth returns true. However, at run time I receive at 215 "Bad Authentication Data" error. Has anyone else had this problem?</p> <pre><code> var auth = new SingleUserAuthorizer { Credentials = new InMemoryCredentials { ConsumerKey = TwitterSettings.ConsumerKey, ConsumerSecret = TwitterSettings.ConsumerKeySecret, OAuthToken = TwitterSettings.AccessToken, AccessToken = TwitterSettings.AccessTokenSecret, } }; auth.Authorize(); } </code></pre> <p>And here is the if else that is stating I am authorized:</p> <pre><code> if (auth == null || !auth.IsAuthorized) { } // If Twitter Authorizes Application if (auth.IsAuthorized &amp;&amp; i == 1) { HttpClient client = new HttpClient(); HttpResponseMessage response = await client.GetAsync(new Uri("https://api.twitter.com/1.1/search/tweets.json?q=%23freebandnames&amp;since_id=24012619984051000&amp;max_id=250126199840518145&amp;result_type=mixed&amp;count=4")); string json = await response.Content.ReadAsStringAsync(); JObject obj = JObject.Parse(json); var jsonResults = obj["results"]; await JsonConvert.DeserializeObjectAsync&lt;List&lt;Tweet&gt;&gt;(jsonResults.ToString()); } </code></pre> <p>I am able to get into the auth.IsAtuhorized portion of the code but the response is returning a 215 error. Also I know my URI is correct because I copied it straight from the Twitter API 1.1 example page to test the call. Thanks in Advance</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload