Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report for Bug 37261 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
Currently we are using Xamarin.Auth to connect to Twitter.
var authenticator = new OAuth1Authenticator(Platform.TwitterConsumerKey, Platform.TwitterConsumerSecret,
new Uri("https://api.twitter.com/oauth/access_token"), new Uri("https://mobile.twitter.com/"));
authenticator.Error += onAuthenticatorError;
authenticator.Completed += onAuthenticatorCompleted;
The Authentication succeeds and onAuthenticatorCompleted is called which is all good.
The problem is that right after that onAuthenticatorError is called even though I can successfully communicate with Twitter without any problems. I am wondering why that is happening.
The exception that I can view onAuthenticatorError is following:
"The remote server returned an error: (401) Authorization Required."
I am not sure if this is a bug in Xamarin.Auth or related to code in our project. Another developer has the same issue as posted in here:
I do maintain Xamarin.Auth my fork and samples are here:
I have tried to make my samples descriptive as much as posible. I have
even added markdown property which should explain how to setup server:
Currently we have problems with iOS and savinf AccountStore and as soon as we solve that we'll proceed with publishing nugets and component.
Reassigning this to Components as it appears to be an issue with Xamarin.Auth rather than Xamarin.Android