Have you been able to reproduce it yourself locally? I would love to watch the log file, perhaps it can reveal what class it doesn’t find.
@Dragosha: I just downloaded Look You Loot, and I got the same issue! Yay! (or something :/)
“Didn’t find class “com.defold.adtruth.InstallReceiver””
It’s part of an internal extension that we removed this sprint.
Could it be that you have a custom AndroidManifest.xml that references this class?
If so, you should be able to remove it and try again?
Did it it work for you on your phone?
@agulev: Could this be the issue for you as well?
1 Like
Do you have a custom AndroidManifest.xml?
With “com.defold.adtruth.InstallReceiver” in it?
yes, I use custom AndroidManifest.xml (some NE required it) with:
<service android:name="com.defold.adtruth.InstallReceiver"/>
<receiver
android:name="com.defold.adtruth.InstallReceiver"
android:exported="true">
<intent-filter>
<action android:name="com.android.vending.INSTALL_REFERRER" />
</intent-filter>
</receiver>
Seems, I need to remove this strings?
1 Like
Yes, I’m sorry for this hickup. We didn’t really think of the custom manifests you are using.
You can compare with the manifest in the builtins/ folder, where we have removed it.
6 Likes
That’s why AAR support would be useful =)
Would be great if you are writing in version release notes about changes in manifest. Thanks!
Yes, and why we want it. It’s still in the backlog. (/DEF-2544)
Yes, it was just that we missed it this time. Our policy is ofc to always make our users aware of actions they need to take when using a new release or feature.
4 Likes
The thing with AdTruth is that it’s a small King internal extension for use by King games to handle install attribution. It’s been there since day one, but now that we have native extensions we’re able to remove it and let King teams use it as an extension instead. It’s never been documented or used by anyone outside of King and that’s why we simply forgot about custom manifests when we removed it. We’re sorry for this. Our ambition is to always notify you guys of any changes affecting you and your games.
8 Likes
Thank you!
I thought AdTruth was part of Defold analytics install tracking.
2 Likes
0 crashes for me for the last two days (since last update with right AndroidManifest).
Thank you, guys!
6 Likes
Here is my new report for 1.2.141 with truth androidmanifest:
crashes:
seems like a stable release!
signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)
base.apk
10 Nov 12:29 on app version 59
LGE V20 (elsa), Android 8.0
Report 1 of 1
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
pid: 0, tid: 0 >>> com.dragosha.hamster <<<
backtrace:
#00 pc 0000000000e31bfa /data/app/com.android.chrome-QKOp7l_Y8kbQB83wDK7V8Q==/base.apk
#01 pc 0000000001195221 /data/app/com.android.chrome-QKOp7l_Y8kbQB83wDK7V8Q==/base.apk
ANR:
5 Likes
Hmm, I remembered that this bug was fixed, but there is again null pointer in iap module:
java.lang.NullPointerException
com.defold.iap.IapGooglePlayActivity.onCreate
All 8 crashes on Android 5.0
Engine ver: 1.2.141
LGE LG Prime Plus 4G (mc90ds), Android 5.0
Report 1 from 8
java.lang.RuntimeException:
at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:2331)
at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:2391)
at android.app.ActivityThread.access$800 (ActivityThread.java:151)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1309)
at android.os.Handler.dispatchMessage (Handler.java:102)
at android.os.Looper.loop (Looper.java:135)
at android.app.ActivityThread.main (ActivityThread.java:5354)
at java.lang.reflect.Method.invoke (Native Method)
at java.lang.reflect.Method.invoke (Method.java:372)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:908)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:703)
Caused by: java.lang.NullPointerException:
at com.defold.iap.IapGooglePlayActivity.onCreate (IapGooglePlayActivity.java:223)
at android.app.Activity.performCreate (Activity.java:6021)
at android.app.Instrumentation.callActivityOnCreate (Instrumentation.java:1105)
at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:2284)
4 Likes
Yes, that issue should be fixed in the next release (1.2.142) (DEF-3585)
5 Likes
Released in 1.2.142
1 Like
engine version 1.2.144
java.lang.IllegalArgumentException
com.dynamo.android.DefoldActivity.onCreate
Wiko FEVER (l5460), Android 6.0
1 / 2
java.lang.RuntimeException:
at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:2572)
at android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:2654)
at android.app.ActivityThread.-wrap11 (ActivityThread.java)
at android.app.ActivityThread$H.handleMessage (ActivityThread.java:1488)
at android.os.Handler.dispatchMessage (Handler.java:111)
at android.os.Looper.loop (Looper.java:207)
at android.app.ActivityThread.main (ActivityThread.java:5728)
at java.lang.reflect.Method.invoke (Native Method)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main (ZygoteInit.java:679)
Caused by: java.lang.IllegalArgumentException:
at android.app.NativeActivity.onCreate (NativeActivity.java:170)
at com.dynamo.android.DefoldActivity.onCreate (DefoldActivity.java:205)
at android.app.Activity.performCreate (Activity.java:6376)
at android.app.Instrumentation.callActivityOnCreate (Instrumentation.java:1113)
at android.app.ActivityThread.performLaunchActivity (ActivityThread.java:2519)
1 Like
I don’t have source code access at the moment but @Johan_Beck-Noren should be able to check tomorrow what changes (if any) could cause this problem.
Anything in particular about the devices? Android OS versions?
In my both my cases it was Android 6.0 (ZTE BLADE V7 (P653A10) and Cubot MAX (x6069_cubot_5365u))
UPD:
Looks like android 6 can’t find libname path for some reason https://android.googlesource.com/platform/frameworks/base/+/android-cts-6.0_r32/core/java/android/app/NativeActivity.java#170
1 Like