Same here, but as AirborneMarik mentioned above they have a workaround posted on the Visual Studio developer community in this thread: https://developercommunity.visualstudio.com/t/Cannot-add-Apple-Account-VS-2002-Enter/10773193 I believe the primary workaround is that you can still manually specify your provisioning profile and signing certificate even though Visual Studio doesn't let you sign in to your Apple developer account. This workaround came too late for me, but I was able to build, debug and deploy on the mac using a combination of the dotnet CLI, VSCode, and Xcode. I still used Windows to do Android development and deployment, and just used the mac for iOS. I did run into a problem where the publish was failing on Windows because it wasn't able to do the iOS build, so I ended up setting up my .csproject file so that it only targets iOS if running on a mac, and only targets Android if running on Windows. Oh, and there seems to be an issue in XCode when doing the publish to the store, so you have to choose the "Custom" option so it lets you select the provisioning profile. For some reason it detected the signing cert okay, but it didn't choose the profile even though it was the only one in the dropdown list. It is unfortunate that a critical feature of the developer experience was deleted seemingly without warning. It almost feels like an attempt to push people towards native development tools by not providing a stable platform for multi-platform development systems.