There’s currently an issue where you need to revoke and regenerate tokens on apps.twitter.com, yes.
In both of your cases, this sounds like a general OAuth issue. Things to look at - are you system clocks accurate? Are you properly encoding the request?
@Chirag24624560 I just used the RestSharp code generated by Postman in a new dotnet console application to post a Tweet update. That code looks a little different to the code you’ve posted above.
using System;
using RestSharp;
namespace testclient
{
class Program
{
static void Main(string[] args)
{
var client = new RestClient("https://api.twitter.com/1.1/statuses/update.json?status=another%20test%20in%20dotnet");
var request = new RestRequest(Method.POST);
request.AddHeader("Cache-Control", "no-cache");
request.AddHeader("Authorization", "OAuth oauth_consumer_key=\"xxx\",oauth_token=\"xxxxr\",oauth_signature_method=\"HMAC-SHA1\",oauth_timestamp=\"1523311958\",oauth_nonce=\"xxxx\",oauth_version=\"1.0\",oauth_signature=\"xxxx"");
request.AddHeader("Content-Type", "application/x-www-form-urlencoded");
request.AddHeader("Content-Length", "11964");
request.AddHeader("Accept-Encoding", "gzip;q=1.0,deflate;q=0.6,identity;q=0.3");
IRestResponse response = client.Execute(request);
Console.WriteLine(response.Content);
}
}
}