Source sets from submodules not listed while creating a new string [365591190]

Fixed

Bug

Status Update

No update yet.

Description

mi...@gmail.com

created issue #1

Sep 10, 2024 06:31AM

```
####################################################

Please provide all of the following information, otherwise we may not be able to route your bug report.

####################################################

1. Describe the bug or issue that you're seeing.
In the new beta version of Android Studio it is not possible to create a new string value resource in the strings.xml of the submodule from another submodule. I have one strings.xml located in the common submodule, which is integrated by using "implementation project(path: ':common')" in build.gradle of the main module.
I use this since years, as I only want to have one strings.xml for all submodules to have only one file to translate and to use the same strings in all submodules.
In the last release versions it was possible to create a new string resource value in this common submodule with the main module, but in the new beta it is not possible anymore!
Please fix this!
Please also have a look to the screenshot I made.

For more information on how to get your bug routed quickly, see

https://developer.android.com/studio/report-bugs.html

Build: AI-242.20224.300.2421.12312915, 202409032002
AS: Ladybug | 2024.2.1 Beta 1
AI-242.20224.300.2421.12312915, JRE 21.0.3+-12282718-b509.11x64 JetBrains s.r.o., OS Windows 11(amd64) v10.0 , screens 1920x1080 (100%)
Android Gradle Plugin: 8.6.0
Gradle: 8.8
Gradle JDK: JetBrains Runtime 21.0.3
NDK: from local.properties: (not specified), latest from SDK: (not found)
CMake: from local.properties: (not specified), latest from SDK: (not found), from PATH: (not found)
```

Screenshot 2024-09-10 083043.png

232 KB

View

Download

Comments

vm...@google.com <vm...@google.com> Sep 10, 2024 08:59AM

Assigned to an...@google.com.

je...@google.com <je...@google.com> Sep 13, 2024 11:25PM

Reassigned to cm...@google.com.

cm...@google.com <cm...@google.com> #2Sep 16, 2024 11:31AM

I don't think the average developer understands the distinction between method references and method definitions in this context (inside a DEX file). I know I don't.

@jvg, can you elaborate?

mi...@gmail.com <mi...@gmail.com> #3Sep 17, 2024 08:27AM

people who are looking at the bytecode in the dex to optimize their app through shrinking hopefully will learn the difference as string tables for method references between various dex files can account for quite a bit of disk space. but more importantly a definition is something you can analyze its code for where a reference you can't so the UI can be confusing without seeing the difference

cm...@google.com <cm...@google.com> #4Sep 17, 2024 12:11PM

Reassigned to an...@google.com.

How about something like this?

I think having defined members be directly under the class node while references are nested in a group makes more sense.

Also note that the method refs have a slightly different icon. There is no existing equivalent for field refs that I could find.

https://screenshot.googleplex.com/4yXVM9Rzh4wnkjM.png

an...@google.com <an...@google.com> #5Sep 18, 2024 05:56PM

Accepted by an...@google.com.

sounds reasonable to me, thanks

an...@google.com <an...@google.com> #6Sep 18, 2024 09:17PM

Marked as fixed.

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 Ladybug Feature Drop | 2024.2.2 Canary 4
Android Gradle Plugin 8.8.0-alpha04

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!

an...@google.com <an...@google.com> #7Sep 23, 2024 08:03PM