ANR caused by SDK

[JasonPool]

version：4.30.0; 4.33.0

#00 pc 0x00000000000bbb68 /apex/com.android.runtime/lib64/bionic/libc.so (nanosleep+8)
#1 pc 0x0000000000b549f4 /data/app/com.xxx.yyy-hLQxGi53oq2XOeaf8Z58YA==/split_config.arm64_v8a.apk!libil2cpp.so
#2 pc 0x0000000000b612d0 /data/app/com.xxx.yyy-hLQxGi53oq2XOeaf8Z58YA==/split_config.arm64_v8a.apk!libil2cpp.so
#3 pc 0x0000000000b06178 /data/app/com.xxx.yyy-hLQxGi53oq2XOeaf8Z58YA==/split_config.arm64_v8a.apk!libil2cpp.so
#4 pc 0x0000000000b105e8 /data/app/com.xxx.yyy-hLQxGi53oq2XOeaf8Z58YA==/split_config.arm64_v8a.apk!libil2cpp.so
#5 pc 0x000000000034dd80 /data/app/com.xxx.yyy-hLQxGi53oq2XOeaf8Z58YA==/split_config.arm64_v8a.apk!libunity.so
#6 pc 0x0000000000131e30 /data/app/com.xxx.yyy-hLQxGi53oq2XOeaf8Z58YA==/split_config.arm64_v8a.apk!libunity.so
#7 pc 0x0000000000131d48 /data/app/com.xxx.yyy-hLQxGi53oq2XOeaf8Z58YA==/split_config.arm64_v8a.apk!libunity.so
at com.unity3d.player.ReflectionHelper.nativeProxyInvoke (Native method)
at com.unity3d.player.ReflectionHelper.a (unavailable)
at com.unity3d.player.ReflectionHelper$1.invoke (unavailable)
at java.lang.reflect.Proxy.invoke (Proxy.java:1006)
at com.adjust.sdk.OnEventTrackingSucceededListener.onFinishedEventTrackingSucceeded (OnEventTrackingSucceededListener.java)
at com.adjust.sdk.ActivityHandler$43.run (ActivityHandler.java:1419)
at android.os.Handler.handleCallback (Handler.java:900)
at android.os.Handler.dispatchMessage (Handler.java:103)
at android.os.Looper.loop (Looper.java:219)
at android.app.ActivityThread.main (ActivityThread.java:8668)
at java.lang.reflect.Method.invoke (Native method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run (RuntimeInit.java:513)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:1109)

we not use adjustConfig.setEventSuccessDelegate in unity，but get this anr in google android vitals. how can i fix it.

[rbyjoswald]

I would also like to know this

[juanblasco]

Using v5.1.1 and still happening

[uerceg]

Hey guys,

Thank you for reporting this and sorry for the delay. We are looking at this on our end and we'll try to add the changes to next SDK release to make all the Unity callbacks dispatched to be executed inside of the Unity's main thread (vs. native main thread where they are being executed right now).

I'll keep you posted on the release to give it a shot once live.

[uerceg]

Hey guys,

We have just shipped v5.1.0 where we tried to address this issue. If possible, feel free to give it a shot and let us know if the issue still persists with this version or not. I'll close this ticket for the time being, but feel free to comment / reopen it if needed.

Looking forward to hearing back from you.

Cheers