Bump the dependencies group across 1 directory with 18 updates

[dependabot]

Bumps the dependencies group with 11 updates in the / directory:

Package	From	To
com.android.tools.build:gradle	8.13.1	9.1.0
org.jetbrains.kotlin:kotlin-gradle-plugin	2.2.21	2.3.20
androidx.navigation:navigation-safe-args-gradle-plugin	2.9.6	2.9.7
com.google.dagger:hilt-android-gradle-plugin	2.57.2	2.59.2
com.google.dagger:dagger	2.57.2	2.59.2
androidx.activity:activity-ktx	1.12.4	1.13.0
androidx.compose:compose-bom	2026.02.00	2026.03.01
androidx.media3:media3-exoplayer	1.9.2	1.10.0
androidx.core:core-ktx	1.17.0	1.18.0
org.jetbrains.kotlin.plugin.compose	2.2.21	2.3.20
gradle-wrapper	8.13	9.4.1

Updates com.android.tools.build:gradle from 8.13.1 to 9.1.0

Updates org.jetbrains.kotlin:kotlin-gradle-plugin from 2.2.21 to 2.3.20

Release notes

Sourced from org.jetbrains.kotlin:kotlin-gradle-plugin's releases.

Kotlin 2.3.20

Changelog

Analysis API. FIR

New Features

• KT-78090 Implement stubs support for new conditional returns and holdsIn contracts

Fixes

• KT-82948 'FirRegularClass' expected as a containing declaration, got 'FirTypeAliasImpl'
• KT-83467 Package-level JSpecify annotations are ignored when coming from jars or libraries
• KT-82057 K2. Cannot infer type parameter 'R' in Ktor routing post() function with explicit response type
• KT-82846 AA: unresolved KtExpression.expressionType for the reference to the parameter with default value
• KT-80485 False positive UNRESOLVED_REFERENCE on nested interface from super-super class in the super type position inside an anonymous object
• KT-82772 Flaky false positive deprecation warning on PersistentMap.put in Kotlin repo in IDE mode
• KT-76487 StdLibSourcesLazyDeclarationResolveTestGenerated.testWrappedInt is unstable
• KT-82618 Various tests are failing with NPE in kt-master after updating the compiler on 19.11.25
• KT-82076 Error querying members of JavaClass created for SymbolLightClassForAnnotationClass during library analysis
• KT-71596 Include Js/Wasi checkers in AbstractLLFirDiagnosticsCollector
• KT-82085 No OUTER_CLASS_ARGUMENTS_REQUIRED on type parameter bound in IDE
• KT-81873 Provide a way of including traces in phase JFR events
• KT-71929 Consider leaving the non-post-compute version at EnhancementSymbolsCache.enhancedFunctions

Analysis API. Infrastructure

• KT-83173 Analysis API Tests: Library names with RC versions aren't sanitised
• KT-65140 LL FIR: Implement AbstractFirPsiJsDiagnosticTest for LL FIR
• KT-82212 [Analysis API, LL FIR] Implement AbstractDiagnosticsFirWasmTest and AbstractDiagnosticsFirWasmWasiTest for LL FIR

Analysis API. Light Classes

• KT-82227 Value classes should expose regular static methods

Analysis API. PSI

• KT-81710 'KtTypeReference.getTypeText' does not account for 'suspend' modifier on suspend lambdas
• KT-82258 Prepare PSI for migration from context receivers to context parameters
• KT-81074 KDoc: List rendering is broken

Analysis API. Providers and Caches

• KT-82449 K2 IDE Analysis Freezes During Gradle Sync (Recursive Module Dependency Computation in KotlinModuleDependentsProviderBase.computeTransitiveDependents)
• KT-82629 'collectDiagnostics' returns stale syntax error after editor fix
• KT-74907 Analysis API: Apply platform-based library module content restrictions consistently

Analysis API. Standalone

• KT-81107 AA: KtSourceModuleBuilder.sourceRoots doesn't works with symbolic links

... (truncated)

Changelog

Sourced from org.jetbrains.kotlin:kotlin-gradle-plugin's changelog.

2.3.20

Analysis API. FIR

New Features

• KT-78090 Implement stubs support for new conditional returns and holdsIn contracts

Fixes

