IssueTracker

can you share your android studio version

Is this happening with Studio 3.0?

Note: This worked for me on Windows 7 Pro 32-bit (with Android Studio 2.3.3). Seems like an issue with adt-branding module (which should contain the "/idea/AndroidStudioApplicationInfo.xml" resource).

Hi, also happened on Mac Book Pro 15 retina mi-2015
MacOs Sierra 10.12.6
Android Studio 2.3.3
java version "1.8.0_51"
Java(TM) SE Runtime Environment (build 1.8.0_51-b16)
Java HotSpot(TM) 64-Bit Server VM (build 25.51-b03, mixed mode)

Thank you for this feedback. Your feedback helps make sure Android development tools are great! Given your issues has been resolved I am closing this issue.

Yeah, that's the kicker. Sync doesn't appear to touch annotation processing at all at the moment, and it would be quite a significant change to make. I'll have a think. Let me know if you have any ideas in the mean time, and thanks for the quick reply!

Doesn't every project that uses APT require you to build to see the generated files? Using Dagger2 for example, if I create a component, DaggerComponent won't exist until I build. I would rather have the test generated sources work today like normally generated sources, then wait for a feature that would be a nice to have but sounds incredibly difficult.

Don't forget to support library and test projects. A snippet on SO is for application projects only. In gist linked in the first post, there is comment for library projects: https://gist.github.com/koral--/f99d64c72741c29431ce4e15c0e5b6d7#gistcomment-2020133

Regarding not firing annotation processors on Gradle sync. When creating this issue I've only complained about not recognized already generated sources.
I agree with #8 that generating sources on each Gradle sync may be a candidate for the separate issue/feature.

David: you're spot on, that's the current situation. I wanted to be on the same page as the community before I submitted anything.

Karol: yep, I've made sure that both library and test projects work as well. Thanks for the reminder! :)

Does your solution also work with Kotlin and kapt?

Good question. I don't have a project that reproduces the bug in Kotlin. Do you have one? Preferably something extremely minimal.

Here is an official sample with kotlin and dagger: https://github.com/JetBrains/kotlin-examples/tree/master/gradle/android-dagger
I haven't tried if it reproduces the bug, but theoretically, it should.

Similar workaround exists for idea Gradle plugin: https://github.com/JetBrains/kotlin-examples/blob/master/gradle/kotlin-code-generation/example/build.gradle#L17-L18
Note that paths to generated source files are different: folders named kapt and kaptKotlin vs apt.

ag/I2d478c4dd156d2a8c19dbe7dbd92681cc21dcfa8 contains the fix for the original problem. I'm going to close this bug for the time being. Karol: if you continue to have problems with Kotlin after the 3.0 release, please open a new bug and refer back to this one in it. :)

ด้สักที