New Crowdin updates

[feruzm]

Summary by CodeRabbit

• New Features

  • UI strings for an AI Image Generator added (prompts, buttons, status, errors).
  • New wallet/dropdown action: "AI Image" alongside Transfer, Promote, Boost.

• Localization

  • Added a server-configuration hint to date/time error messages across locales.
  • Locale updates and minor punctuation tweaks to surface the new texts.

[coderabbitai]

Note

Due to the large number of review comments, Critical severity comments were prioritized as inline comments.

♻️ Duplicate comments (5)

src/config/locales/fr-FR.json (1)

224-225: ⚠️ Potential issue | 🟠 Major

Do not manually edit non-en-US locale files in this PR.

These additions in src/config/locales/fr-FR.json (Line 224, Line 971, Line 1146 blocks) should be reverted and applied in src/config/locales/en-US.json only, then synchronized via Crowdin.

Based on learnings: “In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.”

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/fr-FR.json` around lines 224 - 225, The PR accidentally
modifies non-en-US locale files: revert the manual edits in
src/config/locales/fr-FR.json (remove the added keys like "current_time" and
"server_hint" and the other blocks at the ranges you noted: 971-974 and
1146-1170) and instead add these new/updated translation keys only to
src/config/locales/en-US.json; once en-US is updated, leave other locale files
untouched and let the Crowdin synchronization propagate translations to fr-FR
and others.

src/config/locales/pa-IN.json (3)

224-225: ⚠️ Potential issue | 🟠 Major

Revert direct edits in non-en-US locale file.

These key changes are in src/config/locales/pa-IN.json; they should be added in src/config/locales/en-US.json and propagated via Crowdin instead of being edited directly here.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/pa-IN.json` around lines 224 - 225, Revert the manual
edits to the pa-IN.json locale (remove the added/modified keys "current_time"
and "server_hint") and instead add those keys and their English strings to the
en-US.json locale file; after committing the change to en-US.json, leave
pa-IN.json untouched so the translations will be propagated via Crowdin (do not
directly edit any non-en-US locale files like pa-IN.json).

---

971-974: ⚠️ Potential issue | 🟠 Major

Do not add wallet.dropdown_* keys directly to pa-IN.json.

Please move these additions to src/config/locales/en-US.json and let Crowdin sync localized files.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/pa-IN.json` around lines 971 - 974, Remove the four added
translation keys ("dropdown_transfer", "dropdown_promote", "dropdown_boost",
"dropdown_ai_image") from pa-IN.json and instead add them to en-US.json so
Crowdin can propagate translations; ensure you only modify en-US.json for
new/updated keys and revert the changes in pa-IN.json before committing.

---

1146-1170: ⚠️ Potential issue | 🟠 Major

ai_image_generator block should not be introduced directly in pa-IN.json.

Add this block in src/config/locales/en-US.json only, then rely on Crowdin synchronization for pa-IN.json.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/pa-IN.json` around lines 1146 - 1170, Remove the newly
added "ai_image_generator" localization block from pa-IN.json (do not manually
edit other locale files) and instead add that exact block under the root locale
keys in en-US.json so Crowdin can propagate translations; locate the block by
the "ai_image_generator" key and ensure the strings match the diff, then restore
pa-IN.json to its previous/synced state so only en-US.json contains the new
entries.

src/config/locales/da-DK.json (1)

224-225: ⚠️ Potential issue | 🟠 Major

Revert manual edits in non-en-US locale file.

Line 224, Line 971, and Line 1146 modify locale keys directly in src/config/locales/da-DK.json. Please keep key additions in src/config/locales/en-US.json only and let Crowdin sync propagate translations.

Based on learnings: “In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.”

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/da-DK.json` around lines 224 - 225, Revert the manual
changes in the Danish locale by removing the direct edits to the translation
keys (e.g., "current_time" and "server_hint" and any other keys you modified in
da-DK.json) so that da-DK.json remains untouched; instead add or update the keys
only in en-US.json (the source of truth) and let Crowdin propagate translations.
Ensure da-DK.json is restored to its previous state (undo your edits around the
affected keys) and commit only the en-US.json changes going forward.

🟠 Major comments (32)

src/config/locales/mk-MK.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Non-en-US locale is being edited directly, which breaks the localization workflow.

These changes are in src/config/locales/mk-MK.json, but this repo’s flow requires manual key updates in src/config/locales/en-US.json only, with other locales synced via Crowdin. Please move/update keys in en-US.json and let Crowdin propagate them.

Based on learnings: "In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests."

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/mk-MK.json` around lines 224 - 225, You've edited
non-en-US locale files directly (e.g., src/config/locales/mk-MK.json) — revert
those manual changes and instead add or update the same translation keys (e.g.,
"current_time" and "server_hint") in src/config/locales/en-US.json only; remove
any direct edits in mk-MK.json and the other ranges mentioned (around lines
971-974 and 1146-1170) so Crowdin can propagate translations automatically.
Locate the keys by name in the diff and ensure the canonical additions/updates
are made in en-US.json; do not commit changes to other locale files.

