Remove unused strings upload_progress_notification_title_in_progress and share_license_summary

Open Beginner friendly
  • Is something wrong?
#7,280 2 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@benndip is already working on this.

Since Nov 10, 2026.

Assessment

Difficulty
1/5
Estimated time
Under an hour
Newbie friendliness
83/100
Issue type
Refactor
Clarity
Clearly specified
Activity status
Active
Tech stack
android, kotlin, xml
Domain
internationalization, mobile

Research direction

Open app/src/main/res/values/strings.xml and values-qq/strings.xml; locate upload_progress_notification_title_in_progress and share_license_summary and remove those entries. Check that neither string remains in those files; translated entries are expected to disappear during the next translatewiki.net sync. The optional lint check is a separate suggestion, with related issues #4284 and #6456.

Written by the indexing model from the issue text.

Description

good first issue localization
Summary

Two translatable string resources in app/src/main/res/values/strings.xml are no longer referenced anywhere in the code:

String Last usage removed in
upload_progress_notification_title_in_progress (%1$s uploading) #4298 (2021, WorkManager upload rewrite)
share_license_summary (plural, This image will be licensed under %1$s) #6738 (2026, license selection UI redesign)

Translators on translatewiki.net are still asked to translate and maintain them, and some translations contain broken placeholders (ckb, ka, xmf for the first; my, tcy for the second, see #7003), which shows up as noise in placeholder checks.

Suggested fix

Remove both entries from values/strings.xml (and their values-qq/strings.xml documentation). The translated values-*/strings.xml entries will be dropped automatically by the next translatewiki.net sync.

It might be worth adding a lint check (Android Lint UnusedResources, scoped to strings) to CI so unused strings are caught when the code using them is removed. Related: #4284, #6456.

Dominant language
Kotlin
Stars
1.2k
Forks
1.4k
Avg merge
1d 23h
Merged PRs (30d)
151

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from commons-app/apps-android-commons

All issues in commons-app/apps-android-commons

Similar issues

More Kotlin issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.