now I had my modules set up, and I went about trying to some fields on an Activity or two. ( Any is the root of the class hierarchy in Kotlin, similar to the way that Object is the root of the Java class hierarchy.) Upon closer inspection, that didn’t seem to be the issue, but rather than get hung up on this – I just converted my modules to Java classes and decided to come back to this issue later. My intial thought was that Kotlin was causing my Module to extend Any, rather than Object. Attempting to compile my module gave the following error:Įrror:Modules must not extend from other classes: The first thing I did was try to create the various Dagger Modules that I’d need, which is where I hit my first roadblock. So I proceeded to give it a try with kapt 1 anyway (which seemed like it might do what I want). This didn’t really deter me, however, because I’m stubborn like that. Finally, I stumbled upon this article, which said, “Unfortunately, Square’s Dagger 1 does not appear to work with Kotlin while Google’s Dagger 2 does”. There’s a lot of information about using Dagger 2 with Kotlin but not so much about Dagger Classic. I knew Annotation Processing support was a relatively new addition to Kotlin, so I began to search for some information about how to get Dagger to play nicely with the Kotlin compiler. Personally, I’m still a fan of Dagger 1 (or as I refer to it, Dagger Classic), and when I started working on my Kotlin app, that’s what I was planning to use. I’ve been toying around with it lately (the Kotlin Koans are a great place to start for a beginner) and wanted to try building an app with it – that is, until I hit a few road blocks. Unless you’ve been hiding from all the news about Android development, you’ve likely heard about Kotlin ( which hit version 1.0 on Monday!).

Dagger kotlin