Status Update
Comments
mi...@gmail.com <mi...@gmail.com> #2
Additional Info: it happens only in androidTest files - on regular packages it works normally
cl...@google.com <cl...@google.com>
kd...@google.com <kd...@google.com> #3
Andy when you made changes to fix folding did that have any sort of unintended side-effect? I'm doubtful, but just figured you might have more context there.
ma...@gmail.com <ma...@gmail.com> #4
an...@google.com <an...@google.com> #5
Thanks for the feedback. I am not able to reproduce the issue locally, unfortunately. To help us troubleshoot this issue further, we will need more information.
Can you share a sample project where this issue happens? I suspect this may be triggered by specific characteristics of the resources in use, but I'm not sure exactly what.
Barring that, a few questions may help:
- Are the resources that are shown as
...
from the current module, or a dependent module? - Are the resource values empty, or longer than 60 characters?
- Do the resource values use any placeholders (eg,
%1$s
)? - What code is hidden behind the three dots? Is it a call to
getString()
, just a raw reference toR.string.foo
, something else?
mi...@gmail.com <mi...@gmail.com> #6
Example of such a hidden part test.findText(Common.getString(R.string.seal_not_scanned)).isNotDisplayed() Common is object with method for getting String from main project: fun getString(@StringRes id: Int): String { val context: Context = ApplicationProvider.getApplicationContext() return context.getString(id) }
part which is hidden behind dots is bolded one. Only way to uncover it is to type some object like Common after "(" then it is shown. In this is example under R.string.seal_not_scanned is short text "Not scanned"
Everything happens under androidTest files and string resources are from main module of app
an...@google.com <an...@google.com>
an...@google.com <an...@google.com> #7
I've submitted a fix that I expect will fix this which will be available in the next canary (Ladybug Feature Drop 2024.2.2 Canary 2).
Note that I haven't been able to reproduce this locally, unfortunately, so the fix is speculative. I've been able to reproduce scenarios where resources are folded to ...
instead of the actual resource value, but clicking (or Ctrl+clicking) on them always expands them. But the fix I've made actually now will start resolving the resource values correctly, so the appropriate values will be displayed. Since the reports we've received of this bug all involve the "missing" resource values that are replaced with ...
, I'm hopeful this will make the problem a non-issue.
Please let us know if you run into this again on Ladybug Feature Drop 2024.2.2 Canary 2 or a later build.
an...@google.com <an...@google.com> #8
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 2
- Android Gradle Plugin 8.8.0-alpha02
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!
Description
In code when there is occurrence like R.string.sth it is usually folded to ... (3 dots, usually in parenthesis) - like in attached screenshot.
Previously single click or sometimes double click was revealing full definition allowing to edit it. Now it is often stuck and do not expand it. Sometimes it reveals as previously.
Build: AI-241.18034.62.2411.12071903, 202407102313
AS: Koala | 2024.1.1 Patch 1
AI-241.18034.62.2411.12071903, JRE 17.0.11+0--11852314x64 JetBrains s.r.o., OS Windows 10(amd64) v10.0 , screens 2400.0x1350.0, 1920.0x1080.0
Android Gradle Plugin: 8.5.1
Gradle: 8.7
Gradle JDK: Amazon Corretto 21.0.3
NDK: from local.properties: (not specified), latest from SDK: 20.1.5948944
CMake: from local.properties: (not specified), latest from SDK: 3.6.0-rc2, from PATH: (not found)
```