Munim Technologies

Research/Software

Translations that crash Android apps

We ran 1,269,051 translated format strings from every F-Droid app through Java's real formatter. 360 throw whatever the app passes, and 232 of them, in 64 repositories, are strings the app's code actually formats.

Oct 16, 2026 · 6 min read

Android apps fill in text like "3 files deleted" by handing a translated template to Java's formatter. If a translator types %1$ instead of %1$s, puts a space inside a placeholder, or leaves a bare 100%, the template becomes invalid and the call throws. Only people using that language see the crash, so developers rarely do. We measured how often this happens across every open-source app on F-Droid. Of 1,269,051 translations of format strings, 360, in 95 repositories, throw whatever the app passes. 232 of those, in 64 repositories, are strings the app's code formats with arguments: reachable crashes.

The rate is low, but the failure is total for the users it hits, and it gets past every translation platform and every free check we examined.

1,269,051

translated format strings run through OpenJDK 21's java.util.Formatter

360

throw whatever the app passes, in 95 repositories

232

of them are formatted by the app's code, in 64 repositories

1.0

precision of our static check against the JVM (recall 0.983)

The question

Calls like getString(R.string.x, arg) and getQuantityString(...) pass the translation for the user's language to java.util.Formatter. Wikimedia Commons alone has fixed this crash several times, one string and one language at a time. We wanted a census rather than anecdotes: how many apps ship such a translation, which mistakes cause them, and whether the tools translators already use would have caught them.

What we did

On 16 October 2026 the census read the latest commit of all 4,476 source repositories behind F-Droid's index; 3,751 have Android string resources. For every translation of a string with printf placeholders, it called OpenJDK 21's real formatter with arguments matching the English string. A translation is a crash if it throws whatever the app passes, and crash-if-text if it throws only when the app passes text where the translation expects a number. Plural forms are checked against the English form that reads the most arguments, because Android passes every form the same ones. We then searched each app's Kotlin and Java code for calls that format the string, which separates reachable crashes from strings the code never formats.

Reading rows by hand found two false-positive classes in an earlier pass, which we fixed and reran: a date conversion that accepts the Long an app actually passes, and Wikipedia link markup that Android treats as plain text. Both corrections are in the numbers here.

What we found

Crashes are concentrated. ownCloud holds 47 reachable crashes, nearly all in one Uyghur file; Wikimedia Commons 26, Cashiro 25 and OsmAnd 12. Most other affected repositories have one to four. By language, Uyghur leads with 55 crashing translations, all in one app, then Turkish with 18, Arabic 16 and Russian 14.

Reachable crashes by kind of mistake

232 reachable crashes in 64 repositories. A stray percent is the most widespread mistake, in 26 repositories; the malformed-index count is mostly one Uyghur file (44 rows). Source: android-translation-crash-census: data/v6/taxonomy.md (formatted-crash table)

Some mistakes are easy to miss for a reader. The conversion letter gets translated: Russian %1$с uses a Cyrillic es, Arabic %1$دم a dal for d, Greek %1$δδ a delta. To a native reader these look right. A space after the percent sign, common in Turkish, makes the formatter read the space as a flag. And English strings that spell out "25 percent" to avoid escaping are translated as 25%, which throws.

Every translation route appears among the crashes: Crowdin, Transifex, Weblate, translatewiki.net, Lokalise, Localazy and files edited in the repository. The rate per checked translation varies by platform, but one large file can dominate a platform's count, so these are not ratings of the platforms.

Crashing translations per 100,000 checked, by the platform a repository names

All 360 crashing translations, not only reachable ones. Most of Transifex's 65 crashes are ownCloud's Uyghur file. The platform is read from config files or the README. Source: android-translation-crash-census: data/v6/summary.json (by_platform)

We also tested the three open-source checks that could have looked at every one of these translations before release: Weblate's Java format check, translate-toolkit's printf test (pofilter) and Android Lint. Over 366 crashing translations from the earlier pass, each catches most, but none catches all.

Which free checks flag the crashing translations

WeblatepofilterAndroid Lint
Flagged, of 366300322239
Not flagged27442
Outside the check's reach39 depend on the plural form-90 plurals not visited, 35 ignored
Flagged, of 237 formatted198215176
Census 0.2.0 rows after dropping date conversions, rows that print wrong text and a cleared repository. 12 crashing translations pass all three checks. Source: android-translation-crash-census CHECKS.md.

The blind spot has a shape. Weblate and pofilter recognise a % only when a conversion letter follows it, so a % before a space, a period or the end of the string passes, and that is exactly where the formatter throws. Lint never visits plural resources. Of the 24 crashing translations that pass both Weblate and pofilter, 22 are an extra lone %.

What it means

These crashes are cheap to prevent: run each translation through the real formatter in CI, or add a rule for a lone percent sign to the checks translators already use. Maintainers have confirmed the problem. Tallybook's maintainer reproduced a Turkish crash on an emulator, found it broke a settings screen as soon as it opened, a bug present since 2019, and merged the fix. We report crashes only where a project accepts such reports, and publish every row with a link to the line, so translators can fix the rest.

More research