question-mark
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.

Update to 2.40.1 from 2.40 breaks build

See original GitHub issue

I have a hilt @Entrypoint and other dagger components that depend on it and the code is working in 2.40 but not in 2.40.1. Code example similar to my code: In 1st Gradle module with hilt dependencies:

@EntryPoint
@InstallIn(SingletonComponent::class)
interface SomeComponent {

    fun exposeContext(): Context

    fun exposeApplication(): Application
}

In 2nd Gradle module with dagger dependencies(not hilt):

@CoreScope
@Component(
    modules = [
        CoreInjectionModule::class,
        AndroidInjectionModule::class,
        DatabaseModule::class,
        CoreViewModelModule::class,
        CoreServicesModule::class,
        CoreBroadcastModule::class,
        CoreWorkerModule::class
    ],
    dependencies = [GiantComponent::class, SomeComponent::class]
)
interface CoreComponent : ExposeCoreDependencies, ExposeComponent, WorkerComponent {

    @CoreInjector
    override fun dispatcher(): BaseModuleAndroidInjector<Any>

    @CoreInjector
    override fun workers(): WorkerProviders
}

(Because I am between a migration from dagger I can not use hilt in all Gradle modules) The build has this error: CoreComponent can not resolve all of its dependencies or have cyclic dependency… I fixed it by reversing the hilt and dagger to 2.40 for now.

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Reactions:4
  • Comments:13

github_iconTop GitHub Comments

4reactions
bcorsocommented, Dec 9, 2021

@gmazzo, yeah we’ve been having plans to improve this error message for a while https://github.com/google/dagger/issues/2208.

Due to the increase in issues related to this, I’ve now started looking into fixing it. Hopefully, we’ll have better error messages in the next Dagger release.

3reactions
carlonzocommented, Nov 15, 2021

same here. 2.40 to 2.40.1 we get a error: dagger.internal.codegen.ComponentProcessor was unable to process 'packagename.OurComponent' because not all of its dependencies could be resolved. Check for compilation errors or a circular dependency with generated code.

we are not using Hilt. only Dagger + Anvil.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Minecraft Update 2.40 Out for Create New World Changes ...
Mojang has released the Minecraft update 2.40 patch today, and this one is for changes to the Create New World experience and more!...
Read more >
Minecraft 2.40 Patch Notes (Minecraft Version 2.40)
According to the official Minecraft 2.40 patch notes, the latest update brings updated Create New World experience to the game.
Read more >
1501511 – Python 3.6.3 breaks Pykickstart build due to string ...
Description of problem: Some change in how Python 3.6.3 works with strings breaks a Pykickstart unittest, which results in failed build in Koji....
Read more >
No Windows package for 2.40.1 (#1362) · Issues - graphviz
I'm not sure I understand the benefit of running Ubuntu under Windows 10 to build Graphviz. The goal is to debug the Windows...
Read more >
218165 – textproc/libxml++26: Update to 2.91.3
Patch to update textproc/libxml++26 to 2.40.1 (5.67 KB, patch) ... with the comment "Revert r437110, this upgrade breaks lots of ports depending on...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found