AGP 8.2+ forces coreLibraryDesugaring to all intermediate library modules, even if they don't use it [341002194]

Fixed

Bug

Status Update

No update yet.

Description

g....@xe.gr

created issue #1

May 16, 2024 02:49PM

DESCRIBE THE ISSUE IN DETAIL:

STEPS TO REPRODUCE:

have a base (library) module in your app that needs and uses coreLibraryDesugaring
use the above module in various other (library) modules of the same app that don't need coreLibraryDesugaring themselves
use corelibraryDesugaring in the application module of the app
use AGP 8.2+
(try to) build the app

Until AGP 8.1.x, the above setup was working OK. However, when updating to AGP 8.2.x, the build fails and AGP forces us to define coreLibaryDesugaring in all the intermediate (library) modules too.

IMO this enforcement is too strict and it should be applied only for application-type modules, not library-type ones too.

Android Studio Jellyfish | 2023.3.1
Build #AI-233.14808.21.2331.11709847, built on April 12, 2024
Runtime version: 17.0.10+1-b1087.23 aarch64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
macOS 14.4.1
GC: G1 Young Generation, G1 Old Generation
Memory: 5120M
Cores: 10
Metal Rendering is ON
Registry:

ide.instant.shutdown=false
debugger.click.disable.breakpoints=true
debugger.new.tool.window.layout=true
analyze.exceptions.on.the.fly=true
ide.experimental.ui=true

Non-Bundled Plugins:

com.intellij.javafx (1.0.4)
dev.j-a.swift (1.0.0.345-233)
com.intellij.marketplace (233.14808.24)
IdeaVIM (2.11.0)
com.jetbrains.kmm (0.8.2(233)-8)
com.majera.intellij.codereview.bitbucket (2024.2.0.233)

Comments

g....@xe.gr <g....@xe.gr> #2May 16, 2024 03:02PM

Information redacted by Android Beta Feedback.

bi...@google.com <bi...@google.com> May 16, 2024 09:55PM

Assigned to bi...@google.com.

da...@google.com <da...@google.com> May 17, 2024 09:11PM

Reassigned to an...@google.com.

je...@google.com <je...@google.com> May 21, 2024 06:03PM

Reassigned to bi...@google.com.

bi...@google.com <bi...@google.com> #3May 21, 2024 06:30PM

Accepted by bi...@google.com.

redacted

bi...@google.com <bi...@google.com> #4May 23, 2024 12:13AM

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

g....@xe.gr <g....@xe.gr> #5May 24, 2024 08:30PM

m32694048@gmail.com

bi...@google.com <bi...@google.com> #6May 24, 2024 08:54PM

I have turmux

g....@xe.gr <g....@xe.gr> #7May 24, 2024 09:06PM

Unfortunately, the issue isn't solved in beta 2.1 despite the changelog saying it is :-(

bi...@google.com <bi...@google.com> #8May 24, 2024 09:09PM

This issue is still persisting in the Android 15 public beta 1 as well.

mf...@medallia.com <mf...@medallia.com> #9May 31, 2024 05:55PM

Thank you for reporting this issue. We have a fix rolling out in the next release.

bi...@google.com <bi...@google.com> #10May 31, 2024 05:59PM

New update

jt...@medallia.com <jt...@medallia.com> #11Jun 3, 2024 04:48PM

Oppo

bi...@google.com <bi...@google.com> #12Jun 3, 2024 05:51PM

The issue returned in Android 15 Beta 2

e....@gmail.com <e....@gmail.com> #13Jun 21, 2024 09:17AM

Android 15 beta 2.. issue persists

sg...@google.com <sg...@google.com> #14Jun 21, 2024 09:25AM

Yes, issue persists
Build number AP31.240426.023

e....@gmail.com <e....@gmail.com> #15Jun 21, 2024 09:53AM

Issue definitely still persisting :/

Message last modified on Jun 21, 2024 09:58AM

bi...@google.com <bi...@google.com> Aug 28, 2024 10:26PM

Marked as fixed.

sg...@google.com <sg...@google.com> #16Aug 29, 2024 06:17AM

We detected a new issue b/344110362 being duplicated to this closed issue automatically, and we have set b/344110362 as the current tracking bug, please check if any action needs to be taken.

g....@xe.gr <g....@xe.gr> #17Aug 29, 2024 06:39AM

Still not resolved with Android 15 beta 2.2 :-(

bi...@google.com <bi...@google.com> #18Aug 29, 2024 08:57PM

Didn't have issue with beta 2.1. Now issue has returned. Android version AP31.240426.023.B4.