Build randomly fails

Question

Build randomly fails

Closed this issue 3 years ago · 9 comments

Love the idea of the plugin but I get the following error on clean builds from CLI (and therefore CI):

Could not determine the dependencies of task ':features:core-ui:compileDebugJavaWithJavac'.
> Could not create task ':features:core-ui:kaptDebugKotlin'.
   > Manifest file does not exist: /opt/****/workspace/Android-pipeline/features/core-ui/build/generated/auto-manifest/AndroidManifest.xml

I have to run the task from Android Studio for it to pass. I haven't been able to find any configuration differences between the two builds. Any ideas?

Answer 1 · 2021-03-06T23:33:09.000Z

Very interesting. I have the sample project that builds on the CI.

I only tested it with stable Android Gradle Plugin so far. Are you using the beta version?

Answer 2 · 2021-03-07T00:31:29.000Z

Sorry, should have mentioned the AGP version. I'm on 4.0.2. This seems to happen in the configuration phase, so I would think the issue the kapt plugin looking for a file at the config stage. Let me see if I can reproduce with your sample project.

Answer 3 · 2021-04-30T20:46:54.000Z

Hi, sorry for not getting back to this earlier. I tried to reproduce this in my projects but I unfortunately cannot.

If you can give me a sample project, that would be very nice.

Answer 4 · 2021-04-30T23:04:56.000Z

I can't share the project but can't reproduce on others. I can we can just close. I'll reopen if I get time to dig deeper and figure out why it might be happening.

Answer 5 · 2021-07-26T22:39:30.000Z

Hey, I figured out how to reproduce. There's some conflict with Android databinding and kapt.

If you add the kotlin("kapt") plugin and enable dataBinding, even a clean fails with manifest not found.

android {
      ....
      buildFeatures {
        dataBinding = true
    }
}

Answer 6 · 2021-12-03T00:05:20.000Z

I can share I have experienced similar sounding issues with kapt and databinding. I've been using this plugin successfuly in my private projects, and it works really great. I wanted give it a go and also migrate another, larger project that leverages databinding. I applied the plugin and that's the moment I stopped having stable builds 💥

After a bit of digging I was able to narrow it down to the mere fact the manifest package changes. In my case applying the plugin changes package names from com.example.mypackage to com.example.my_package, which appareantly doesn't play well with databinding.
Given the fact the plugin doesn't have to be applied and I was able to reproduce the issue both locally and on CI - I reported the issue directly to Google https://issuetracker.google.com/issues/208855057 🤷
I haven't seen Manifest file does not exist error though

btw

Thank you for this great plugin, I really respect the idea and appreciate the fact you made it open-source!

Answer 7 · 2021-12-03T18:37:14.000Z

Thanks for sharing. I will try to deep dive and see what I can do to fix. It is a tricky one actually. I have some ideas in mind but those might not be good since I want to keep this plugin lazy to keep build performance at a good level.

For the specific package name issue, you can override the package names per module. This might help prevent the conflict with databinding

Answer 8 · 2022-03-19T14:47:37.000Z

Hey folks, it is a bit hard to solve this issue. To handle such edge-cases, I introduced disable() function with the new version. Using this, you can disable auto manifest generation for the modules where you have databinding enabled.

Databinding is considered deprecated so I'm not sure if I will invest time to fix it just for databinding. Thanks for understanding.

Answer 9 · 2022-03-20T18:21:11.000Z

@tasomaniac thanks for the effort, I agree it's not worth the effort with databinding at this piont.