MS Xamarin deprecated - xamarin

When exactly Microsoft announced that MS Xamarin mobile app development framework would be deprecated? I mean the date of the first announced plan that Xamarin would be deprecated.

Not sure if this qualifies as "deprecated", but during the Build 2020 conference, Microsoft announced that Xamarin Forms will be merged into the new .NET MAUI Framework.
Here's a relevant quote from the official blog entry:
Xamarin.Forms will ship a new major version later this year, and continue to ship minor and service releases every 6 weeks through .NET 6 GA in November 2021. The final release of Xamarin.Forms will be serviced for a year after shipping, and all modern work will shift to .NET MAUI.
Note that this quote only applies to Xamarin.Forms, the cross-plattform UI Framework.
The underlying technologies Xamarin.iOS and Xamarin.Android, which allow you to compile C# code to iOS and Android packages, are alive and kicking and have become an official part of .NET. The blog entry states:
As part of our .NET unification, Xamarin.iOS and Xamarin.Android will become part of .NET 6 as .NET for iOS and .NET for Android.

The end of support date for the current version of Xamarin.Forms (5.0), Xamarin.Android (14) and Xamarin.iOS (15) is May 1, 2024: https://dotnet.microsoft.com/en-us/platform/support/policy/xamarin

Related

Xamarin Xamarin.Android Xamarin.iOS - End of Support

I'm looking for official and up-to-date information about Xamarin.Android and Xamarin.iOS End of Support.
The official Microsoft page seems obsolete as lastest Xamarin.Android and Xamarin.iOS are not listed.
https://dotnet.microsoft.com/en-us/platform/support/policy/xamarin
Anyone having a link to the official information about:
Last Xamarin.Android version ever released and End of Support.
Last Xamarin.iOS version ever released and End of Support.
Official .NET 6 for Android release date and End of Support.
Official .NET 6 for iOS release date and End of Support.
There are descriptions about the end of support in the link
At least two years from last release date, or newer release.
And the latest stable version of xamarin.ios is 14.0.0.0, it released in September 21, 2020.
the latest stable version of xamarin.android is 12.1.99.117, it released in January 5, 2022.
This is the latest update I found today and seems they are not planning to continue with Xamarin.
It would be good to start the migration from Xamarin.forms to .Net MAUI ASAP now.
I don't think we will able to migrate Xamarin.iOS and Xamarin.Android projects. So for that, we have to start from scratch with another tech.
Check the latest update here.

UIWebView warning in Xamarin Forms iOS

Sending my .ipa to Apple, I received this warning:
Apple will no longer accept submissions of new apps that use UIWebView as of April 30, 2020 and app updates that use UIWebView as of December 2020. Instead, use WKWebView for improved security and reliability. Learn more (https://developer.apple.com/documentation/uikit/uiwebview).
I followed carefully this solution
Forms 4.5 or newer.
Xamarin.iOS 13.10.0.17
Visual Studio 16.4.3
This flag in the additional mtouch arguments field: --optimize=experimental-xforms-product-type
Still getting the warning.
I think it is because I references Telerik controls in my project, but I also followed this solution
No luck yet
This post has the answer
In my project I have as a nuget a reference to
Xamarin.Forms.Visual.Material
and this internally references to
Xamarin.iOS.MaterialComponents
The version of the components was old (72) so I added as a new nuget the latest version Xamarin.iOS.MaterialComponents, (nowadays it is 92), uploaded a new .IPA and the error dissapeared.

No PCL option for Xamarin project

I'm just getting into Xamarin Forms based app development and most of the articles -- if not all -- that I've come across suggest I create a new Xamarin Forms project using Portable Class Library (PCL) approach.
I'm running the latest version of Visual Studio 2017 15.5.1 and when I start a new Xamarin Forms project, I get the following screen with no PCL option.
Am I missing something?
You Can Select .Net Standard. it is Replacement of PCL.
NET Standard is a formal specification of .NET APIs that are intended to be available on all .NET runtimes (such as .NET Framework, Mono, and .NET Core)
For More Details Please visit : https://blog.xamarin.com/building-xamarin-forms-apps-net-standard/

Building a Watch OS2 application using Xamarin forms

As per Xamarin documentation Watch OS2 is supported only on simulator and still updates for device support are awaited.
https://blog.xamarin.com/watchos-2-preview-and-updates/
Is it somehow possible to build the application in Xamarin and WatchApp in Xcode?
Ref: Xamarin.iOS 9.3 preview #3 for tvOS and WatchOS 2.0 in Visual Studio
May 14 2016
I'll copy a comment from another thread for cross-referencing here:
I asked the team about this. Updating the watchOS 2 preview to add bitcode support is a high priority. It is among the top priorities the engineering team will be working on after this week's Evolve conference. Apple's recent announcement that watchOS 2 will be required for all new watchOS app submissions starting in June is definitely on the minds of the engineering team.
The hope is that a preview with bitcode support can be made available by the end of May, but the team is still wary of any unanticipated complications that could change that timeline.

MVVMCross Unified Announcement

I am new to MVVMCross and ~6 Mos with Xamarin…
From the Xamarin blog post today : http://blog.xamarin.com/unified-api-and-64-bit-support-complete/
What does that mean as far as MVVMCross is concerned?
I am using MVVMCross 3.2.2 Xamarin Forms (Android, iOS, WinPhone 8.0) and added a Universal Project for Windows Store/Phone 8.1.
MVVMCross and all of the plugins will have to be updated to support the new Unified API that is currently in Alpha. Once they release this you can migrate your iOS application over.
I know that Stuart and Thomasz have already been working on this though. Ideally, if you read through the post you should look to migrate around January 5th when it hits stable.

Resources