Skip to content
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

Ambiguous overloads found for onGoogleAdIdRead #288

Open
CSystem opened this issue Mar 12, 2024 · 3 comments
Open

Ambiguous overloads found for onGoogleAdIdRead #288

CSystem opened this issue Mar 12, 2024 · 3 comments

Comments

@CSystem
Copy link

CSystem commented Mar 12, 2024

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

image
@JRGreenfield
Copy link

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
Copy link

JGedmr commented Jul 24, 2024

Same problem: "Ambiguous overloads found for onGoogleAdIdRead"

Unity version: 2022.3.37f1
Adjust: 4.38.1
Any solution?

@uerceg uerceg mentioned this issue Aug 27, 2024
@uerceg
Copy link
Contributor

uerceg commented Aug 27, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants