-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
androidx.collection.ArrayMapKt is defined multiple times #18665
Comments
@moljac thoughts? |
We've added this issue to our backlog, and we will work to address it as time and resources allow. If you have any additional information or questions about this issue, please leave a comment. For additional info about issue management, please read our Triage Process. |
Oh yaeah and I was born in 1968 when XF used to work. Try updating to latest nugets... And paste here I saw that error somewhere but old butt like me cannot remember any-amore |
the version of the library (Xamarin.GooglePlayServices.Auth) worked is 119.2.0.3 in XF Below is the one in the new .net 7.0, where it isn't working
|
It is much more complicated. Something is transitively pulling in older nugets. I did analysis and found one for now. Can you try adding explicitly this nuget, please?
It worked on my sample. If that helps please report it here (I need it for analysis and record) and close this issue please.
Yup. I was able to repro.
|
One of the reasons is also This PR fails on public DeviceTests - xharness seems to crash. AndroidX versions used by MAUI are behind pulling transitively older versions with types that were moved by google to new artifacts.
Important: for this error patch numbers are very important (so called alignment bumps) |
@moljac including this package worked.
|
1.6.2
this did not worked for me. I get the below error Severity Code Description Project File Line
|
@SushmithaBanoji
|
@Mirksar Thanks. It worked. |
Adding "Xamarin.AndroidX.Fragment.Ktx" worked fir me |
Thanks matteomonizza. This also fixed my issues with upgrading our MAUI project to .net 8. |
For me, this configuration did the trick (migrating to .Net 8) <PackageReference Include="Xamarin.Firebase.Messaging">
<Version>123.3.1</Version>
</PackageReference>
<PackageReference Include="Xamarin.AndroidX.Fragment.Ktx ">
<Version>1.6.2.1</Version>
</PackageReference> |
Not working here: <PackageReference Include="Xamarin.AndroidX.Activity" Version="1.8.1.1" />
<PackageReference Include="Xamarin.AndroidX.Activity.Ktx" Version="1.8.1.1" />
<PackageReference Include="Xamarin.AndroidX.Fragment.Ktx" Version="1.6.0.1" />
<PackageReference Include="Xamarin.Firebase.Messaging" Version="123.3.1" />
|
@mfeingol try changing version to "1.6.2" on PackageReference Include="Xamarin.AndroidX.Fragment.Ktx" Version="1.6.0.1" It worked for me. |
Thanks, @mikelor. For some reason I forgot to check for updates. This appears to work: <ItemGroup Condition="'$(TargetFramework)' == 'net8.0-android34.0'">
<PackageReference Include="Xamarin.GooglePlayServices.Location" Version="121.0.1.4" />
<PackageReference Include="Xamarin.AndroidX.Activity" Version="1.8.1.1" />
<PackageReference Include="Xamarin.AndroidX.Activity.Ktx" Version="1.8.1.1" />
<PackageReference Include="Xamarin.AndroidX.Fragment.Ktx" Version="1.6.2.1" />
</ItemGroup> (The firebase reference isn't needed, at least in my case.) |
Description
I am creating a mobile app using .NET MAUI 7.0. This mobile app will use Google OneTap signin facility for android. However, when imported this nuget library Xamarin.GooglePlayServices.Auth, I get the below error.
I have attached the github repo to reproduce at your end.
https://github.com/sabrigo/googlesignin
Steps to Reproduce
Link to public reproduction project repository
https://github.com/sabrigo/googlesignin
Version with bug
7.0.101
Is this a regression from previous behavior?
Yes, this used to work in Xamarin.Forms
Last version that worked well
Unknown/Other
Affected platforms
Android
Affected platform versions
No response
Did you find any workaround?
No response
Relevant log output
The text was updated successfully, but these errors were encountered: