fix(android): set the Kotlin jvmTarget without requiring the Kotlin G… - #3799
Merged
Conversation
Contributor
SDK Size
|
oliverlaz
approved these changes
Sep 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Follow-up to #3798. That change stops applying
kotlin-androidwhen AGP has alreadyregistered the
kotlinextension, which is what AGP 9 does by default. Butandroid.kotlinOptionsis contributed by the Kotlin Gradle plugin itself, so skipping theplugin left both wrapper modules unable to configure at all:
Set the target on the KotlinCompile tasks instead. That form resolves on both paths.
A note for integrators: the
android.builtInKotlin=falseis still necessary because the SDK has peer dependencies that require this setting.