Phrase Strings Releases 2025

Introduced support for additional metadata fields per key in the Strings catalog. These include comment, extractionState, and shouldTranslate. The placement of each field during import/export has been standardized, and Xcode translation states are now mapped to Phrase equivalents to improve compatibility.

Added a parameter to the translation versions API to filter for entries that include content changes, making it easier to trace meaningful updates.

Added support for automatic locale fallback during downloads/pull to avoid complex .phrase.yml setups, using the value from the locale settings.

Selecting all keys and then deselecting some keys at the editor now preserves correct selection and batch actions can be applied to it.

Figma plugin now allows users to select specific target languages during push when Figma preview is enabled. The modal remembers previous selections and provides flexibility for TMS and Strings use cases.

Added support for the ar-001 locale in Strings to better support integrations where ar-mod is unavailable.

Prevented auto job creation from AJC when Figma Live Preview is enabled to avoid duplicate job creation. Includes messaging updates and logic to support both modes.

Nested notranslate tags were not correctly unescaped, resulting in malformed MT output. This has been fixed.

A backend error in branch merge operations caused by inconsistent key structures during bulk insert. This has been fixed.

Global search and editor inconsistencies were occuring when querying translations in child keys. This has been fixed and results now include correct source/target data from both parent and child keys.

Unrelated actions were shown even when filters were applied. This has been fixed and filtering in the Activity tab now correctly limits results to matching event types.

There were major performance issues in the editor with large key sets, including forced refreshes, UI lag, and screen jumping. This has been fixed and improvements ensure smoother navigation and editing.

Locales with region codes (e.g. zh-TW) were not correctly identified as spaceless, unlike their base locale. This has been fixed.

It is now possible to apply organizational job templates when creating jobs from the translation editor.

If using automated job creation, active scheduled automations can now be manually triggered anytime by using the option Run automation now.

Job Sync:

Apostrophes were incorrectly rendered as entities when pre-translating from English to French using Google Translate. This has been fixed.

A Guest viewing permission could not be deselected for users assigned the Project Manager role. This has been fixed.

Key search in the Jobs page returned no results when key names contained the sequence :-. This has been fixed.

The In-Context Editor in the US data center was facing performance issues. This has been fixed.

The job name has been added to page titles for easier job navigation in tabs.

No job syncs were being displayed and a Syncing error message appeared when accessing the Job Sync page in Strings. This has been fixed.

Selecting a language for export triggered an error requiring users to Please fill out this field unnecessarily. This has been fixed.

The Customize download modal within jobs was not displaying properly making it unusable. This has been fixed.

Corrected behavior on project pages where after navigating to the next page, users were shown an empty screen until scrolling manually. This has been fixed.

The Job Syncs page now displays who originally created each connector in the Created by column.

The Upload a new file endpoint now supports the source_locale_id parameter, allowing more accurate locale matching during job sync processes.

Hidden layers or frames were included during content extraction from Figma, even when the plugin setting to exclude them was disabled.

The API incorrectly returned keys as untranslated due to invalid plural form handling for the German locale. This has been fixed.

Merging branches did not properly carry over translations into the main branch. This has been fixed.

Keys appeared as linked keys even after removing their connection to the parent key. This has been fixed.

The Create new link window would disappear when typing a parent key name. This has been fixed.

The placeholder %s in Right-To-Left (RTL) languages (e.g. Hebrew, Arabic) was incorrectly handled in the UI. This has been fixed.

The filtered jobs URL used an incorrect separator, causing filters to break when reusing the link in a new browser tab. This has been fixed.

Job annotations and job locale annotations can now be set in the job detail page.

The Job Syncs page is now available to list and configure job syncs with Phrase TMS directly in Strings.

GitLab sync operations would fail due to an invalid custom Git provider API endpoint error. This has been fixed.

Valid GitLab branches could not be selected during sync setup, despite API accessibility and proper permissions. This has been fixed.

The scrollbar in the Favorites section of the left-hand navigation menu was missing when too many favorite projects were listed. This has been fixed.

The list of languages supported by the Gengo integration for placing orders has been expanded to include 115 additional locales:

hr, zh-hk, ca, cy, lt, dt, ln, is, mn, be, bn, am, xh, lv, so, gu, pa, kn, ps, te, ha, mg, or, ka, lo, hy, ht, az, ns, ss, kk, tn, om, ig, ta, su, as, lg, jv, ku-so, ilo, luo, kea, mr, km, kac, ewo, tsg, bm, khq, umb, kg, cjk, dyu, ml, af, mk, sw, ur, zu, ar-ro, es-mx, dyu-r, taq-r, ta-ro, ak, gd, tt, tz, bo, ck, gn, iu, qu, se, chi, hi-ro, yo, wo, cb, ara, ff, te-ro, cat, ne, kmr, shn, wes, ti, taq, kmb, guz, kln, kam, cja, bs, fa, si, sl, sq, bn-ro, ay, sa, fo, mi, st, ge, ur-ro, eu, SR-RS, zh-SG, gan, EN-TT, et, NL-BE.

