Bump hilt-android from 2.39.1 to 2.43.2

[dependabot]

Bumps hilt-android from 2.39.1 to 2.43.2.

Release notes

Sourced from hilt-android's releases.

Dagger 2.43.2

What’s New In Dagger

Bug Fixes

• Fixes #3495: Updates the XProcessing jars, which should again be compatible with java 8. (62b7f4592)
• Adds support reading metadata from Kotlin 1.8 by updating kotlin-metadata-jvm to 5.0. (353a50b1e)
• Fixes an issue where the Hilt Gradle Plugin artifact was being bloated with additional classes causing its size to be way bigger than its suppose to be. (8235bebe9)

Dagger 2.43.1

What’s New In Dagger

Bug Fixes

• Fixes #3480. Replace dependency on javax.annotation:jsr250-api:1.0 with javax.annotation:javax.annotation-api:1.3.2. (e9dc377d1)
• Fixes #3483: Add onPluginEnd to BindingGraphPlugin, which will be called after all BindingGraphPlugins have been visited (34452751e)
• Fixes #3476: Fix issue with Dagger generating mismatching parameter names in component inject functions. (90300d992)

Dagger 2.43

What’s New In Dagger

Potentially Breaking Changes

• Note: Dagger 2.43/2.43.1 require java 11 due to a change in Dagger's XProcessing dependency. However, this requirement has been recently reverted in XProcessing and Dagger 2.43.2 should support java 8 again (see [issue #3495](google/dagger#3495)).

Bug Fixes

• Fixes #3401 where Dagger generated mismatched parameter names in subcomponent factory method implementations when the original factory method is in a separate build unit from the component that implements it.

What’s New In Hilt

Potentially Breaking Changes

• Hilt now throws if the base activity/fragment class’s getDefaultViewModelProviderFactory() returns null. This is unlikely to happen though unless overridden by the user to return null. (9eee8e47f)
• As part ViewModel bug fixes, dependencies were updated as below. androidx.navigation users will need to update to 2.5.0 to interoperate. These libraries require building with SDK 31. To build with SDK 31, AGP users will need to use AGP 7.0+. This will also require using JDK11.
  • androidx.activity and androidx.fragment to 1.5.0
  • androidx.lifecycle to 2.5.0
  • androidx.savedstate to 1.2.0

Bug Fixes

• Fix #3464 where SPI plugins were not being invoked with Hilt's Gradle Plugin aggregation (enableAggregatingTask) turned on. (b83887624)
• Fixes #2328 and #3232 where getting multiple instances of @HiltViewModel with different keys would cause a crash.
• Fixes #2152. hiltNavGraphViewModels is now no longer necessary to use @HiltViewModel with navigation backstack entries as the owner. The default ViewModelProvider.Factory from activities and fragments can be used directly with the backstack entry as the owner. (74ea7653a)
• Make it so that map keys used with @BindValueIntoMap in Kotlin code do not need to use the @field notation. (e59183324)

Dagger 2.42

What’s new in Dagger

Potentially breaking changes

As of this release, Dagger’s generated class will no longer extend the user-defined @Component annotated class (885b16dcf). This change was done to improve build times in certain scenarios by avoiding a known javac bottleneck. However, it may also be a breaking change for some users. For example

</tr></table> 

... (truncated)

Commits

• 21617b7 2.43.2 release
• 8235beb Don't shadow transitive dependencies of the :agp-wrapper-* projects.
• 62b7f45 Update XProcessing jars.
• 353a50b Update kotlin-metadata-jvm to 5.0 which support reading metadata from upcomin...
• 12b385b Update to Kotlin 1.7.0 in the Hilt Gradle Plugin project.
• ab008dd Update Dagger yml and README with new latest version number.
• e9dc377 Replace dependency on javax.annotation:jsr250-api:1.0 with javax.annotation:j...
• b9413ba Rollback of google/dagger@2cce0be5e8d32ffd0cb0d7359...
• 2cce0be Migrate to the new JavaPoetExtKt#toAnnotationSpec(XAnnotation) API in XProc...
• 56335c1 Migrate dagger.spi.model.Key.MultibindingContributionIdentifier to use XPro...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #332.