AzureDevOps Credentials Visual Studio MAC - macos

I just updated to MacOS Catalina because a Xamarin project needed the latest XCode. Everything was working before this update.
I am now unable to push to or pull from AzureDevops ({domain}.visualstuido.com), though I can clone a project from it without any problems.
When attempting to push or pull (even a project just cloned) I get the Microsoft sign-in dialog but it's blank (see image below).
I have tried rebooting (several times), restarting Visual Studio, applied all updates, (VS, MacOS, Java etc) but nothing is making any difference. Despite Googling this for several hours I can't any cause/resolution.
I'm looking for help on how to diagnose the cause and of course fix the problem.

Related

"No matching profiles found" with SiriKit in Visual Studio for Mac

I haven't found if anybody had similar problem. My Visual Studio for Mac project stopped seeing application provisioning profile after I added SiriKit support there. Just can't find it, nor automatically, neither when trying to set manually.
I have checked bundle id and all my Entitlements several times, as well as removing cache, relaunch Visual Studio and even restarting Mac, but nothing helped.
First point:
Xcode can see this provision profile perfectly. I've created test project with Extensions for Siri. It can see the provision profile, and even launch the test app on the real device. But not in Visual Studio for Mac.
Second point:
Visual Studio can see other provision profiles, which doesn't have SiriKit enabled. As well as the newly created provision profiles (without SiriKit).
Any ideas would be helpful.
My system set:
macOS Mojave, Version 10.14.2
Xcode, Version 10.1 (10B61)
Visual Studio for Mac (Community), Version 7.7.1 (build 15)
Mono Framework, Version 5.16.0.221
Xamarin.iOS, Version 12.2.1.12
Update
Looks like apple fixed it (see last comments in this thread). I was able to create new provision (with new bundle id) and VS for Mac saw it successfully. However I guess you need to regenerate old provisions at apple developer portal, as they still have duplicate keys.
Also, looks like an update for VS for Mac will come in the nearest few days, that will fix this issue with duplicate key (see this pull request), so you can just wait)
Question is closed
There is a bug which is causing such issues. Already reported here..
https://forums.developer.apple.com/message/343811#343811

Xamarin Studio 6.3 with mono 4.8.. suddenly debugger not working

I cannot hit breakpoints in Xamarin Studio since yesterday afternoon. Restart, clean, rebuild still no joy. Using Mac OSX. I am aware this issue is in version 5 of mono. But I am on 4.8. Is anyone having the same problem. Very frustrating.
Dump your local copy and pull a new copy from the repo.

How can I specify Xamarin version in Appveyor build process?

We use Appveyor for our continuous integration and it automatically includes the latest Xamarin version when creating the build vm.
However, all developers and the mac host for building the iOS app are using the previous version. We are unwilling to upgrade at this point as multiple projects are due to be released within the next few weeks and these big upgrades invariably add days of delay.
As such, it would be great if someone could show me how I can specify the Xamarin version when creating the build Vm. Thanks!
I sent an email to appveyor support and they replied with this partial solution:
I’m afraid we can’t have multiple versions of Xamarin as it ties pretty hard into Visual Studio environment. Maybe in the future they will do it more portable.
You can rollback to the previous build worker image for now. Add image: Previous Visual Studio 2015 to your appveyor.yml or select it on UI (Environment tab of project settings) if you don’t use yml. Of course, it’s not a long term solution as current image will become previous during the next update. It maybe Xamarin issue or the app should be upgraded to Xamarin Latest version.

Multiple errors when creating Xamarin.Forms - Blank Xaml App (Xamarin.Forms Portable) or Android App

I using Windows 10 and am trying to create a Xamarin.Forms - Blank Xaml App (Xamarin.Forms Portable) project for the first time. I have Visual Studio 2015 Enterprise Update 3 installed and have tried uninstalling, reinstalling, and repairing multiple times.
When I create a project, I get the following errors:
"The name 'InitializeComponent' does not exist in the current context"
"Error encountered while loading the project. Some project features, such as full solution analysis for the failed project and projects that depend on it, have been disabled" - for App, Droid, UWP, WinPhone, Windows, and iOS
"The XamlCTask task failed unexpectedly..." - for UWP, WinPhone, Windows, and iOS
I tried this on my work computer and home computer and I had the same issues with both.
I have tried updating Xamarin.Forms nuget to the latest version and the created 36 errors with Droid. I also tried going to c:/users/[YOURNAME]/AppData/Local. Delete the Xamarin folder and that did not solve the issue.
I tried creating other Visual Studio projects that did not involve Xamarin and did not have any issues with those. I know the issue is with Xamarin (probably something with Android) itself, but I don't think that there is anything that I am missing from the install. I tried installing it by first installing Visual Studio, then going to Modify and adding Cross Platform. That didn't work, so I uninstalled then downloaded the Xamarin Installer. I had the same issues with both.
I created a blank Android App and that give me the warning - "aapt.exe" exited with code - 1073741849".
A blank app for iPhone does not give any errors or warnings.
Windows Phone does not give any errors or warnings either.
Any ideas of what I should check for so I can get this working?
Here is a picture of the error that I'm getting
Try updating to the latest version of Forms to get rid of the XamlC errors. Assuming you haven't updated, the template is using a modestly old version. As for the aapt error, if you have the N SDK preview installed, removing that should help. Alternatively, make certain that you have up through API 23 installed.

Xamarin.Forms: "InitializeComponent does not exist" when cloning from Github

I have a Xamarin.Forms PCL Project (both iOS and Android). I can build it perfectly in my local repo. However, if I clone or download the same up-to-date code from Github, I got the error "InitializeComponent does not exist in the current context"
My setup is:
Xamarin.Forms PCL Project
Xamarin.Forms 1.5.0.6446
Xamarin Studio 5.9.7 (build 9)
Mac OS X
My gitignore file: https://gist.github.com/NamXH/00690ea72a426d9f0383
I am aware that there are some known bugs with "InitializeComponent does not exist" in a Shared Project or Visual Studio. However, I think mine is different.
There's another weird situation: If I update Xamarin.Forms packages to a newer version, the project can be built normally. However, if I discard all the changes (by checking out the commit before updating), I got the InitializeComponent error. When I checkout the latest commit (with the new packages changes), it can be built again. Everything is done locally in this situation.
Thanks for your help!
I have solved the problem. The issue is I use Github client for Mac and for some reasons the client does not detect all the changes in the packages folder. I have to use the git add command in the console to add the missing files (mostly dll files).
In short, every time I update packages, I have to use git commands in the console to add new changes.

Resources