The Editor button is also available in the project list view of the Projects page for faster access to the String editor.

Spreadsheet files (.xlsx) downloaded from Phrase Strings failed to open in Google Drive preview and in Google Sheets after upload. This has been fixed.

Keys ending with an even number of backslashes were parsed incorrectly. This has been fixed.

The Figma plugin was freezing/crashing when closing the window or making changes. This has been fixed.

The ICU preview rendering for right-to-left languages displayed segments in the wrong order. This has been fixed.

The GitHub integration now supports repositories with more than 100,000 files or larger than 7 MB.

Previously, syncs relied on GitHub’s all files list, which is truncated for large repositories and caused incomplete imports. The new implementation queries only the required subfolders or files directly, avoiding truncation and ensuring that all files beyond the cutoff are correctly retrieved.

Key descriptions in the Strings editor could not be updated due to an error related to the linked key’s plural status. This has been fixed.

Improved context visibility during uploads by adding new statistics fields: Custom metadata fields created and Custom metadata fields updated. These are displayed for all uploads for customers with access to custom metadata feature.

New webhooks available:

A new version 3.10.5 of the Android SDK is now available.

A separate webhook is now sent for each plural form when marking a pluralized key as reviewed.

When using the Phrase Strings connector, a source mismatch was incorrectly detected despite identical content. This has been fixed.

DeepL machine translation would not return translations when translating from en-WW to en-GB, despite it being supported. This has been fixed.

Unicode-escaped emojis (e.g. \uD83D\uDE1E) were replaced by whitespace during file upload. This has been fixed.

Creating jobs from templates triggered an internal server error. This has been fixed.

The string count in the editor displayed more strings than actually existed in a project. This has been fixed.

Unity plugin: PhraseMetadata tags caused runtime exceptions in standalone builds. This has been fixed.

Introduced the updated_since filter for downloads to better control data export based on updates. Improvements include examining what types of updates trigger filtering (e.g., translation changes vs. key updates), performance considerations, and aligning backend logic with the UI and documentation.

Webhook payloads now include a sent_at timestamp field. This enhancement supports more precise tracking and debugging of webhook events. Related documentation and example schemas have been updated accordingly.

The translation_key_prefix field in configuration .YML files worked via CLI but not with automated GitHub repo sync. This has been fixed.

Omitting the point_of_contact field in a PATCH request unintentionally set it to null. The field now remains unchanged unless explicitly set. This has been fixed.

Keys with {} as source content were not populated after export from TMS. Improvements now correctly distinguish ICU plural formats to avoid misinterpretation. This has been fixed.

Single-select custom metadata values containing spaces could not be applied in the editor due to validation errors. This has been fixed.

Newly created custom metadata values were incorrectly preselected when batch-editing custom metadata in the editor. This has been fixed.

Applying a job template would clear preselected translation keys and associated metadata in the job settings. This has been fixed.

Branch-specific keys were displayed in global search results even if branching was not included in the subscription plan. This has been fixed.

Translation overdue and Revision overdue filters were not working in the Jobs page. This has been fixed.

The Share translation memory setting was not preserved when duplicating a project. This has been fixed.

The translation_key_prefix in the .phrase.yml configuration file was not applied during automated GitHub repo sync. This has been fixed.

Deleted translation keys were causing count mismatches and pagination errors. This has been fixed.

It was not possible to batch unverify translations due to timeout errors. This has been fixed.

Empty cells in uploaded .XLSX files were incorrectly populated. This has been fixed.

Users can now define job automations that pick up content, create jobs, and kick off translations with no manual work.

Phrase Language AI is now available as a machine translation option.

Merging branches were falsely triggering conflict warnings even when no edits were made on the main branch. This has been fixed.

The <small> tag was not properly escaping during .XLIFF export, unlike other inline tags. This has been fixed.

Infinite query loops were caused when GraphQL returned invalid responses. A safeguard mechanism has been implemented. This has been fixed.

As of June 11, 2025, legacy SSO logins will no longer be supported in Phrase. Users will no longer be able to access Phrase Strings in web browsers using SSO configurations set up directly in Strings. To continue logging in, organizations must set up Platform SSO or use alternative methods such as email/password or supported social logins (Google, Microsoft, GitHub). This change improves security and enables a unified login experience across the Phrase Platform.

