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.

Warnings when using Kotlin 1.3.70

See original GitHub issue

When I updated to Kotlin 1.3.70 I started getting this warning when building:

[WARN] Issue detected with dagger.internal.codegen.ComponentProcessor. Expected 1 originating source file when generating <path-to-repo>/app/build/generated/source/kapt/debug/com/example/feature/FeatureActivity_MembersInjector.java, but detected 0: [].

The FeatureActivity lives in another module which has kapt and dagger enabled but for some reason the injector is generated in the app module. Not sure what I can do to fix this issue.

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Reactions:4
  • Comments:14

github_iconTop GitHub Comments

2reactions
bcorsocommented, Mar 10, 2020

Can you add the com.google.dagger:dagger-compiler dependency to the module containing FeatureActivity. Once you’ve done that, Dagger will generated FeatureActivity_MembersInjector when compiling FeatureActivity.

1reaction
davidliucommented, Mar 11, 2020

Keep in mind, I’m not a dagger contributor, only an avid user of it, so I don’t know any of the context as to why this is, only that this is a workaround.

That said, doing a fresh project with just a member inject on a class, MembersInjector is generated just fine without any components or modules, so I’m unsure what the cause is.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Kotlin 1.3.70 Released - The JetBrains Blog
Today we're happy to present to you the latest version of Kotlin – 1.3.70. This incremental release doesn't provide any major new features....
Read more >
Warning "Kotlin plugin version is not the same as library ...
I faced the same issue while using Firebase with Kotlin. I had to upgrade all the dependencies with their latest version available.
Read more >
"Classpath entry points to a non-existent location" in 1.3.70
Hi,. I updated Kotlin from 1.3.61 to 1.3.70 and I found an irritating warning related to kapt: > Task :base:kaptGenerateStubsTestKotlin w: ...
Read more >
Upgrading your build from Gradle 6.x to the latest
Alternatively, you could run gradle help --warning-mode=all to see the deprecations in ... Note that Gradle scripts are still using the Kotlin 1.3...
Read more >
Kotlin version (@kotlin_version) / Twitter
Changelog Compiler KT-54463 Delegating to a field with a platform type causes java.lang. ... Release Kotlin 1.3.70 EAP 3 · JetBrains/kotlin.
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