src/config/locales/lv-LV.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Revert manual locale edits in lv-LV.json and move key changes to en-US.json only.

These additions (Line 224, Line 971, and Line 1146) are in a non-source locale file. Please remove src/config/locales/lv-LV.json changes from this PR and add/update the keys only in src/config/locales/en-US.json so Crowdin can propagate them.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/lv-LV.json` around lines 224 - 225, Revert the manual
edits in src/config/locales/lv-LV.json (remove the added/changed keys such as
"current_time" and "server_hint" and the other key blocks at the ranges
referenced) so that this locale file is unchanged in the PR, and instead add or
update those same keys in src/config/locales/en-US.json only; ensure you add the
exact key names ("current_time", "server_hint", and the keys from the blocks
referenced at 971-974 and 1146-1170) with their English values in en-US.json so
Crowdin can propagate translations, then commit the revert for lv-LV.json and
the corresponding edits to en-US.json.

src/config/locales/he-IL.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Revert manual edits in he-IL.json and move source-key changes to en-US.json only.

Line 224, Line 225, Line 971–Line 974, and Line 1146–Line 1170 should not be edited directly in this repo workflow. These keys should be introduced/updated in src/config/locales/en-US.json, then synced to other locales via Crowdin.

Suggested diff for this file (revert local manual additions)

@@
-      "current_time": "Current time;",
-      "server_hint": "You can also try changing API Server in Settings > Server."
+      "current_time": "Current time;"
@@
-    "dropdown_transfer": "Transfer",
-    "dropdown_promote": "Promote",
-    "dropdown_boost": "Boost",
-    "dropdown_ai_image": "AI Image",
@@
-  "ai_image_generator": {
-    "title": "AI Image Generator",
-    "prompt_label": "Describe the image you want to create",
-    "prompt_placeholder": "A beautiful sunset over mountains...",
-    "chars_remaining": "{count} characters remaining",
-    "select_aspect_ratio": "Select aspect ratio",
-    "cost_label": "Cost",
-    "balance_label": "Balance",
-    "points_unit": "POINTS",
-    "generate_button": "Generate Image",
-    "generating": "Generating your image...",
-    "result_title": "Generated Image",
-    "insert_button": "Insert into post",
-    "download_button": "Download",
-    "share_button": "Share",
-    "generate_again": "Generate Again",
-    "success": "Image generated successfully!",
-    "error_insufficient_points": "Insufficient points. You need {required} but have {available}.",
-    "error_content_policy": "Your prompt was rejected by content policy. Points were not refunded.",
-    "error_rate_limit": "Too many requests. Please wait and try again.",
-    "error_generic": "Image generation failed. Please try again.",
-    "error_prompt_required": "Please enter a prompt",
-    "use_suggestion": "Use: \"{suggestion}\"",
-    "dropdown_label": "AI Image"
-  },

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/he-IL.json` around lines 224 - 225, The he-IL locale file
was manually edited—undo the manual additions for the keys "current_time" and
"server_hint" (and the other ranges mentioned: keys at 971–974 and 1146–1170) by
reverting those changes in this locale, and instead add or update the
corresponding source keys only in en-US.json so Crowdin can propagate them;
locate the entries "current_time" and "server_hint" in
src/config/locales/he-IL.json (and the keys in the referenced ranges), remove or
revert the manual edits there, then make the intended key additions/changes in
en-US.json so the localization workflow remains consistent.

src/config/locales/bn-BD.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Do not manually edit non-en-US locale files

Line 224-225, Line 971-974, and Line 1146-1170 introduce manual key updates in src/config/locales/bn-BD.json. In this repository, translation key additions/updates should be made only in src/config/locales/en-US.json; other locale files are Crowdin-synced. Please revert these manual changes from bn-BD.json and keep source-string updates in en-US.json only.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/bn-BD.json` around lines 224 - 225, Revert the manual
additions/edits in bn-BD.json and restore the original Crowdin-synced content,
removing the manually added translation keys such as "current_time" and
"server_hint" (and the other keys added in the same change set), and instead add
or update those keys only in src/config/locales/en-US.json so the translations
stay authoritative in the source locale; ensure bn-BD.json no longer contains
your manual changes before committing so Crowdin remains the single source for
localized files.

src/config/locales/ceb-PH.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Do not manually edit non-en-US.json locale files

These additions are in src/config/locales/ceb-PH.json, but this repository’s localization flow requires adding/updating keys only in src/config/locales/en-US.json; other locales should be synced by Crowdin. Please move these key changes to en-US.json and revert this locale file from the PR.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/ceb-PH.json` around lines 224 - 225, Revert the manual
edits in the non-en locale (remove the added keys "current_time" and
"server_hint" from ceb-PH.json and undo the other manual changes referenced),
and instead add or update those keys only in src/config/locales/en-US.json
(e.g., add "current_time" and "server_hint" entries there); ensure all other
locale files are left untouched so Crowdin can sync translations automatically.

