Fixed
Status Update
Comments
[Deleted User] <[Deleted User]> #2
We had a similar crash in production but the obfuscated trace looks close and makes no sense:
Caused by java.lang.ClassNotFoundException
Didn't find class "com.google.android.aidl.BaseStub" on path: DexPathList[[zip file "/data/app/com.wayfair.wayfair.dev-Z7SYLQacxBCTrvutI7fmlQ==/base.apk"],nativeLibraryDirectories=[/data/app/com.wayfair.wayfair.dev-Z7SYLQacxBCTrvutI7fmlQ==/lib/arm64, /data/app/com.wayfair.wayfair.dev-Z7SYLQacxBCTrvutI7fmlQ==/base.apk!/lib/arm64-v8a, /system/lib64, /system/vendor/lib64]]
Caused by java.lang.ClassNotFoundException
Didn't find class "com.google.android.aidl.BaseStub" on path: DexPathList[[zip file "/data/app/com.wayfair.wayfair.dev-Z7SYLQacxBCTrvutI7fmlQ==/base.apk"],nativeLibraryDirectories=[/data/app/com.wayfair.wayfair.dev-Z7SYLQacxBCTrvutI7fmlQ==/lib/arm64, /data/app/com.wayfair.wayfair.dev-Z7SYLQacxBCTrvutI7fmlQ==/base.apk!/lib/arm64-v8a, /system/lib64, /system/vendor/lib64]]
ms...@gmail.com <ms...@gmail.com> #3
This issue was opened on the CleverTap sdk: https://github.com/adjust/android_sdk/issues/402
They say they reached out to Google and Google fixed it, but with the same version 1.1.
Can we have a new version? We need repeatable builds.
They say they reached out to Google and Google fixed it, but with the same version 1.1.
Can we have a new version? We need repeatable builds.
ms...@gmail.com <ms...@gmail.com> #4
Sorry, adjust sdk, not clevertap :)
ue...@gmail.com <ue...@gmail.com> #5
Give a try to:
implementation('com.android.installreferrer:installreferrer:1.1') { changing .= true}
Should be fixed as of few days ago.
implementation('com.android.installreferrer:installreferrer:1.1') { changing .= true}
Should be fixed as of few days ago.
ms...@gmail.com <ms...@gmail.com> #6
The problem is that there was a version 1.1 with the bug, and a new version 1.1 without the bug. This doesn't allow for repeatable builds. When an sdk/library has a correction or any change, a new version should be released. A given version number should have the identical behavior from one day to the next. Using this changing attribute like this is a bad practice.
wo...@gmail.com <wo...@gmail.com> #7
I don't think anyone would argue against this. Release fixes as fixes and don't pretend there wasn't a mistake.
kr...@gmail.com <kr...@gmail.com> #8
This issue is a saver! Who would think a new version/fix is released without version increment ... (facepalm)
al...@gmail.com <al...@gmail.com> #9
This is definitely not expected behaviour from Android Google team to push same version with fix without any notice.
ms...@gmail.com <ms...@gmail.com> #10
Can we please have a new version 1.2 with the fix, to avoid issues with the cached 1.1?
Note there are two problems with { changing .= true }
1) It appears that this is incorrect syntax resulting in a build error. The proper syntax seems to be { changing = true}
2) In our case, we have a nexus mirror which pulled in the original 1.1 which crashed. Our project only goes through this nexus mirror for dependencies. Using { changing = true } doesn't seem to work in our project, unless we also add the google() repository to the project, bypassing our mirror to get the latest 1.1 from google.
Note there are two problems with { changing .= true }
1) It appears that this is incorrect syntax resulting in a build error. The proper syntax seems to be { changing = true}
2) In our case, we have a nexus mirror which pulled in the original 1.1 which crashed. Our project only goes through this nexus mirror for dependencies. Using { changing = true } doesn't seem to work in our project, unless we also add the google() repository to the project, bypassing our mirror to get the latest 1.1 from google.
al...@google.com <al...@google.com>
ch...@google.com <ch...@google.com>
li...@google.com <li...@google.com>
ju...@google.com <ju...@google.com> #11
Please upgrade to the latest client version 1.1.2
b9...@gmail.com <b9...@gmail.com> #12
I'm using 2.0 and still facing this issue.
li...@google.com <li...@google.com>
li...@google.com <li...@google.com> #13
We released version 2.1 to fix this issue. Please upgrade to the version and have a try.
Description
java.lang.NoClassDefFoundError: Failed resolution of: Lcom/google/android/aidl/BaseStub;
at com.android.installreferrer.api.InstallReferrerClientImpl.startConnection(InstallReferrerClientImpl.java:133)
It does this immediately after my app calls `referralClient.startConnection(this)`
Using v1.0 of the library works fine. Upgrading to v1.1 immediately causes issues for my app, and is unusable.