You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Apple: adding or dropping a strings table changes CFBundleLocalizations but not the compatibility id, so an update can reach a binary with a stale language list #664
On Apple platforms the strings tables become the bundle's localizations: localizationKeys in host/apple/build.mjs writes CFBundleDevelopmentRegion and CFBundleLocalizations from reach.locales. That list is part of the signed Info.plist, but it is not a compatibility input. So an update that adds or drops a strings table keeps the compatibility id and can reach a binary whose declared languages are stale. iOS then keeps negotiating the app's language, and drawing its own controls, from the old list.
Steps:
An app with strings/en.json and strings/fr.json. Build and install the iOS binary.
Add strings/de.json.
Bake again. The compatibility id is the same, so the change ships as an update to the installed binary.
The installed binary's CFBundleLocalizations still lists only en and fr. On a device set to German, iOS negotiates the bundle's language from that list, so it never picks German, and the system's own words in the app (Back, Cancel, Edit) follow en.
Step 4 was not run as written. It follows from the stale CFBundleLocalizations and the docs' note that the system's words and chrome follow the table the system picks.
Cause
compatibility_id_pinned in bake/src/compat.rs records grants, purposes and other plist-bound inputs, but not the table names that reach::derive already reads into reach.locales.
How a fork fixed it
appandflow/exact#7: right after crate::reach::derive, a new localizations(platform, &mut compat) runs. On ios and macos, for an app with more than one table, it records localizations: {base, locales} as a compatibility input and recomputes the id. The plan requires it the way it requires grantPurposes (receipt.rs).
Adding or dropping a language is a binary release.
Editing a translation's text is not, because only the table names are recorded, never the text.
An app with one table, and every other platform, keeps the id it had, so existing cohorts don't move.
Tests: the_plists_languages_are_in_the_id (the id moves when a language is added, and not for a translation edit, a single table, or the web) and a_plan_requires_the_localizations_its_inputs_carry. docs/contract-for-agents.md says which edits need a new binary.
Not covered: changing strings.base in a one-table app moves CFBundleDevelopmentRegion without moving the id. Covering that would move every Apple app with a strings table into a new cohort, and the system's chrome falls back the same way either way.
Host
iOS, macOS
Smallest app that shows it
component App
view
column padding=16
text t("hello")
with strings/en.json and strings/fr.json each holding {"hello": "..."}, then a third table added after the binary ships.
Exact commit
f3a4ace. bake/src/compat.rs there has no localization input after crate::reach::derive.
Fixed in 1982dcc, following appandflow#7 by Janic Duplessis. An iOS or macOS app with more than one strings table now records localizations: {base, locales} in its compatibility id. So adding or dropping a table needs a new binary, while editing a translation still ships as an update. Push and deploy compare these inputs in both directions, so they catch a dropped table as well as an added one. Apple apps that already ship several tables move to a new cohort once. No other host has this gap: Android's localized channel names already enter the id through androidChannels, and Windows, Linux and the web list no locales.
Activity
ccheever commentedon Nov 15, 2026
Fixed in 1982dcc, following appandflow#7 by Janic Duplessis. An iOS or macOS app with more than one strings table now records
localizations: {base, locales}in its compatibility id. So adding or dropping a table needs a new binary, while editing a translation still ships as an update. Push and deploy compare these inputs in both directions, so they catch a dropped table as well as an added one. Apple apps that already ship several tables move to a new cohort once. No other host has this gap: Android's localized channel names already enter the id throughandroidChannels, and Windows, Linux and the web list no locales.Posted by Claude Code on the maintainers' behalf.
An Apple app's strings tables are in its compatibility id