Closed gmazzo closed 3 years ago
Thanks for reporting this. We will debug and get back to you.
@gmazzo Are you still facing this issue in the latest version of the plugin? Also are you using Android Studio or Intellij iDEA ? And the version?
Still the same, the error is gone now (or at least I couldn't find it) but still the main component is missing.
Can you share us the below details?
Android Studio 4.2 Canary 16 Build #AI-202.7660.26.42.6939830, built on October 29, 2020 Runtime version: 11.0.8+10-b944.6842174 x86_64 VM: OpenJDK 64-Bit Server VM by N/A macOS 10.16 GC: G1 Young Generation, G1 Old Generation Memory: 6144M Cores: 12 Registry: external.system.auto.import.disabled=true Non-Bundled Plugins: com.jetbrains.ChooseRuntime, org.jetbrains.kotlin, com.madrapps.dagger-plugin, org.intellij.plugins.markdown
202-1.4.30-release-AS8194.7
dagger-2.29.1
Thanks @gmazzo Can you test with this? Just download the zip and drag drop it in the IDE and restart your IDE. Please let us know if the issue is resolved.
Still the same. May be our project is too complex? We have several Gradle modules and some of them expose full dagger components (those are shown). Then the main app component has them as dependencies (and that's the one it's missing).
Is there any debug/intermediate file I can check or send to you?
Yes. Go to Preferences -> Appearance & Behaviour -> Notifications. Turn on the "Log" option for the "Dagger Group". Now hit the "Refresh" button in the Dagger toolwindow. The logs will get printed in the Event Log. Could you copy the entire log and mail to madrasappfactory@gmail.com ? We will debug it and get back to you.
Now it has appeared 🤔 , but also other components are missing. Strange.
How this perform with big scale Dagger
projects and with an extensive usage of dagger-android
? Seems it's blocking the IntelliJ UI to me.
I think I can close the ticket now. But I'm not sure I can promote the tool internally in our company (yet). Seems a bit unstable, but goes in a great direction!
We have rolled out the fix to all versions we currently support. We have tested with Components with around 50+ sub components. Ideally the graph is calculated in the background thread, and then the tree is updated in the UI thread. So there shouldn't be anything blocking. I will close this issue, and if you continue to face performance issues please raise a new one. Meanwhile we are testing the plugin for performance problems.
In our app, we have several Dagger components, and our main one declares them as a dependency.
I only see the child components in the graph, but no the main one
GlovoAppComponent
:Log: