Android Studio does not read AGP 7.1 source & javadoc jars [197636221]

Assigned

Bug

adexe s nau

Status Update

No update yet.

Description

dr...@gmail.com

created issue #1

Aug 24, 2021 06:05PM

I'm testing out the new source & javadoc jar generation added in AGP 7.1 via https://issuetracker.google.com/issues/145670440

It seems that Android Studio does not know how to consume source or javadoc jars generated via this mechanism.

I'm using this configuration:

android.publishing.multipleVariants {
  allVariants()
  withSourcesJar()
  withJavadocJar()
}

afterEvaluate {
  publishing {
    publications {
      maven(MavenPublication) {
        from components.default

        ...
      }
    }
  }
}

STEPS TO REPRODUCE:

See the dhannay/agp7.1-bug-repro branch of this repo (specifically this commit)
Run ./gradlew publishToMavenLocal to publish a snapshot build
From any other Android project, add a dependency: implementation 'com.linkedin.shaky:shaky:3.0.3-SNAPSHOT'
Run Gradle sync in Android Studio and try to open any class from the library (e.g. Shaky.java).
Observe that Android Studio does not detect the source jar and instead shows the decompiled bytecode

Studio Build: Android Studio Bumblebee | 2021.1.1 Canary 9 Build #AI-211.7628.21.2111.7653804, built on August 18, 2021 Runtime version: 11.0.10+0-b96-7281165 x86_64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. macOS 11.5.2 GC: G1 Young Generation, G1 Old Generation Memory: 4096M Cores: 12 Registry: external.system.auto.import.disabled=true

Version of Gradle Plugin: 7.1.0-alpha09 (in both producing and consuming projects) Version of Gradle: 7.2-rc-1 Version of Java: 11.0.10 OS: macOS

Comments

xa...@google.com <xa...@google.com> #2Aug 24, 2021 06:29PM

Hello

dr...@gmail.com <dr...@gmail.com> #3Aug 24, 2021 11:34PM

Hello there,

Thank you for reporting this! However, it seems that this is the expected behavior as the method will return the valid named ranges. Would you be interested in turning this into a feature request instead? If yes, how would it impact your organization in terms of costs and productivity?

bi...@google.com <bi...@google.com> Aug 31, 2021 11:09AM

Accepted by bi...@google.com.

to...@googlemail.com <to...@googlemail.com> #4Aug 31, 2021 12:50PM

Sure, please make it a feature request. It would be useful for automating the maintenance of named ranges across a large number of sheets, which is what I was trying to implement 3 years ago when I logged this issue. I don't know how much time is spent manually checking and fixing corrupted named ranges, but certainly some amount each week.

to...@googlemail.com <to...@googlemail.com> #5Aug 31, 2021 01:19PM

Hi,

Named ranges help a lot to write dynamic scripts that do not require static range references. And it is crucial to have a good way to define, delete and manage named ranges within app scripts. Especially manage invalid named ranges.

bi...@google.com <bi...@google.com> #6Aug 31, 2021 01:33PM

Thank you for the details provided! I have forwarded them internally.

Best regards

to...@googlemail.com <to...@googlemail.com> #7Aug 31, 2021 01:55PM

+1 please fix this

Message last modified on Aug 31, 2021 01:56PM

xa...@google.com <xa...@google.com> #8Aug 31, 2021 06:35PM

I really need this feature, as my workflow often involves maintaining a collection of tabs, each having many named ranges in common. That is, I'll create a new worksheet by duplicating a "template" sheet, and then populate it with data. Older sheets eventually get deleted, which produces a growing collection of defunct named ranges.

I haven't found a way to delete them in bulk via the Sheets UI either. In fact, it's a surprisingly tedious process because the UI resets the viewport to the very top list item after each deletion, forcing the user to manually perform O(n-squared) scroll wheel rotations.

I would be really grateful if this were fixed / added.

Thank you

to...@googlemail.com <to...@googlemail.com> #9Sep 1, 2021 08:40AM

bi...@google.com <bi...@google.com> #10Feb 8, 2022 01:42AM

I have run into this bug earlier this week.

Any chance of progress?

In particular, named ranges that are on a deleted sheet (tab) can hang around and do not show up through the Spreadsheet.getNamedRanges(...) call.

The Spreadsheet Editor is doing something out of band wrt the API to see these objects but from App Script I can not see them.

Message last modified on Mar 21, 2022 04:28PM

bi...@google.com <bi...@google.com> #11Mar 21, 2022 04:32PM

I need this ... it's a nightmare having to do it manually

th...@showroomprive.net <th...@showroomprive.net> #12Jul 25, 2022 03:38PM

This request would break many of my scripts as we are relying on the broken named ranges not being found and we would otherwise often have duplicate named ranges with the same name. Please make it an option to also select the broken named ranges which is off by default

dr...@gmail.com <dr...@gmail.com> #13Sep 26, 2022 11:41PM

Dear Google Team, this issue got reported 5 years back. Can you please let us know when this is going to get fixed

bi...@google.com <bi...@google.com> #14Sep 26, 2022 11:43PM

I'm impacted as well!
Having no more options but manual deletion...
I hope NamedRanges methods get improved soon.

[Deleted User] <[Deleted User]> #15Oct 27, 2022 10:20PM

bi...@google.com <bi...@google.com> #16Mar 20, 2023 05:12PM

Assigned to sm...@google.com.

+1 -- for Sheets using a lot of Named Ranges, not being able to access these #REF ranges with a script is a big problem.

dr...@gmail.com <dr...@gmail.com> #17Apr 28, 2023 12:37AM

I can't see the linked internal issue, but is there any chance this is coming soon? It's blocking us from publishing separate debug vs release aars for our libraries which means devs need to resort to things like passing "isDebug" flags into library code.

bi...@google.com <bi...@google.com> #18May 1, 2023 06:26PM

Currently the implementation is landed but we disable the feature because of a performance concern. Bradley, users can try it with studio flag right?

sm...@google.com <sm...@google.com> #19May 1, 2023 06:31PM

Unfortunately there is currently no way for users to enable this.

sa...@gmail.com <sa...@gmail.com> #20Aug 6, 2023 11:51AM

I'm trying to make this work for a few of our specific usecases. While I can figure out how to resolve the sources based on the sample project at https://issuetracker.google.com/u/1/issues/197636221#comment10 . I was unable to figure out how to link those sources to Android Studio. Would you have an example, guidance (or a link to the studio sources that do this) so that I can understand how does sources linking work in Android Studio?

ga...@google.com <ga...@google.com> Sep 20, 2023 08:55AM

Reassigned to ga...@google.com.

ga...@google.com <ga...@google.com> #21Sep 22, 2023 04:55PM

We added an option under File | Settings | Experimental that you can use to enable this feature: Enable support for multi-variant Javadocs and Sources. I'm reducing priority to P2 because there is an opt-in.

It will not be enabled by default until https://issuetracker.google.com/271601839 is fixed, and we are also thinking about making javadoc/sources more on-demand (https://issuetracker.google.com/301214737).

Message last modified on Sep 22, 2023 04:56PM

to...@googlemail.com <to...@googlemail.com> #22Sep 22, 2023 08:31PM

Which version(s) of Android Studio will include the feature?

za...@gmail.com <za...@gmail.com> #23Sep 25, 2023 03:09AM

In Studio Iguana alpha05, it no longer downloads/indexes sources and javadoc jars, Is it possibly related to this feature's work? I tested with both Enable support for multi-variant Javadocs and Sources enabled and disabled

ga...@google.com <ga...@google.com> #24Sep 25, 2023 08:59AM

Re #22: It is in Studio H Canary 9 (and above) and Studio I Canary 1 (and above)

Re #23: It should not be related to this work, but it may be an issue introduced by this change. Can you please file a new issue?

wd...@gmail.com <wd...@gmail.com> #25Feb 12, 2024 07:47PM

Re #24: I have tried but it doesn't work, anything I have missed? I'm using:

studio: Android Studio Hedgehog | 2023.1.1 Patch 2
gradle: 7.4
agp: 7.3.0

ga...@google.com <ga...@google.com> #26Feb 13, 2024 05:59PM

Re #25:

You need Studio Hedgehog and above for the IDE and AGP 8.1 and above for build.

wd...@gmail.com <wd...@gmail.com> #27Feb 13, 2024 06:18PM

Re #26: Thank you so much

pa...@gmail.com <pa...@gmail.com> #28Feb 20, 2024 10:20AM

Hello I am using studio Hedgehog and I can not download java sources, I observed on compose libraries 1.5/1.6, I tried also iguana rc2 but has the same problem I am seeing the compiled code

Android Studio Hedgehog | 2023.1.1 Patch 2 gradle: 8.2 agp: 8.2.0

https://snipboard.io/FTecha.jpg

Update: After I disabled "Enable support for multi-variant Javadocs and Source" , the problem solved for both Android studios

Message last modified on Feb 20, 2024 10:29AM

to...@yahoo.com <to...@yahoo.com> #29Mar 24, 2024 02:02PM

still a problem in Android Studio Koala | 2023.3.2 Canary 2 (seen it with the material jar)

is...@google.com <is...@google.com> May 13, 2024 07:08AM

Status: New

hu...@google.com <hu...@google.com> Jun 4, 2024 04:50PM

Assigned to an...@google.com.

bi...@google.com <bi...@google.com> #30Jun 4, 2024 11:28PM

Reassigned to bi...@google.com.

As #21 mentioned, keep it open until the multi variant support is enabled by default. Currently, blocked on Gradle side.

ia...@stadiamaps.com <ia...@stadiamaps.com> #31Oct 7, 2024 02:28PM

Still doesn't seem to be working for me in Android Studio, even after enabling the setting. We've had to fall back to only publishing release builds.

Here is an example published on Maven Central:

https://repo.maven.apache.org/maven2/io/github/rallista/maplibre-compose/0.0.18/. And a discussion on a GitHub issue:

https://github.com/vanniktech/gradle-maven-publish-plugin/issues/828.