IssueTracker

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

We have shared this with our product and engineering team and will update this issue with more information as it becomes available.

Thanks for reporting this issue.

COARSE_LOCATION typically takes location information from the nearby cell tower. If many users are near the same cell tower, each of those users will be given the same position. Using a FINE position will give much more detailed information.

Also, in certain areas, for privacy reasons, a less-exact location will be given, and that less-exact location might be identical for many users. Again, a fine-location configuration will return more precise location data.

We believe with reference to the above comment, your query has been answered, hence closing the bug. Please feel free to re-open the issue in the future if desired.

It seems AGP is not correctly excluding kotlin_module files during java resource merging, so we'd expect a collision - although this error message isn't clear.

Until we release we have a fix for the issue, a workaround may be to add packagingOptions { exclude 'META-INF/*.kotlin_module' } to the build.gradle conflicting libraries, so AGP doesn't attempt to merge them.

Alternatively you can give them unique names e.g.

kotlin {
    compilerOptions {
        moduleName.set(project.path)
    }
}

applied to all projects

We set the module to the dashified project gradle path. Kinda feel like this should be the default for the module merging issue in general

In my case, I had similar errors with MergeJavaResourcesTask
But in my case, errors were against for META-INF metadata from Google AutoService instead of kotlin-module

And I did set same workaround with Comment #8, then errors were gone.

I also had an error from Google AutoService and packagingOptions { exclude 'META-INF/*.kotlin_module' } removes the error in next build but it does not look correct solution. Can someone help me to fix this issue. For my case the error is for some debug source code which we generate using Google AutoService. Should I exclude those files or use pickFirst for them?

I have same issue again after Comment #14
I'm not sure, but I'm guessing that error was raised again after applied AGP 8.2

In my case, module A and module B have implementations of interface Xxx which can be loaded by AutoService.

and MergeJavaResourcesTask was failed of app C while merge META-INF/services/Xxx from module A and module B

I had previously applied the workaround from #10 to our build, however it caused packaging issues that manifested as runtime crashes. I'll be taking a second look at the workaround to see if I can fix our previous issues with it since we are starting to see this problem happen a lot more frequently. An issue with Anvil has been causing our developers to use --rerun and --rerun-tasks more frequently than usual, which masks the issue here. With the latest beta release of anvil, those options are no longer needed and this bug pops up a lot more frequently. We are using AGP 8.2.2 currently

With the latest beta release of anvil, those options are no longer needed and this bug pops up a lot more frequently.

It doesn't seem like the latest beta has resolved these issues :/ https://github.com/square/anvil/issues/876

Have been having the same issue in recent builds, rm -rf app/build is what helped in my case.

I've managed to get what looks like a reliable reproduction case for this.

This is mitigated in 22ea772c902a9891a6023ed1ebdc832871775ba6 but I am suspicious there are other lurking issues by inspection and from #comment19

Filed issue 327603250 to follow up, marking this as closed as the initial issue should no longer directly bite.

Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:

• Android Studio Jellyfish | 2023.3.1 Canary 12
• Android Gradle Plugin 8.4.0-alpha12

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.

Thank you for taking the time to submit feedback — we really appreciate it!

AGP 8.3 final version was released at today.
Could this fix be applied to AGP 8.3.x patch version?
Or is there another solution that can alleviate this issue?

Re #comment19 - are you using merge or pickFirst in packagingOptions?

No, we have some exclude rules but don't use either merge or pickFirst

The fixes for this issue are now also available in:

• Android Studio Iguana | 2023.2.1 Patch 1
• Android Gradle Plugin 8.3.1

We encourage you to try the latest update.

If you notice further issues or have questions, please file a new bug report.