src/config/locales/ur-IN.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Do not manually edit non-en-US.json locale files in this repo.

This PR directly updates src/config/locales/ur-IN.json (for example at Line 224, Line 971, and Line 1146). Locale key additions/changes should be made in src/config/locales/en-US.json only, then synced via Crowdin. Please move these additions there and remove manual edits from this file.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files are automatically synchronized via Crowdin integration.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/ur-IN.json` around lines 224 - 225, Remove the manual
edits from the ur-IN locale (the added/changed keys "current_time" and
"server_hint" and any other edits at the noted ranges) and instead add those
keys/updates to src/config/locales/en-US.json so Crowdin can propagate
translations; specifically, revert changes in ur-IN.json and place the new
keys/values into en-US.json (matching key names "current_time" and
"server_hint") then commit en-US.json only so the Crowdin sync updates other
locale files.

src/config/locales/sv-SE.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Do not commit manual key updates in sv-SE.json.

These additions/edits belong in src/config/locales/en-US.json only; non-en-US locale files are Crowdin-synced and should not be manually changed in PRs. Please revert this file from the PR and keep source key updates in en-US.json.

Based on learnings: In the ecency-mobile repository, only en-US.json should be modified for translation key updates; other locale files are automatically synchronized via Crowdin.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/sv-SE.json` around lines 224 - 225, Revert the manual
translation key changes in sv-SE.json (remove the added/edited keys such as
"current_time" and "server_hint" and any other edits in the indicated ranges)
because non-en-US locales are Crowdin-managed; instead make your source key
additions/edits only in en-US.json (update src/config/locales/en-US.json with
the new/changed keys), then update the PR so sv-SE.json remains unchanged.

src/config/locales/sl-SI.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Do not manually edit non-source locale files in this PR

This file (src/config/locales/sl-SI.json) includes direct key additions/updates. Please move translation-key source changes to src/config/locales/en-US.json and let Crowdin sync sl-SI.json automatically, otherwise localization drift and overwrite churn can occur.

Based on learnings: In this repository, only en-US.json should be modified for translation key updates, and all other locale files are synchronized via Crowdin integration.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/sl-SI.json` around lines 224 - 225, Revert the manual
edits in src/config/locales/sl-SI.json (remove the added/updated keys
"current_time" and "server_hint" and any other manual changes at the noted
ranges), then add/update those translation-key additions only in
src/config/locales/en-US.json so Crowdin can propagate them; ensure you do not
modify any non-source locale files directly and leave sl-SI.json to be synced by
Crowdin.

src/config/locales/fil-PH.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Revert manual updates in fil-PH.json and move key changes to en-US.json only.

These edits are in a non-source locale file. Per your repo workflow, translation keys should be added/updated only in src/config/locales/en-US.json, then propagated by Crowdin; keeping these manual changes here risks drift/overwrite.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/fil-PH.json` around lines 224 - 225, Revert the manual
edits in the fil-PH locale file (remove the added/modified keys such as
"current_time" and "server_hint" and any other manual changes in this file) and
instead add or update those translation keys only in
src/config/locales/en-US.json; keep fil-PH.json unchanged so Crowdin can manage
translations, and remove any duplicated key changes elsewhere in fil-PH (the
other manual edit blocks referenced) to avoid drift.

src/config/locales/fi-FI.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Do not manually update fi-FI locale keys in this PR

These key additions/updates are in src/config/locales/fi-FI.json, but this repo’s localization flow expects source key changes in src/config/locales/en-US.json only, with other locales synced via Crowdin. Please move/restrict these changes to en-US.json and drop direct edits in fi-FI.json.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration and should not be manually edited in pull requests.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/fi-FI.json` around lines 224 - 225, The PR incorrectly
modifies fi-FI locale keys ("current_time", "server_hint" and the other ranges
noted); instead, revert/remove these edits from src/config/locales/fi-FI.json
and apply the key additions/updates only to src/config/locales/en-US.json (the
canonical source for translations) so Crowdin sync will propagate them; ensure
you remove the semicolon typo in the "current_time" value when moving the change
and commit only en-US.json changes while leaving fi-FI.json unchanged.

src/config/locales/id-ID.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Revert manual edits in this non-en-US locale file.

These additions are in src/config/locales/id-ID.json, but this repository’s localization flow requires new/updated keys to be made only in src/config/locales/en-US.json and synced via Crowdin. The new values here are also English, which can introduce mixed-language UI in Indonesian locale.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/id-ID.json` around lines 224 - 225, Revert the manual
edits in the Indonesian locale file by removing or restoring the modified keys
"current_time" and "server_hint" (and the other ranges mentioned) so they no
longer contain English strings; instead, leave those keys unchanged (or remove
them) so translations are maintained from the canonical en-US source and synced
via Crowdin. Ensure you do not introduce new/updated keys directly in non-en-US
locale files—make changes in en-US.json only and let the localization pipeline
propagate them.