• KT-82948 'FirRegularClass' expected as a containing declaration, got 'FirTypeAliasImpl'
• KT-83467 Package-level JSpecify annotations are ignored when coming from jars or libraries
• KT-82057 K2. Cannot infer type parameter 'R' in Ktor routing post() function with explicit response type
• KT-82846 AA: unresolved KtExpression.expressionType for the reference to the parameter with default value
• KT-80485 False positive UNRESOLVED_REFERENCE on nested interface from super-super class in the super type position inside an anonymous object
• KT-82772 Flaky false positive deprecation warning on PersistentMap.put in Kotlin repo in IDE mode
• KT-76487 StdLibSourcesLazyDeclarationResolveTestGenerated.testWrappedInt is unstable
• KT-82618 Various tests are failing with NPE in kt-master after updating the compiler on 19.11.25
• KT-82076 Error querying members of JavaClass created for SymbolLightClassForAnnotationClass during library analysis
• KT-71596 Include Js/Wasi checkers in AbstractLLFirDiagnosticsCollector
• KT-82085 No OUTER_CLASS_ARGUMENTS_REQUIRED on type parameter bound in IDE
• KT-81873 Provide a way of including traces in phase JFR events
• KT-71929 Consider leaving the non-post-compute version at EnhancementSymbolsCache.enhancedFunctions

Analysis API. Infrastructure

• KT-83173 Analysis API Tests: Library names with RC versions aren't sanitised
• KT-65140 LL FIR: Implement AbstractFirPsiJsDiagnosticTest for LL FIR
• KT-82212 [Analysis API, LL FIR] Implement AbstractDiagnosticsFirWasmTest and AbstractDiagnosticsFirWasmWasiTest for LL FIR

Analysis API. Light Classes

• KT-82227 Value classes should expose regular static methods

Analysis API. PSI

• KT-81710 'KtTypeReference.getTypeText' does not account for 'suspend' modifier on suspend lambdas
• KT-82258 Prepare PSI for migration from context receivers to context parameters
• KT-81074 KDoc: List rendering is broken

Analysis API. Providers and Caches

• KT-82449 K2 IDE Analysis Freezes During Gradle Sync (Recursive Module Dependency Computation in KotlinModuleDependentsProviderBase.computeTransitiveDependents)
• KT-82629 'collectDiagnostics' returns stale syntax error after editor fix
• KT-74907 Analysis API: Apply platform-based library module content restrictions consistently

Analysis API. Standalone

• KT-81107 AA: KtSourceModuleBuilder.sourceRoots doesn't works with symbolic links

... (truncated)

Commits

• d57eb4a Add ChangeLog for 2.3.20-RC3
• 41886bb [Gradle] Update KGP npm tooling dependency versions
• 210a9bd [Native] Do not mark iosX64 target as deprecate in DSL
• 7ed446e Add ChangeLog for 2.3.20-RC2
• 520eade [K/JVM] Fix incorrect optimization of local delegation
• 7ef8bcc Reflection: add LazyKProperty to fix recent performance regression
• 9fa7cf2 [Gradle] Link NoActiveThreadsAfterCompilerInvocationIT with KT-84566
• d410596 [Gradle] Shutdown coroutines dispatcher threads after compiler invocation
• 348430b [BTA] Fix compatibility between API 2.3.20 and KC 2.3.10
• 4058f3c [CMP] HiddenFromObjC remove outdated offset check
• Additional commits viewable in compare view

Updates androidx.navigation:navigation-safe-args-gradle-plugin from 2.9.6 to 2.9.7

Updates com.google.dagger:hilt-android-gradle-plugin from 2.57.2 to 2.59.2

Release notes

Sourced from com.google.dagger:hilt-android-gradle-plugin's releases.

Dagger 2.59.2

Bug fixes:

• Fixed #5116,#5099: Replaced Hilt's "android-classes" transform with attribute rules (f7e31b857)
• Fixed #5122: Fixed issue with slow incremental builds introduced by HiltSyncTask in AGP 9 support (1be57655b)

Dagger 2.59.1

Bug fixes:

• Fixed #5099: Fixes compilation error with jetifierEnabled=true in AGP 9 (8dcce8790)
• Fixed #5098: Updated minimum required AGP version to 9.0.0 to make it clearer this is a requirement when using the Hilt Gradle plugin. (141e5941a)

Dagger 2.59

Breaking changes:

(If you do not use Hilt or the Hilt Gradle plugin, this change does not affect you.)

