Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

3.3.0 is binary-incompatible with 3.2.0

See original GitHub issue

✍️ Describe the bug

I have a project that uses Chucker, which also uses a library that uses Chucker. The library is still using 3.2.0, and when I updated my app to 3.3.0 and ran it, it crashed at runtime with this error:

java.lang.NoSuchMethodError: No direct method <init>(Landroid/content/Context;Lcom/chuckerteam/chucker/api/ChuckerCollector;JLjava/util/Set;ILkotlin/jvm/internal/DefaultConstructorMarker;)V in class Lcom/chuckerteam/chucker/api/ChuckerInterceptor; or its super classes (declaration of 'com.chuckerteam.chucker.api.ChuckerInterceptor' appears in /data/app/~~GJiF7AJl427rbyfaLOyo1A==/com.myproject-GIw2-OO7zIRGQFD6KsWDQg==/base.apk)

According to @cortinico,

Seems like the ChuckerInterceptor(Context, ChuckerCollector, Set) is missing.

💣 Steps to reproduce

Have a library with Chucker 3.2.0.
Have an app with Chucker 3.3.0, and which uses the above library.
Launch app.
Observe crash.

🔧 Expected behavior

App should not crash.

📄 Additional context

Adding the missing constructor will make it easier to migrate to Chucker 3.3.0.

Issue Analytics

State:
Created 3 years ago
Comments:7 (3 by maintainers)

Top GitHub Comments

1reaction

vbuberencommented, Feb 15, 2021

Looks like we can close this one thanks to #509

1reaction

autonomousappscommented, Oct 2, 2020

Btw, I haven’t formalized it yet, but it would be possible to use my plugin to get a snapshot of your ABI at any given moment, and you could use that to compare across versions. You’d run ./gradlew :lib:abiAnalysisDebug and then look at the output at build/reports/dependency-analysis/debug/intermediates/abi-dump.txt. I plan to make this easier in the future. If you do try this, let me know how it goes, as having a real use-case to discuss would make it easier to build out the feature fully.

Top Results From Across the Web

spacy.strings.StringStore size changed, may indicate binary ...

StringStore size changed, may indicate binary incompatibility. Expected 80 from C header, got 64 from PyObject #310.

ABI Policy and Guidelines - GCC, the GNU Compiler Collection

These details are defined as the compiler Application Binary Interface, or ABI. ... GCC 3.2.0: libstdc++.so.5.0.0 (Incompatible with previous).

Apache Spark 3 and backward compatibility? - Stack Overflow

There are some breaking changes in Spark 3.0.0, including source incompatible change and binary incompatible changes.

Scala is a Maintenance Nightmare - MungingData

This post explains why it's so hard to maintain Scala projects (binary incombatilbilities, frequent breaking changes, SBT plugins, ...

Installation — PySpark 3.3.1 documentation - Apache Spark

cd spark-3.3.0-bin-hadoop3 export SPARK_HOME=`pwd` export PYTHONPATH=$(ZIPS=("$SPARK_HOME"/python/lib/*.zip); IFS=:; echo "${ZIPS[*]}"):$PYTHONPATH ...