The Verify mentioned translations option is now available when uploading localization files.

New API endpoints have been introduced to unreview translations individually or in bulk using queries.

Usernames containing spaces could not be mentioned in job comments. This has been fixed.

Branch creation was failing in some projects. This has been fixed.

Newly created tags were not visible when switching to a different key in the editor, requiring a page refresh. This has been fixed.

It was not possible to see replies to comments from the Activity tab of the editor sidebar, nor to which key the reply belonged. This has been fixed.

Syncing repositories caused an encoding compatibility error due to a mismatch between UTF-8 and UTF-16 encodings. This has been fixed.

The Custom metadata page showed an incorrect number of assigned projects. This has been fixed.

The status bar in the Projects page showed reviewed translations even when the Basic review workflow was selected. This has been fixed.

Selecting one tag in the Query builder inadvertently selected two additional tags. This has been fixed.

Loading jobs after adding keys resulted in a 504 gateway error time out. This has been fixed.

Filtering job templates by type was not working. This has been fixed.

Translations on child keys in languages not present in the parent key can now be created and edited.

Newly created tags in the editor were not appearing in the tag suggestions when switching to another key. This has been fixed.

Exporting in xcstrings format through repository syncs would result in separate files per language instead of a single consolidated file as expected. This has been fixed.

Selecting a tag via the query builder's checkbox in the editor unintentionally selected adjacent tags. This has been fixed.

Support for Unicode CLDR version 47 has been added and set as the new default for pluralization. This update ensures the latest standard is used for all projects in Strings.

Uploading files containing pluralized keys with mentioned null plural forms triggered a runtime error due to improper handling of content hashes. This has been fixed.

Search input in the query builder was automatically copied into all open tabs instead of staying tab-specific. This has been fixed.

The exported plural form one would incorrectly contain content from the other form in linked keys. This has been fixed.

A pre-translation could unverify already translated keys and keys appeared both pre-translated and untranslated at once in certain filters. This has been fixed.

Screenshots in the Figma plugin were not uploaded to projects due to frame structure mismatches. This has been fixed.

In projects with branching enabled, saving translations in secondary branches sometimes triggered an error about translation not found. This has been fixed.

The Enterprise Quality setting was causing a problem in TextMaster translation orders. This has been fixed.

Creating a translation order from English to Russian via TextMaster resulted in an unsupported language error. This has been fixed.

Wrapped quotation marks in target strings were removed when the translation was reimported through Job Sync. This has been fixed.

Apple Strings Catalog (.XCSTRINGS) is now supported.

Project-based job templates can now be applied when creating jobs in the translation editor.

There is a new Update translations on source match option on import that ensures that target translations are updated only when the source text matches existing content.

Figma:

Pressing the Enter key in the editor triggered a pop-up instead of inserting a new line. This has been fixed.

Searching for keys by tags did not work when manually typing the tag name after tag. This has been fixed.

Translation not found error appeared upon saving translations, despite the translations being successfully saved. This has been fixed.

Unverified keys were not shown in the editor, despite being present in the project overview. This has been fixed.

When Turkish was selected in the language filter, keys associated with a specific tag were not displayed. This has been fixed.

The unverified translations count in analytics was taking up to two days to update. This has been fixed.

CDATA content in Android XML exports was incorrectly escaped when using OTA. This has been fixed.

Translations were not updated when merging a branch into the main branch. This has been fixed.

The dropdown list of tags in the editor sidebar did not function properly when searching for existing tags. This has been fixed.

Mentions in comments did not work correctly for users with spaces in their usernames, preventing proper tagging and notifications. This has been fixed.

When syncing a plural form translation from a parent key, the translation incorrectly propagated to all plural forms in child keys. This has been fixed.

Auto-translate was not applied to CLI imports despite being enabled in both the config file and project settings. This has been fixed.

Microsoft Translate did not function for translations from en-GB to no-NO or no. This has been fixed.

The untranslated filter did not correctly display untranslated keys, even after recalculating stats. This has been fixed.

Selecting an existing tag after typing in the Tags field removed all previously assigned tags. This has been fixed.

A branch merge resulted in a could not be created error, preventing completion of the translation process. This has been fixed.

Clicking the search bar in the editor caused the entire browser to freeze or crash. This has been fixed.

Clicking on Translate tagged keys did not display any results unless a space was manually added after the tag. This has been fixed.

The Log in with SSO button has been removed from the legacy login page. Accessing the legacy login page will result in an automatic redirect to the Platform login page after a short delay. Users from organizations without a Platform SSO setup can gain access by:

The tag search pop-up was flashing repeatedly until the full list was loaded. This has been fixed.

