fix: lock iOS and Android SDK dependencies to specific versions #284
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Problem
Users reported
NoSuchMethodErrorcrashes when initializing Amplitude (#283). The error occurred due to Gradle resolving different versions ofanalytics-androidat compile-time vs runtime.Root Cause
The dependency was specified as a version range
[1.22,2.0). When Android SDK v1.22.4 added a new constructor parameter toConfiguration, it created a binary incompatibility. Kotlin's default parameter handling generates specific bytecode signatures that don't match when the constructor signature changes.Two scenarios can cause the crash:
1. Dependency Conflict Resolution:
2. Gradle Lockfile + Incremental Build:
Solution
Lock Android SDK to specific version
1.22.4to ensure compile-time and runtime use the same version.Changes
android/build.gradle:analytics-android:[1.22,2.0)→analytics-android:1.22.4Testing
Closes #283