src/config/locales/sq-AL.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Move these localization key changes to en-US.json only

These key additions/updates should not be made in src/config/locales/sq-AL.json; please revert this file’s edits and add/update keys only in src/config/locales/en-US.json for Crowdin sync flow.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; other locale files are auto-synchronized via Crowdin.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/sq-AL.json` around lines 224 - 225, Revert the
additions/edits that added the localization keys "current_time" and
"server_hint" (and any other unintended key changes in this sq-AL file) so
sq-AL.json matches the original localized file, then add or update those keys
only in en-US.json; specifically remove the two keys from the sq-AL locale, add
the exact keys "current_time" and "server_hint" with their English values into
src/config/locales/en-US.json, and ensure no other locale files are modified
(this also applies to the other unintended key edits noted).

src/config/locales/bs-BA.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Avoid manual translation-key changes in non-en-US locale files.

Line 224–Line 225, Line 971–Line 974, and Line 1146–Line 1170 add new keys in src/config/locales/bs-BA.json. In this repo’s localization flow, these keys should be added/updated in src/config/locales/en-US.json only, then synchronized via Crowdin. Please move these key changes to en-US.json and revert this file to prevent localization drift/conflicts.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/bs-BA.json` around lines 224 - 225, The bs-BA locale file
was manually changed to add translation keys (e.g., "current_time",
"server_hint" and the other keys added around the ranges mentioned); revert all
manual edits in src/config/locales/bs-BA.json so it matches the synced Crowdin
copy, and instead add or update those new keys only in
src/config/locales/en-US.json (create the keys with English source text there);
do not keep any new key additions in non-en-US files to avoid localization
drift.

src/config/locales/yo-NG.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Please avoid manual updates in yo-NG.json; update en-US.json only.

These additions should be made in src/config/locales/en-US.json and propagated via Crowdin, not committed directly in non-en-US locale files.

Suggested patch for this file (revert manual locale edits)

@@
-      "current_time": "Current time;",
-      "server_hint": "You can also try changing API Server in Settings > Server."
+      "current_time": "Current time;"
@@
-    "boost": "Boost",
-    "dropdown_transfer": "Transfer",
-    "dropdown_promote": "Promote",
-    "dropdown_boost": "Boost",
-    "dropdown_ai_image": "AI Image",
+    "boost": "Boost",
@@
-  "ai_image_generator": {
-    "title": "AI Image Generator",
-    "prompt_label": "Describe the image you want to create",
-    "prompt_placeholder": "A beautiful sunset over mountains...",
-    "chars_remaining": "{count} characters remaining",
-    "select_aspect_ratio": "Select aspect ratio",
-    "cost_label": "Cost",
-    "balance_label": "Balance",
-    "points_unit": "POINTS",
-    "generate_button": "Generate Image",
-    "generating": "Generating your image...",
-    "result_title": "Generated Image",
-    "insert_button": "Insert into post",
-    "download_button": "Download",
-    "share_button": "Share",
-    "generate_again": "Generate Again",
-    "success": "Image generated successfully!",
-    "error_insufficient_points": "Insufficient points. You need {required} but have {available}.",
-    "error_content_policy": "Your prompt was rejected by content policy. Points were not refunded.",
-    "error_rate_limit": "Too many requests. Please wait and try again.",
-    "error_generic": "Image generation failed. Please try again.",
-    "error_prompt_required": "Please enter a prompt",
-    "use_suggestion": "Use: \"{suggestion}\"",
-    "dropdown_label": "AI Image"
-  },

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/yo-NG.json` around lines 224 - 225, Revert the manual
translations added to yo-NG.json (the "current_time" and "server_hint" keys) and
instead add or update those keys in src/config/locales/en-US.json; ensure only
en-US.json is edited locally and rely on Crowdin to propagate changes to other
locale files like yo-NG.json (do not commit manual edits to non-en-US locale
files), and check any other non-en-US files referenced in the review (e.g., the
ranges noted) and remove manual changes there as well so translations remain
controlled via en-US.json + Crowdin.

src/config/locales/sa-IN.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Revert manual edits in non-en-US locale file.

Line 224, Line 971, and Line 1146 introduce translation-key changes directly in src/config/locales/sa-IN.json. These updates should be made in src/config/locales/en-US.json only, with Crowdin handling downstream locale sync.

Based on learnings: “In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.”

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/sa-IN.json` around lines 224 - 225, Revert the manual
edits in src/config/locales/sa-IN.json: undo the changes to the translation keys
introduced (e.g., "current_time" and "server_hint" and the other edits in the
ranges noted around lines 971–974 and 1146–1170) so this locale file remains
untouched; instead make any new or changed translation-key additions in
src/config/locales/en-US.json only, then let Crowdin propagate translations to
sa-IN and other locales.

