Ambiguous overloads found for onGoogleAdIdRead

[CSystem]

version: unity 4.37.1

Exception: Ambiguous overloads found for onGoogleAdIdRead with given parameters
at UnityEngine.AndroidJavaProxy.Invoke (System.String methodName, System.Object[] args) [0x00000] in <00000000000000000000000000000000>:0
at UnityEngine._AndroidJNIHelper.InvokeJavaProxyMethod (UnityEngine.AndroidJavaProxy proxy, System.IntPtr jmethodName, System.IntPtr jargs) [0x00000] in <00000000000000000000000000000000>:0
Rethrow as TargetInvocationException: com.adjust.sdk.AdjustAndroid+DeviceIdsReadListener.onGoogleAdIdRead(null)
at UnityEngine.AndroidJavaProxy.Invoke (System.String methodName, System.Object[] args) [0x00000] in <00000000000000000000000000000000>:0
at UnityEngine._AndroidJNIHelper.InvokeJavaProxyMethod (UnityEngine.AndroidJavaProxy proxy, System.IntPtr jmethodName, System.IntPtr jargs) [0x00000] in <00000000000000000000000000000000>:0

[JRGreenfield]

A small amount of our Android user base is also throwing a TargetInvocationException because of ambiguous overloads found for DeviceIdsReadListener::onGoogleAdIdRead(null).

Currently using Adjust 4.38.0 and Unity 2022.3.22f1.

[JGedmr]

Same problem: "Ambiguous overloads found for onGoogleAdIdRead"

Unity version: 2022.3.37f1
Adjust: 4.38.1
Any solution?

[uerceg]

Hey guys,

Sorry for a bit of waiting on this one. We have just shipped v5.0.2 which should hopefully address this issue.

Unfortunately, the fix is part of the version 5 and not the v4 which you might be using, so upgrade to the new version would be required.

Looking forward to hear from you whether this version solved this issue for you.

Cheers

[JRGreenfield]

Hello,

I just updated to v5.0.4 and I have not seen the error in Sentry during testing so far. We are going to rollout to a wider audience next week, so I will let you know if we see anything popup.

Thanks!

[uerceg]

Hey @JRGreenfield,

Thank you for getting back on this one. Looking forward to hearing back from you after wider rollout.

Cheers.