Open vsfeedback opened 2 years ago
@vsfeedback Thanks for the feedback.
Repro sample maybe? Content of the project files? That would help. Thanks
@vsfeedback Thanks for the feedback.
Repro sample maybe? Content of the project files? That would help. Thanks
This issue is the same as https://github.com/xamarin/GooglePlayServicesComponents/issues/532 which is not fixed yet even though the issue is closed GoogleAuthUtil still missing in the latest Xamarin.GooglePlayServices.Auth.Base
This issue has been moved from a ticket on Developer Community.
I'm trying to compile my Android project that uses the Plugin.GoogleClient package. I have the Xamarin.GooglePlayServices.Auth (https://www.nuget.org/packages/Xamarin.GooglePlayServices.Auth/119.2.0.1?_src=template) package installed, however the linker cannot find the GetToken() method even though it is included within that package. Here is the error that I get:
error XALNK7000: Mono.Linker.MarkException: Error processing method: 'System.Void Plugin.GoogleClient.GoogleClientManager/<>c__DisplayClass48_0::b__1()' in assembly: 'Plugin.GoogleClient.dll' ---> Mono.Cecil.ResolutionException: Failed to resolve System.String Android.Gms.Auth.GoogleAuthUtil::GetToken(Android.Content.Context,Android.Accounts.Account,System.String)
error XALNK7000: at Mono.Linker.Steps.MarkStep.HandleUnresolvedMethod(MethodReference reference)
error XALNK7000: at Mono.Linker.Steps.MarkStep.MarkMethod(MethodReference reference)
error XALNK7000: at Mono.Linker.Steps.MarkStep.MarkInstruction(Instruction instruction)
error XALNK7000: at Mono.Linker.Steps.MarkStep.MarkMethodBody(MethodBody body)
error XALNK7000: at Mono.Linker.Steps.MarkStep.ProcessMethod(MethodDefinition method)
error XALNK7000: at Mono.Linker.Steps.MarkStep.ProcessQueue()
error XALNK7000: --- End of inner exception stack trace ---
error XALNK7000: at Mono.Linker.Steps.MarkStep.ProcessQueue()
error XALNK7000: at Mono.Linker.Steps.MarkStep.ProcessPrimaryQueue()
error XALNK7000: at Mono.Linker.Steps.MarkStep.Process()
error XALNK7000: at Mono.Linker.Steps.MarkStep.Process(LinkContext context)
error XALNK7000: at MonoDroid.Tuner.MonoDroidMarkStep.Process(LinkContext context)
error XALNK7000: at Mono.Linker.Pipeline.ProcessStep(LinkContext context, IStep step)
error XALNK7000: at Mono.Linker.Pipeline.Process(LinkContext context)
error XALNK7000: at MonoDroid.Tuner.Linker.Process(LinkerOptions options, ILogger logger, LinkContext& context)
error XALNK7000: at Xamarin.Android.Tasks.LinkAssemblies.Execute(DirectoryAssemblyResolver res)
error XALNK7000: at Xamarin.Android.Tasks.LinkAssemblies.RunTask()
error XALNK7000: at Microsoft.Android.Build.Tasks.AndroidTask.Execute() in /Users/builder/azdo/_work/1/s/xamarin-android/external/xamarin-android-tools/src/Microsoft.Android.Build.BaseTasks/AndroidTask.cs:line 17
Original Comments
Feedback Bot on 10/20/2021, 11:27 PM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.
Jonathan Pobst [MSFT] on 10/25/2021, 08:37 AM:
This type looks like it is actually in
Xamarin.GooglePlayServices.Auth.Base
, and was removed between version117.0
and117.1
:https://www.fuget.org/packages/Xamarin.GooglePlayServices.Auth.Base/117.0.0/lib/monoandroid90/Xamarin.GooglePlayServices.Auth.Base.dll/Android.Gms.Auth/GoogleAuthUtil
I have filed an issue to investigate it to be fixed:
https://github.com/xamarin/GooglePlayServicesComponents/issues/532
For now, the workaround would be to use the
117.0
version of theXamarin.GooglePlayServices.Auth.Base
NuGet package.Alexander Perelberg on 11/30/2021, 08:52 AM:
That workaround does not work.
The only workaround I found was to completely remove Plugin.GoogleClient from the entire Android project.
Please let me know if this issue is going to be fixed in the near future.
Feedback Bot on 2/9/2022, 11:27 PM:
I detected that this issue hasn’t received a lot of activity, votes, or comments in the past 90 days. Based on this, the issues severity and affected area, it’s my experience that this issue is unlikely to get fixed. To improve the situation, consider following best practices for quality problem reports, and giving us more details on how this issue is impacting you.
Original Solutions
(no solutions)