src/config/locales/ta-IN.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Revert manual edits in non-en-US locale file.

Line 224, Line 971, and Line 1146 contain direct translation-key updates in src/config/locales/ta-IN.json. Please move these key additions to src/config/locales/en-US.json and rely on Crowdin synchronization for localized files.

Based on learnings: “In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.”

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/ta-IN.json` around lines 224 - 225, Revert the manual
additions/edits of the translation keys in the ta-IN.json locale (specifically
remove the direct changes for "current_time" and "server_hint" and the other key
ranges mentioned) and instead add those new/updated keys to the en-US.json
locale file so Crowdin can propagate translations; ensure you remove the manual
entries from ta-IN.json and place identical key names and English strings into
en-US.json (so keys like "current_time" and "server_hint" appear only in
en-US.json), then leave localized files for Crowdin sync.

src/config/locales/sr-CS.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Revert manual edits in non-en-US locale file.

Line 224, Line 971, and Line 1146 add translation keys directly in src/config/locales/sr-CS.json. Please revert this file’s locale-key edits and apply them only in src/config/locales/en-US.json, then let Crowdin sync propagate.

Based on learnings: “In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.”

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/sr-CS.json` around lines 224 - 225, Revert the manual
additions in the Serbian locale file by removing the added translation keys
(e.g., "current_time" and "server_hint" plus the other inserted blocks) from
sr-CS.json, then add those keys only to the en-US.json locale file so Crowdin
can propagate translations; ensure no other non-en-US locale files are changed
and leave Crowdin to sync the rest.

src/config/locales/es-AR.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Revert manual edits in non-en-US locale file.

Line 224, Line 971, and Line 1146 add/update locale keys directly in src/config/locales/es-AR.json. These should be introduced in src/config/locales/en-US.json only and synced to other locales through Crowdin.

Based on learnings: “In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files (e.g., es-ES.json, de-DE.json, etc.) are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.”

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/es-AR.json` around lines 224 - 225, Revert the manual
translation edits in the non-English locale (remove the added/updated keys such
as "current_time" and "server_hint" and the other recent manual entries in
es-AR.json), and instead add those new/updated keys only in en-US.json so they
flow through Crowdin; ensure the es-AR.json changes are undone (restore from
last committed version) and commit the new keys into en-US.json only so the
localization pipeline can sync them.

src/config/locales/uz-UZ.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Revert these non-en-US.json localization edits.

Line 224-225, Line 971-974, and Line 1146-1170 manually add/update locale keys in src/config/locales/uz-UZ.json. Please drop this file from the PR and keep key-definition changes in src/config/locales/en-US.json only.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/uz-UZ.json` around lines 224 - 225, Revert all manual
edits in src/config/locales/uz-UZ.json (including the added/modified keys such
as "current_time" and "server_hint" and the changes around the ranges you
flagged: ~lines 224-225, 971-974, 1146-1170) by removing those key
additions/updates from this file and restore it to the upstream/branch version;
instead make any new or updated localization key definitions only in
src/config/locales/en-US.json so Crowdin can propagate translations
automatically.

src/config/locales/az-AZ.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Please keep this locale file untouched and let Crowdin sync it.

Line 224-225, Line 971-974, and Line 1146-1170 contain direct key updates in src/config/locales/az-AZ.json. These changes should be removed from this PR; update en-US.json only.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/az-AZ.json` around lines 224 - 225, Remove the direct
edits to the az-AZ.json locale file and restore the original content for the
affected keys ("current_time" and "server_hint") as well as the other changed
blocks (lines referenced around 971-974 and 1146-1170); only make translation
key additions/updates in en-US.json so Crowdin can propagate them—revert the
changes in src/config/locales/az-AZ.json and ensure your intented key additions
exist only in en-US.json before committing.

src/config/locales/ac-ace.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Revert manual locale edits outside en-US.json.

Line 224-225, Line 971-974, and Line 1146-1170 add keys directly in a non-en-US.json locale file. Please remove these changes from this file and keep key additions only in src/config/locales/en-US.json so Crowdin can propagate translations.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/ac-ace.json` around lines 224 - 225, Remove the manually
added translation keys from ac-ace.json (e.g., "current_time", "server_hint" and
the other keys you added in the blocks at lines referenced) and instead add any
new or updated keys only to en-US.json so Crowdin can propagate translations;
locate the additions in ac-ace.json (search for "current_time" and "server_hint"
and the blocks around the other ranges) and delete them, then ensure the
canonical key entries exist in en-US.json only.