Jobs created via API used the template creator as the Job owner instead of the selected Job owner. This has been fixed.

Searching for tags in the editor was slow in projects with many tags. This has been fixed.

Pressing Enter in the editor would open a view instead of inserting a new line. This has been fixed.

The response schema for Upload objects did not include the tags field. This has been fixed.

Array keys were incorrectly exported as strings instead of arrays in the target file. This has been fixed.

The Figma tag was not applied to all keys when pushing content from Figma. This has been fixed.

Unverified translations in analytics were taking too long to update. This has been fixed.

Starting a job via API returned an incorrect validation error instead of the expected job was already started message. This has been fixed.

CDATA blocks in Android XML was incorrectly exporting escaped characters despite being inside CDATA. This has been fixed.

A database error was occurring due to excessive data length in the log column. This has been fixed.

Query builder results increased unexpectedly when filtering by custom metadata. This has been fixed.

Translations were not being updated after merging a branch into the main branch. This has been fixed.

Using the batch action to exclude keys was not updating empty strings. This has been fixed.

The locale_mapping parameter was not being processed correctly in .CSV imports via CLI 2.35. This has been fixed.

Some missing terms were flagged in the editor but were not displayed in the quality assurance issues list. This has been fixed.

Exporting translations to GitHub was failing due to a missing translation status error. This has been fixed.

False positive QA issues were appearing on the auality assurance tab due to pluralized keys. This has been fixed.

Auto-translation was not being triggered during CLI imports despite being enabled in settings. This has been fixed.

A splash screen has been implemented on the legacy login page, automatically redirecting users to the Phrase Platform login after 5 seconds. Users have the option to cancel the redirect and remain in the current login environment.

i18next translation syntax placeholders are now supported in the Strings editor, enabling recognition and highlighting of nested translation patterns for improved web application localization workflow.

Users are now notified when reaching the 65,000 keys display limit in the Strings editor.

The editor key list now shows icons of the excluded keys at first glance.

Not all keys were visible in the scrollable list when creating a new job, requiring users to search for specific keys instead. This has been fixed.

In some cases, one file out of 300 could get stuck during processing when using the API upload tool. This has been fixed.

The Languages tab of Phrase Analytics was displaying deleted spaces. This has been fixed.

Certain locales were missing in packages exported for translation via FTP connector. This has been fixed.

The Keys unmentioned statistics were not working correctly when using translation_key_prefix during file uploads. This has been fixed.

The placeholder suggestion dropdown in the Strings editor was not displaying correctly. This has been fixed.

Merging sub-branches into the main branch was not possible due to unresolved conflicts. This has been fixed.

The Save and Review button was verifying translations, but not setting them as reviewed in the Strings editor. This has been fixed.

The Languages tab of the project page now supports hundreds of languages with a cleaner design, better filters, and smoother navigation.

Key features:

Strings editor:

Upload IDs are now displayed in the uploads list and details page. Users can copy the IDs and search for them to track specific uploads.

TextMaster translation orders with unsupported language combinations now display clear error messages when quality control services are not available for specific language pairs.

Completed translation orders were not showing translated content in the Orders tab. This has been fixed.

The Suggestions menu in the editor sidebar was not showing complete results on the first click, requiring multiple key selections to display all available suggestions. This has been fixed.

Screenshots from the Figma plugin were appearing in random order within the editor instead of maintaining a consistent design-first approach. This has been fixed.

It was not possible to sort favorite projects by name. This has been fixed.

Mentions in comments followed by punctuation were not being added correctly. This has been fixed.

CSV uploads via CLI failed to process custom metadata due to invalid values. This has been fixed.

The system was creating duplicate languages when importing XLIFF files with the same language code but different names. This has been fixed.

HTML characters in key descriptions were not being properly escaped during XLIFF export. This has been fixed.

The Figma plugin was detecting hidden layers even when the Include hidden layers option was disabled. This has been fixed.

MT engines were not functioning correctly with specific locale combinations. This has been fixed.

The Languages tab of the Phrase Analytics page was displaying outdated spaces information. This has been fixed.

Job context failed to appear in the editor sidebar when using Single key view mode. This has been fixed.

Translators were receiving notifications about events in languages they were not assigned to work with. This has been fixed.

Tooltip timestamps were not matching the time zone selected in user settings. This has been fixed.

Search queries were not properly handling case sensitivity setting in the editor. This has been fixed.

File import created duplicate keys and displayed incorrect character encoding when downloading in iOS Localizable Stringsdict format. This has been fixed.

Downloading content filtered by job tags was resulting in system timeouts. This has been fixed.

Translations of linked keys were not synced. This has been fixed.