This release adds AGP 9 support for the Hilt Gradle plugin. This means that if you use the Hilt Gradle Plugin, AGP 9 is now a requirement along with AGP 9’s own requirements like Gradle 9.1+ (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Note: AGP 9 also seems to cause issues with enableJetifier=true (see #5099). This will be fixed in a follow-up release.

Bug fixes/features:

• Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

Commits

• 118f2e5 2.59.2 release
• 1be5765 Change HiltSyncTask to extend DefaultTask instead of Sync.
• f7e31b8 Replace Hilt's "android-classes" transform with attribute rules.
• 5909005 Automated Code Change
• 3507b0d Support nullability in Switching Providers
• 1900560 Internal changes
• 8c69595 Update Dagger yml and README with new latest version number.
• 1dbb1dd Internal refactoring
• 62b5423 Internal changes
• 8dcce87 Add AggregatedPackagesTransform for "android-classes" artifact type.
• Additional commits viewable in compare view

Updates com.google.dagger:dagger from 2.57.2 to 2.59.2

Release notes

Sourced from com.google.dagger:dagger's releases.

Dagger 2.59.2

Bug fixes:

• Fixed #5116,#5099: Replaced Hilt's "android-classes" transform with attribute rules (f7e31b857)
• Fixed #5122: Fixed issue with slow incremental builds introduced by HiltSyncTask in AGP 9 support (1be57655b)

Dagger 2.59.1

Bug fixes:

• Fixed #5099: Fixes compilation error with jetifierEnabled=true in AGP 9 (8dcce8790)
• Fixed #5098: Updated minimum required AGP version to 9.0.0 to make it clearer this is a requirement when using the Hilt Gradle plugin. (141e5941a)

Dagger 2.59

Breaking changes:

(If you do not use Hilt or the Hilt Gradle plugin, this change does not affect you.)

This release adds AGP 9 support for the Hilt Gradle plugin. This means that if you use the Hilt Gradle Plugin, AGP 9 is now a requirement along with AGP 9’s own requirements like Gradle 9.1+ (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Note: AGP 9 also seems to cause issues with enableJetifier=true (see #5099). This will be fixed in a follow-up release.

Bug fixes/features:

• Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

Commits

• 118f2e5 2.59.2 release
• 1be5765 Change HiltSyncTask to extend DefaultTask instead of Sync.
• f7e31b8 Replace Hilt's "android-classes" transform with attribute rules.
• 5909005 Automated Code Change
• 3507b0d Support nullability in Switching Providers
• 1900560 Internal changes
• 8c69595 Update Dagger yml and README with new latest version number.
• 1dbb1dd Internal refactoring
• 62b5423 Internal changes
• 8dcce87 Add AggregatedPackagesTransform for "android-classes" artifact type.
• Additional commits viewable in compare view

Updates com.google.dagger:dagger-compiler from 2.57.2 to 2.59.2

Release notes

Sourced from com.google.dagger:dagger-compiler's releases.

Dagger 2.59.2

Bug fixes:

• Fixed #5116,#5099: Replaced Hilt's "android-classes" transform with attribute rules (f7e31b857)
• Fixed #5122: Fixed issue with slow incremental builds introduced by HiltSyncTask in AGP 9 support (1be57655b)

Dagger 2.59.1

Bug fixes:

• Fixed #5099: Fixes compilation error with jetifierEnabled=true in AGP 9 (8dcce8790)
• Fixed #5098: Updated minimum required AGP version to 9.0.0 to make it clearer this is a requirement when using the Hilt Gradle plugin. (141e5941a)

Dagger 2.59

Breaking changes:

(If you do not use Hilt or the Hilt Gradle plugin, this change does not affect you.)

This release adds AGP 9 support for the Hilt Gradle plugin. This means that if you use the Hilt Gradle Plugin, AGP 9 is now a requirement along with AGP 9’s own requirements like Gradle 9.1+ (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Note: AGP 9 also seems to cause issues with enableJetifier=true (see #5099). This will be fixed in a follow-up release.

Bug fixes/features:

• Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

Commits

• 118f2e5 2.59.2 release
• 1be5765 Change HiltSyncTask to extend DefaultTask instead of Sync.
• f7e31b8 Replace Hilt's "android-classes" transform with attribute rules.
• 5909005 Automated Code Change
• 3507b0d Support nullability in Switching Providers
• 1900560 Internal changes
• 8c69595 Update Dagger yml and README with new latest version number.
• 1dbb1dd Internal refactoring
• 62b5423 Internal changes
• 8dcce87 Add AggregatedPackagesTransform for "android-classes" artifact type.
• Additional commits viewable in compare view

Updates com.google.dagger:hilt-android from 2.57.2 to 2.59.2

Release notes

Sourced from com.google.dagger:hilt-android's releases.

Dagger 2.59.2

Bug fixes:

• Fixed #5116,#5099: Replaced Hilt's "android-classes" transform with attribute rules (f7e31b857)
• Fixed #5122: Fixed issue with slow incremental builds introduced by HiltSyncTask in AGP 9 support (1be57655b)

Dagger 2.59.1

Bug fixes:

• Fixed #5099: Fixes compilation error with jetifierEnabled=true in AGP 9 (8dcce8790)
• Fixed #5098: Updated minimum required AGP version to 9.0.0 to make it clearer this is a requirement when using the Hilt Gradle plugin. (141e5941a)

Dagger 2.59

Breaking changes:

(If you do not use Hilt or the Hilt Gradle plugin, this change does not affect you.)

This release adds AGP 9 support for the Hilt Gradle plugin. This means that if you use the Hilt Gradle Plugin, AGP 9 is now a requirement along with AGP 9’s own requirements like Gradle 9.1+ (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Note: AGP 9 also seems to cause issues with enableJetifier=true (see #5099). This will be fixed in a follow-up release.

Bug fixes/features:

• Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

Commits

• 118f2e5 2.59.2 release
• 1be5765 Change HiltSyncTask to extend DefaultTask instead of Sync.
• f7e31b8 Replace Hilt's "android-classes" transform with attribute rules.
• 5909005 Automated Code Change
• 3507b0d Support nullability in Switching Providers
• 1900560 Internal changes
• 8c69595 Update Dagger yml and README with new latest version number.
• 1dbb1dd Internal refactoring
• 62b5423 Internal changes
• 8dcce87 Add AggregatedPackagesTransform for "android-classes" artifact type.
• Additional commits viewable in compare view

Updates com.google.dagger:hilt-android-compiler from 2.57.2 to 2.59.2

Release notes

Sourced from com.google.dagger:hilt-android-compiler's releases.

Dagger 2.59.2

Bug fixes:

• Fixed #5116,#5099: Replaced Hilt's "android-classes" transform with attribute rules (f7e31b857)
• Fixed #5122: Fixed issue with slow incremental builds introduced by HiltSyncTask in AGP 9 support (1be57655b)

Dagger 2.59.1

Bug fixes:

• Fixed #5099: Fixes compilation error with jetifierEnabled=true in AGP 9 (8dcce8790)
• Fixed #5098: Updated minimum required AGP version to 9.0.0 to make it clearer this is a requirement when using the Hilt Gradle plugin. (141e5941a)

Dagger 2.59

Breaking changes:

(If you do not use Hilt or the Hilt Gradle plugin, this change does not affect you.)

This release adds AGP 9 support for the Hilt Gradle plugin. This means that if you use the Hilt Gradle Plugin, AGP 9 is now a requirement along with AGP 9’s own requirements like Gradle 9.1+ (https://developer.android.com/build/releases/agp-9-0-0-release-notes).

Note: AGP 9 also seems to cause issues with enableJetifier=true (see #5099). This will be fixed in a follow-up release.

Bug fixes/features:

• Fixed #4944, #4979: Support AGP 9 in HiltGradlePlugin (6afd7ea5a0fb84a38f2d23c990ddbd95e728a39d)

Dagger 2.58

Note: AGP 9 support was held back from this release (google/dagger#5061) because it forces users onto AGP 9. It will be available in the next Dagger release (e92e3f392).

Potential breaking changes:

• Flipped default for dagger.useBindingGraphFix to enabled (d41e8362b). See https://dagger.dev/dev-guide/compiler-options#useBindingGraphFix. Fix: If this change breaks you it’s likely due to providing a binding in an incorrect module, (e.g. the binding requests an Activity but is installed in the SingletonComponent). The fix is to move the @Provides so that it is installed into the correct component (e.g. the ActivityComponent instead of SingletonComponent). You can also set dagger.useBindingGraphFix=disabled but note that this flag is only temporary and will eventually be removed.
• The use of abstract var in components is now banned in super types. The reason for this change is that an abstract var property creates both a getter and a setter on the component which is almost always unintentional. Fix: If this change breaks you, use either an abstract val foo: Foo if you need a getter or abstract fun inject(foo: Foo) if you need an inject method. Note that abstract var is already banned if it is declared directly on the @Component class/interface, but this change fixes the check so that it’s banned even if it’s inherited from a super type.

Bug fixes/features:

• Fixes #1116, #1630, Supported Map<K, Lazy<V>> as a multibinding request type. (7f981a4c3)
• Fixes #3601. No longer adds a deprecation warning for unused dependencies on setters on the component builder. (1cf9dfc96)
• Fixes #4982:
  • Added validation to prevent using Java keywords in Dagger-generated code (72e21a828)
  • Added error for binding elements names that are Java keywords. (38071c5ae)
  • Java keyword validation is now performed earlier during the superficial validation stage. (7f6f7bda7)

Commits

• 118f2e5 2.59.2 release
• 1be5765 Change HiltSyncTask to extend DefaultTask instead of Sync.
• f7e31b8 Replace Hilt's "android-classes" transform with attribute rules.
• 5909005 Automated Code Change
• 3507b0d Support nullability in Switching Providers
• 1900560 Internal changes
• 8c69595 Update Dagger yml and README with new latest version number.
• 1dbb1dd Internal refactoring
• 62b5423 Internal changes
• 8dcce87 Add AggregatedPackagesTransform for "android-classes" artifact type.
• Additional commits viewable in compare view

Updates androidx.activity:activity-ktx from 1.12.4 to 1.13.0

Updates androidx.compose:compose-bom from 2026.02.00 to 2026.03.01

Updates androidx.media3:media3-exoplayer from 1.9.2 to 1.10.0

Release notes

Sourced from androidx.media3:media3-exoplayer's releases.

1.10.0

• Common library:
  • Promote Player.mute() and Player.unmute() from UnstableApi to stable.
  • Promote Format.pcmEncoding and C.PcmEncoding from UnstableApi to stable.
  • Add Format.primaryTrackGroupId to identify the primary group of embedded Format instances (#294).
• ExoPlayer:
  • Add clipping capabilities to AdsMediaSource.
  • Add support for dynamic scheduling in MediaCodecVideoRenderer to better align scheduling work and CPU wake-cycles to when video frames can be processed. You can enable this using experimentalSetEnableMediaCodecVideoRendererDurationToProgressUs() in the DefaultRenderersFactory.
  • Allow setting a custom DataSource.Factory in DefaultPreloadManager.Builder.
  • Allow ExoPlayer to be mocked without Robolectric by moving some default constants to ExoPlayer.Builder. Mocking this complex interface is not generally encouraged - only when the usage is minimal/simple/incidental (#2985).
    • This required moving DEFAULT_STUCK_PLAYING_DETECTION_TIMEOUT_MS from ExoPlayer to ExoPlayer.Builder (without deprecation).
  • Fix a bug where ProgressiveMediaSource propagates out-of-date timeline info to the player, and the queued periods unexpectedly get removed (#3016).
  • Fix issue where ExoPlayer would not request delayed audio focus when playback is requested during phone calls.
  • Fix bug where transitions from on-demand to live content may cause re-buffers at the end of the on-demand content (#3052).
  • Add support for Dolby Vision Profile 10 (#2830).
  • Fix bug where an uninitialized pre roll ad produced an ArrayIndexOutOfBoundsException (#3125).
• CompositionPlayer:
  • Add support for EditedMediaItem.removeVideo.
• Transformer:
  • EditedMediaItem.Builder.setFrameRate() can now set a maximum output frame rate for video, which is particularly helpful when increasing media speed with setSpeed().
• Track selection:
  • Change signature of DefaultTrackSelector.selectAllTracks to include the output array as a parameter, pre-populated with track overrides.
  • Fix issue where embedded metadata tracks are selected irrespective of whether the corresponding primary track is selected (#294).
  • Stabilize TrackSelectionParameters options for preferredVideoLanguages, preferredVideoLabels, preferredAudioLabels, preferredTextLabels and selectTextByDefault.
• Extractors:
  • MP4: Support files with large uuid boxes before other boxes like moov (#3046).
  • MP4: Add support for Versatile Video Coding (VVC) tracks in MP4 containers.
• Inspector:
  • Breaking change: remove FrameExtractor. Users should now depend on the new :media3-inspector-frame module and update imports to androidx.media3.inspector.frame.FrameExtractor.
  • Introduce a new module for extracting and processing decoded video frames.
• Audio:
  • Change underlying decoding library for the IAMF decoder extension from libiamf to iamf_tools.
  • IAMF decoding supports binaural output either through the decoder (when using the IAMF decoder extension) or through the Android Spatializer.
  • Correctly remove support for AC4Profile22 and other legacy profiles when assessing AC-4 decoder support in Automotive scenarios (#2609).
  • Improve the retry logic of AudioOutput initialization in DefaultAudioSink (#2905).
  • Improve the retry logic of AudioOutput initialization in DefaultAudioSink (#2905).
  • Attempt to match the output layout of the speakers (or Spatializer if applicable) when decoding IAMF, both with the IAMF extension and media codec decoders, supported by new fields and logic in AudioCapabilities and AudioCapabilitiesReceiver.
  • Fix bug where playback gets stuck when playing a playlist of gapless audio in compressed offload mode.
• Text:
  • VobSub: Use START and STOP SPU control commands to derive cue duration instead of always defaulting to 5 seconds (#2935).
• Metadata:
  • Increase default count of metadata renderers to four to cover all potential metadata tracks published by HLS variants and renditions (#3043).
• Effect:
  • Move LottieOverlay to a new :media3-effect-lottie module (which also involved renaming it from androidx.media3.effect.LottieOverlay to androidx.media3.effect.lottie.LottieOverlay).
• Effect Lottie:
  • Introduce a new :media3-effect-lottie module which provides functionality for applying lottie effects to video frames.
• IMA extension:
  • Update the IMA SDK version to 3.39.0 in order to have access to the latest Ad media info API.
  • Fix a bug where the ad MIME type did not match the MIME type provided in the IMA LOADED event. The fix now maps the ad MIME type using the ad media info provided by IMA.
  • Add setEnableCustomTabs to ImaAdsLoader and ImaServerSideAdInsertionMediaSource, allowing users to control whether ad click-through URLs are launched using Custom Tabs.

... (truncated)

Changelog

Sourced from androidx.media3:media3-exoplayer's changelog.

1.10.0 (2026-03-25)

This release includes the following changes since 1.9.1 release:

• Common library:
  • Promote Player.mute() and Player.unmute() from UnstableApi to stable.
  • Promote Format.pcmEncoding and C.PcmEncoding from UnstableApi to stable.
  • Add Format.primaryTrackGroupId to identify the primary group of embedded Format instances (#294).
• ExoPlayer:
  • Add clipping capabilities to AdsMediaSource.
  • Add support for dynamic scheduling in MediaCodecVideoRenderer to better align scheduling work and CPU wake-cycles to when video frames can be processed. You can enable this using experimentalSetEnableMediaCodecVideoRendererDurationToProgressUs() in the DefaultRenderersFactory.
  • Allow setting a custom DataSource.Factory in DefaultPreloadManager.Builder.
  • Allow ExoPlayer to be mocked without Robolectric by moving some default constants to ExoPlayer.Builder. Mocking this complex interface is not generally encouraged - only when the usage is minimal/simple/incidental (#2985).
    • This required moving DEFAULT_STUCK_PLAYING_DETECTION_TIMEOUT_MS from ExoPlayer to ExoPlayer.Builder (without deprecation).
  • Fix a bug where ProgressiveMediaSource propagates out-of-date timeline info to the player, and the queued periods unexpectedly get removed (#3016).
  • Fix issue where ExoPlayer would not request delayed audio focus when playback is requested during phone calls.
  • Fix bug where transitions from on-demand to live content may cause re-buffers at the end of the on-demand content (#3052).
  • Add support for Dolby Vision Profile 10 (#2830).
  • Fix bug where an uninitialized pre roll ad produced an ArrayIndexOutOfBoundsException (#3125).
• CompositionPlayer:
  • Add support for EditedMediaItem.removeVideo.
• Transformer:
  • EditedMediaItem.Builder.setFrameRate() can now set a maximum output frame rate for video, which is particularly helpful when increasing media speed with setSpeed().
• Track selection:
  • Change signature of DefaultTrackSelector.selectAllTracks to include

... (truncated)

Commits

• 7ce3aa2 Merge branch 'release' into release-1.10.0
• 9a86cf8 Update release notes for 1.10.0
• 3517ef9 Update version number for 1.10.0 release
• 5c43a67 Bump version to media3:1.10.0-rc03
• 6d157a4 Update release notes for 1.10.0-rc03
• 16356f8 Fix regression in RTSP H264/H265 caused by incorrect sample size resets
• ba1a742 Fix ArrayIndexOutOfBoundsIndexException with unavailable preroll
• f734434 Fix SysUI crash/device reboot issue on API 29 for specific bitmap size
• 82ea60d HlsMediaPeriod: Generate StreamKeys for all streams in redundant group
• 9b8b13d Merge branch 'release' into release-1.9.3
• Additional commits viewable in compare view

Updates androidx.media3:media3-ui from 1.9.2 to 1.10.0

Updates androidx.media3:media3-ui-compose from 1.9.2 to 1.10.0

Updates androidx.media3:media3-ui-compose-material3 from 1.9.2 to 1.10.0

Updates androidx.core:core-ktx from 1.17.0 to 1.18.0

Updates androidx.activity:activity from 1.12.4 to 1.13.0

Updates org.jetbrains.kotlin.plugin.compose from 2.2.21 to 2.3.20

Release notes

Sourced from org.jetbrains.kotlin.plugin.compose's releases.

Kotlin 2.3.20

Changelog

Analysis API. FIR

New Features

• KT-78090 Implement stubs support for new conditional returns and holdsIn contracts

Fixes

• KT-82948 'FirRegularClass' expected as a containing declaration, got 'FirTypeAliasImpl'
• KT-83467 Package-level JSpecify annotations are ignored when coming from jars or libraries
• KT-82057 K2. Cannot infer type parameter 'R' in Ktor routing post() function with explicit response type
• KT-82846 AA: unresolved KtExpression.expressionType for the reference to the parameter with default value
• KT-80485 False positive UNRESOLVED_REFERENCE on nested interface from super-super class in the super type position inside an anonymous object
• KT-82772 Flaky false positive deprecation warning on PersistentMap.put in Kotlin repo in IDE mode
• KT-76487 StdLibSourcesLazyDeclarationResolveTestGenerated.testWrappedInt is unstable
• KT-82618 Various tests are failing with NPE in kt-master after updating the compiler on 19.11.25
• KT-82076 Error querying members of JavaClass created for SymbolLightClassForAnnotationClass during library analysis
• KT-71596 Include Js/Wasi checkers in AbstractLLFirDiagnosticsCollector
• KT-82085 No OUTER_CLASS_ARGUMENTS_REQUIRED on type parameter bound in IDE
• KT-81873 Provide a way of including traces in phase JFR events
• KT-71929 Consider leaving the non-post-compute version at EnhancementSymbolsCache.enhancedFunctions

Analysis API. Infrastructure

• KT-83173 Analysis API Tests: Library names with RC versions aren't sanitised
• KT-65140 LL FIR: Implement AbstractFirPsiJsDiagnosticTest for LL FIR
• KT-82212 [Analysis API, LL FIR] Implement AbstractDiagnosticsFirWasmTest and AbstractDiagnosticsFirWasmWasiTest for LL FIR

Analysis API. Light Classes

• KT-82227 Value classes should expose regular static methods

Analysis API. PSI

• KT-81710 'KtTypeReference.getTypeText' does not account for 'suspend' modifier on suspend lambdas
• KT-82258 Prepare PSI for migration from context receivers to context parameters
• KT-81074 KDoc: List rendering is broken

Analysis API. Providers and Caches

• KT-82449 K2 IDE Analysis Freezes During Gradle Sync (Recursive Module Dependency Computation in KotlinModuleDependentsProviderBase.computeTransitiveDependents)
• KT-82629 'collectDiagnostics' returns stale syntax error after editor fix
• KT-74907 Analysis API: Apply platform-based library module content restrictions consistently

Analysis API. Standalone

• KT-81107 AA: KtSourceModuleBuilder.sourceRoots doesn't works with symbolic links

... (truncated)

Changelog

Sourced from org.jetbrains.kotlin.plugin.compose's changelog.

2.3.20

Analysis API. FIR

...

Description has been truncated