src/config/locales/hr-HR.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

This Crowdin-managed locale file should not be manually updated in this PR.

Line 224-225, Line 971-974, and Line 1146-1170 introduce manual translation-key edits in src/config/locales/hr-HR.json. Please revert this file from the PR and keep source-key updates in src/config/locales/en-US.json only.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/hr-HR.json` around lines 224 - 225, Revert all manual
edits from the hr-HR locale (the keys like "current_time" and "server_hint" plus
the other translation-key edits around those ranges) so this Crowdin-managed
file is unchanged in the PR and keep any source-key updates only in en-US.json;
specifically remove the manual additions/changes in the hr-HR.json file (the
translation keys mentioned in the review) and restore the file to its pre-PR
state, then ensure your intended new/updated keys are present only in
src/config/locales/en-US.json before re-submitting the PR.

src/config/locales/ca-ES.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Manual edits in ca-ES.json should be removed from this PR.

Line 224-225, Line 971-974, and Line 1146-1170 modify translation keys in a Crowdin-managed locale file. Please revert this file and keep these additions in src/config/locales/en-US.json only.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/ca-ES.json` around lines 224 - 225, Revert the manual
translation edits in ca-ES.json (remove the added/modified keys such as
"current_time" and "server_hint" and any other edits made in this PR) and leave
those translation key changes only in en-US.json; restore ca-ES.json to its
Crowdin-synced state so that only en-US.json contains the new or updated keys
and no other locale files are modified.

src/config/locales/gl-ES.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Please don’t introduce new keys directly in gl-ES.json.

These additions should be made in src/config/locales/en-US.json and synced to other locales through Crowdin to keep localization flow consistent.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/gl-ES.json` around lines 224 - 225, You added new
localization keys ("current_time" and "server_hint") directly in
src/config/locales/gl-ES.json; instead remove these entries from gl-ES.json and
add the new keys to src/config/locales/en-US.json (with the English strings),
then push the change so Crowdin can propagate translations to other locales;
ensure you do the same for the other mentioned ranges (lines 971-974, 1146-1170)
by moving any new/modified keys into en-US.json rather than editing non-English
locale files.

src/config/locales/pt-PT.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Avoid direct key updates in pt-PT.json; use en-US.json as source.

New/updated locale keys should be added in src/config/locales/en-US.json only, then propagated via Crowdin. Please revert direct edits in this locale file.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/pt-PT.json` around lines 224 - 225, Revert the manual
edits to locale keys "current_time" and "server_hint" in pt-PT.json and any
other direct changes (e.g., around lines mentioned) and instead add or update
those keys in src/config/locales/en-US.json only; then trigger the normal
Crowdin sync to propagate translations rather than committing changes directly
to pt-PT.json—ensure you edit en-US.json entries for current_time and
server_hint (and the other referenced keys) so the automated localization
workflow handles the rest.

src/config/locales/got-DE.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

got-DE.json should not be manually updated for new translation keys.

Please move these key additions to src/config/locales/en-US.json and let Crowdin propagate them to this locale file.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/got-DE.json` around lines 224 - 225, The German locale
file src/config/locales/got-DE.json was manually edited to add keys
("current_time" and "server_hint" and other ranges noted: 971-974, 1146-1170);
instead revert/remove these manual additions from got-DE.json and add the new
keys only to src/config/locales/en-US.json so Crowdin can propagate them
automatically; locate the additions by the keys "current_time" and "server_hint"
(and the other changed keys in the ranges mentioned), move their entries to
en-US.json, and ensure no other locale files are edited in this PR.

src/config/locales/et-EE.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Keep locale key changes in en-US.json only.

This PR adds/updates keys directly in a non-en-US locale file. Please apply key additions in src/config/locales/en-US.json and rely on Crowdin sync for et-EE.json.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys. All other locale files are automatically synchronized via Crowdin integration, so they should not be manually edited in pull requests.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/et-EE.json` around lines 224 - 225, Revert the manual
edits to the non-English locale (remove the added/changed keys like
"current_time" and "server_hint" from et-EE.json) and instead add or update
those same keys only in the en-US.json master locale; ensure any other manual
changes in the other locale files referenced (around the other noted ranges) are
likewise reverted so all new or changed translation keys exist only in
en-US.json and rely on Crowdin to sync translations back to et-EE and other
locales.

