Remove unused STRING resources [179166707]

Fixed

Bug

Status Update

No update yet.

Description

ms...@vivino.com

created issue #1

Feb 3, 2021 11:54AM

The inspector "Unused Resources" is told to limit search to strings.xml only and does a fine job and identifying all 1000+ strings that are unused. Then I proceed to remove and things take a turn for the worse. It now removes _all_ unused resources and not just the ones it just showed me.

Either I'm not getting this behaviour or there is a bug somewhere.

Build: AI-201.8743.12.41.7042882, 202012200039,

AI-201.8743.12.41.7042882, JRE 1.8.0_242-release-1644-b3-6915495x64 JetBrains s.r.o, OS Mac OS X(x86_64) v10.16, screens 1680x1050; Retina

AS: 4.1.2; Kotlin plugin: 1.4.10-release-Studio4.1-1; Android Gradle Plugin: 4.1.1; Gradle: 6.5; NDK: from local.properties: (not specified), latest from SDK: 22.0.7026061; LLDB: pinned revision 3.1 not found, latest from SDK: (package not found); CMake: from local.properties: (not specified), latest from SDK: 3.10.2, from PATH: (not found)Source: user_sentiment_feedback

IMPORTANT: Please read

https://developer.android.com/studio/report-bugs.html carefully and supply all required information.

Comments

kj...@google.com <kj...@google.com> Feb 3, 2021 11:58AM

Assigned to an...@google.com.

ac...@google.com <ac...@google.com> May 5, 2022 01:08AM

Status: New

an...@google.com <an...@google.com> Aug 29, 2023 08:49PM

Assigned to an...@google.com.

an...@google.com <an...@google.com> Sep 19, 2023 10:10PM

Accepted by an...@google.com.

an...@google.com <an...@google.com> #2Sep 26, 2023 07:58PM

Marked as fixed.

This is fixed in an upcoming canary build of Android Studio.

an...@google.com <an...@google.com> #3Sep 28, 2023 09:05PM

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 Iguana | 2023.2.1 Canary 6
Android Gradle Plugin 8.3.0-alpha06

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!

Issue 179166707