You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.
The Xamarin Component restore operation requires a Xamarin account. Since it is no longer required to have a Xamarin account to build Xamarin apps, the component restore operation can fail because the endpoint expects a Xamarin account. Many Xamarin newcomers will not have Xamarin accounts because of its inclusion in Visual Studio and Xamarin Studio.
This goes unnoticed by someone developing with a Xamarin account, but will be a major point of frustration for those running the app for the first time with Community editions of Visual Studio or Xamarin Studio, and with no Xamarin account logged into the IDE.
It would be a good idea to switch all component references to comparable NuGets, as nuget.org does not require authorization to restore packages.
The text was updated successfully, but these errors were encountered:
We will evaluate the cost/time to update the apps due to not all the same components/versions are available in nuget so the change could be not so easy.
One of those newcomers who don't have Xamarin accounts here:
I need this done. There's no reason to require the account only on this specific case. And there do seem to be components out there worth using from what I can tell, starting, for example, with Android Support Design Library.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The Xamarin Component restore operation requires a Xamarin account. Since it is no longer required to have a Xamarin account to build Xamarin apps, the component restore operation can fail because the endpoint expects a Xamarin account. Many Xamarin newcomers will not have Xamarin accounts because of its inclusion in Visual Studio and Xamarin Studio.
This goes unnoticed by someone developing with a Xamarin account, but will be a major point of frustration for those running the app for the first time with Community editions of Visual Studio or Xamarin Studio, and with no Xamarin account logged into the IDE.
It would be a good idea to switch all component references to comparable NuGets, as nuget.org does not require authorization to restore packages.
The text was updated successfully, but these errors were encountered: