Document -Adagger.android.experimentalUseStringKeys publicly
See original GitHub issueThe commit https://github.com/google/dagger/commit/3a089646fb70fb5a193a731c4909d6ccaeeaadd3 mentions:
I’ve decided to hold off on documenting this until we have a viable solution externally (when R8 is the standard, and it supports META-INF/proguard files).
The stable version on Android Studio 3.3 now supports proguard files under META-INF
for both Proguard and R8. This should be publicly documented now.
Small addition: Maybe do not forget to also mention that enabling this will break Gradle incremental annotation processing support.
Issue Analytics
- State:
- Created 5 years ago
- Comments:5
Top Results From Across the Web
Using Android injector with SDK-level-dependent components.
I have a subclass of TileService (an android.app.Service that is only available on 24+). I want to use the Android injector and ...
Read more >Manual dependency injection - Android Developers
All instances provided by this container can be public. In the example, because you only need an instance of UserRepository , you can...
Read more >Dependency Injection with Dagger 2 - CodePath Cliffnotes
Many Android apps rely on instantiating objects that often require other ... be included as part of the dependency chain by creating a...
Read more >Using Dagger 2 for dependency injection in Android - Tutorial
vogella.java.dagger2 top level package. 3.2. Define or adjust Maven build file. Adjust your pom.xml ...
Read more >Dagger & Android
inject(this); super.onAttach(activity); // ... } } @Subcomponent(modules = ...) public interface YourFragmentSubcomponent extends AndroidInjector<YourFragment> ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Looks like this is fixed in Android Gradle Plugin 3.5 Alpha 08
It looks like Android tooling only reads from jar and aar dependencies. Not from generated code.
Here is an issue to follow regarding this: https://issuetracker.google.com/issues/124235144