src/config/locales/es-MX.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Please remove manual edits from this non-en-US locale file.

Lines [224]-[225], [971]-[974], and [1146]-[1170] directly modify src/config/locales/es-MX.json. This should be excluded from the PR and synchronized via Crowdin instead.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/es-MX.json` around lines 224 - 225, Revert all manual
edits in src/config/locales/es-MX.json (including the modified keys
"current_time" and "server_hint" and the other changes in the blocks around
lines you were flagged for) so this locale file matches the Crowdin-synced
state; do not include any translation changes in this file in the PR — only
update en-US.json when adding/updating keys and let Crowdin propagate
translations to es-MX.json. Ensure the PR removes your direct edits to
src/config/locales/es-MX.json and contains only the intended en-US.json changes.

src/config/locales/ja-JP.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Please avoid committing manual changes to ja-JP.json.

Line [224]-[225], Line [971]-[974], and Line [1146]-[1170] should be reverted from this PR and left to Crowdin sync.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/ja-JP.json` around lines 224 - 225, Revert the manual
edits in src/config/locales/ja-JP.json for the keys "current_time" and
"server_hint" (and the other modified blocks referenced in this PR) so that
ja-JP remains untouched and is managed by Crowdin; only make translation-key
additions/changes in en-US.json going forward and leave all other locale files
(including the blocks that span the other reported ranges) to be synchronized by
the Crowdin integration.

src/config/locales/ko-KR.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Please revert manual changes in ko-KR.json from this PR.

Line [224]-[225], Line [971]-[974], and Line [1146]-[1170] are non-en-US locale edits and should come via Crowdin synchronization, not direct PR modifications.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/ko-KR.json` around lines 224 - 225, Revert the manual
edits in ko-KR.json by removing any direct changes to non-en-US keys and
restoring the file to the state before this PR; specifically revert
modifications to the translation keys "current_time" and "server_hint" (and any
other non-en-US entries touched in this PR, e.g., the blocks around lines that
changed later) so that all non-en-US locales remain synced from Crowdin. After
reverting, ensure only en-US.json contains your new/updated translation keys and
leave localization synchronization to the Crowdin workflow; do not add or modify
other locale files manually.

src/config/locales/sw-KE.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

This locale file should not be manually changed in this PR.

Line [224]-[225], Line [971]-[974], and Line [1146]-[1170] update src/config/locales/sw-KE.json directly. Please move these out of the PR and rely on Crowdin sync.

Based on learnings: In the ecency-mobile repository, only the en-US.json locale file should be modified when adding or updating translation keys; all other locale files are automatically synchronized via Crowdin integration.

Also applies to: 971-974, 1146-1170

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/sw-KE.json` around lines 224 - 225, Revert the manual
changes to the Swahili locale for the keys "current_time" and "server_hint" (and
the other blocks you updated) so this PR does not modify non-English locale
files; instead make any new/updated translation keys in the English source
locale (the en-US locale file) only, commit that change, and remove the edits to
the Swahili entries so they will be picked up via the Crowdin sync pipeline.

src/config/locales/es-ES.json-224-225 (1)

224-225: ⚠️ Potential issue | 🟠 Major

Revert manual edits to non-source locale file (es-ES.json).

This PR directly edits src/config/locales/es-ES.json (e.g., Line [224], Line [498], Line [592], Line [971], Line [1146], and Line [1389]). In this repo workflow, translation key additions/updates should be made in src/config/locales/en-US.json only, then synced through Crowdin. Please move these key changes to en-US.json and remove manual edits from es-ES.json.

Based on learnings: In the ecency-mobile repository, only en-US.json should be modified for translation key updates, while other locale files are automatically synchronized via Crowdin.

Also applies to: 498-500, 592-592, 971-974, 1146-1170, 1389-1399

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/es-ES.json` around lines 224 - 225, Revert the manual
edits in es-ES.json by removing the added/modified translation keys (e.g.,
"current_time", "server_hint" and the other keys noted), and instead add those
key additions/updates into src/config/locales/en-US.json so Crowdin can sync
them; specifically, move the new/changed key entries from es-ES.json into
en-US.json (preserving the exact key names and English strings) and commit the
revert of es-ES.json only, leaving localization synchronization to the Crowdin
workflow.

🟡 Minor comments (1)

src/config/locales/lt-LT.json-1146-1170 (1)

1146-1170: ⚠️ Potential issue | 🟡 Minor

Entire ai_image_generator block is untranslated.

This new feature block contains 24 keys, all with English values. The rest of the file contains proper Lithuanian translations, making this section inconsistent and inaccessible to Lithuanian users.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/lt-LT.json` around lines 1146 - 1170, The
ai_image_generator block is still in English; translate all its string values
into Lithuanian while keeping the key names (ai_image_generator and its child
keys like title, prompt_label, prompt_placeholder, chars_remaining,
select_aspect_ratio, cost_label, balance_label, points_unit, generate_button,
generating, result_title, insert_button, download_button, share_button,
generate_again, success, error_insufficient_points, error_content_policy,
error_rate_limit, error_generic, error_prompt_required, use_suggestion,
dropdown_label) unchanged; preserve all interpolation tokens (e.g., {count},
{required}, {available}, {suggestion}) and punctuation/quotes exactly as they
appear so runtime formatting is unaffected.

