6.7 C
New York
Thursday, March 13, 2025

Xamarin.Types iOS venture not resolving Xamarin’s namespaces whereas Android does & the alternative if up to date


Utilizing .Internet 5.0 /
Xamarin.Types v5.0.0.2125

I re-opened a venture I used to be constructing with .NET 5.0 prior to now and have been attempting to deliver it again to life, the whole lot works properly with android however it does not work with iOS solely due to the namespace decision ( the utilizing statements ) and I do not know what to do actually for the reason that intellisense is not even serving to.
The images of what’s occurring are on the backside of the put up.

I’ve up to date your complete answer to the most recent of each package deal after which the issue shifted from iOS to android saying xamarin.types android venture couldn't discover 15 android x assemblies asking me to put in 3 nuggets packages:

Xamarin.AndroidX.Legacy.Help.V4
Xamarin.AndroidX.Lifecycle.LiveData
Xamarin.AndroidX.Migration

which if I do says doesn't assist .netframework2.0 ( if doing it from the answer’s nuggets )/doesn't assist monoandroid11.0 ( if doing it from the android venture’s nuggets ).

So my thought was to stick with the “legacy” model of Xamarin.Types because it was working with none issues prior to now however proper now I am misplaced.

I additionally tried to increment the model of Xamarin.Types little by little to see if it will resolve the usings at one level within the iOS venture however that did not work.

Now I do not actually know if I ought to replace the whole lot and mess with the android venture for which nothing works or not replace and mess with the iOS venture for which nothing works.

I additionally tried uninstalling and re-installing Xamarin.Types from the Resolution’s packages, tried to dotnet restore, clear construct, shut VS 2022, open it and rebuild however nothing labored.

Both manner, how can I make the iOS venture resolve the utilizing statements ?

AppDelegate.cs
Image 1: AppDelegate.cs

A customized iOS file referred to as CustomFrameRenderer.cs
Image 2: a custom iOS file called CustomFrameRenderer.cs

utilizing statements not resolving in one other file

Image3: using statements not resolving

iOS venture’s nugget packages
enter image description here

Android venture’s nugget packages
enter image description here

Resolution venture’s nugget packages
enter image description here

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles