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.
`dagger-android` 2.10-rc1 aar is missing AndroidManifest.xml
See original GitHub issueThe aar package for dagger-android module is missing AndroidManifest.xml that will generate the following error
Error:Execution failed for task ':app:processDebugManifest'.
> com.android.manifmerger.ManifestMerger2$MergeFailureException: java.io.FileNotFoundException: /.../app/build/intermediates/exploded-aar/com.google.dagger/dagger-android/2.10-rc1/AndroidManifest.xml (No such file or directory)
Current fix now is manually adding AndroidManifest.xml from this repo to 'build/intermediates/exploded-aar/` path but this file will be deleted if a clean build is performed.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:6
- Comments:5
Top Results From Across the Web
No results found
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 Free
Top 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
I submitted a fix and it should be in rc2. Thanks for the report!
This was an issue with our bazel-deploy system - I imagine it’s not the same issue. We were shipping a jar when really we meant to be shipping an aar