🧹 Nitpick comments (5)

src/config/locales/ro-RO.json (3)

1146-1170: Entire ai_image_generator block is untranslated.

All 24 keys in this new block contain English text instead of Romanian translations. This is expected for newly added Crowdin strings pending translation.

Additionally, the AI-generated summary mentioned a duplicate ai_image_generator block in this file, but only one instance exists here (lines 1146-1170). The summary may have been referring to duplication across different locale files in the PR rather than within this specific file.

,

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/ro-RO.json` around lines 1146 - 1170, The
ai_image_generator localization block is still in English; translate all 24 keys
inside the "ai_image_generator" object into Romanian (e.g., "title",
"prompt_label", "prompt_placeholder", "chars_remaining", "select_aspect_ratio",
"cost_label", "balance_label", "points_unit", "generate_button", "generating",
"result_title", "insert_button", "download_button", "share_button",
"generate_again", "success", "error_insufficient_points",
"error_content_policy", "error_rate_limit", "error_generic",
"error_prompt_required", "use_suggestion", "dropdown_label") so the file
contains Romanian strings for each key while preserving placeholders like
{count}, {required}, {available}, and {suggestion}.

---

971-974: Untranslated dropdown labels.

All four new dropdown keys (dropdown_transfer, dropdown_promote, dropdown_boost, dropdown_ai_image) contain English text. These appear to be pending Romanian translation in Crowdin.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/ro-RO.json` around lines 971 - 974, Replace the English
values for the four localization keys with Romanian translations: update
"dropdown_transfer", "dropdown_promote", "dropdown_boost", and
"dropdown_ai_image" in src/config/locales/ro-RO.json to their Romanian
equivalents (e.g., "Transfer" → "Transferă" or "Transfer", "Promote" →
"Promovează" or "Promovează", "Boost" → "Îmbunătățește" or "Boost" if a native
term is preferred, "AI Image" → "Imagine AI" or "Imagine generată de AI"),
ensuring the final chosen translations match Crowdin entries and project
terminology conventions before committing.

---

224-225: Untranslated string detected.

The server_hint value is in English rather than Romanian. Since this is a Crowdin sync, this likely represents a newly added string pending translation.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/ro-RO.json` around lines 224 - 225, The "server_hint"
localization key is still in English; replace its value with the proper Romanian
translation (keeping the JSON string formatting and surrounding quotes intact)
so the entry for "server_hint" is fully translated into Romanian; ensure you
don't alter the key name or surrounding punctuation and that the JSON remains
valid.

src/config/locales/lt-LT.json (2)

971-974: Multiple untranslated dropdown labels.

All four new dropdown keys (dropdown_transfer, dropdown_promote, dropdown_boost, dropdown_ai_image) contain English values in this Lithuanian locale file. For consistency, these should eventually be translated—for example, the file already uses "Pervesti" for transfer operations elsewhere (line 1029).

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/lt-LT.json` around lines 971 - 974, The four dropdown keys
dropdown_transfer, dropdown_promote, dropdown_boost, and dropdown_ai_image in
lt-LT.json are still in English; update their values to Lithuanian translations
(use the existing "Pervesti" value already used for transfer elsewhere for
dropdown_transfer and provide appropriate Lithuanian equivalents for
dropdown_promote, dropdown_boost, and dropdown_ai_image) so the locale file is
fully translated and consistent.

---

225-225: Untranslated string in Lithuanian locale file.

The server_hint value is in English rather than Lithuanian. Since this is a Crowdin-synced update, this is likely a placeholder awaiting translation by the Lithuanian translation community. No action needed if this is intentional Crowdin behavior.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@src/config/locales/lt-LT.json` at line 225, The "server_hint" key in
lt-LT.json contains an English value ("You can also try changing API Server in
Settings > Server.") that should be translated to Lithuanian; update the value
of the "server_hint" property in src/config/locales/lt-LT.json to a proper
Lithuanian translation (or, if this is intentionally left as a Crowdin
placeholder, add a comment/marker per project convention to indicate it is
pending translation) so the locale file no longer contains an English string.