Skip to content

Commit 9f18394

Browse files
committed
update
1 parent 9a9f367 commit 9f18394

File tree

1 file changed

+34
-15
lines changed

1 file changed

+34
-15
lines changed

docs/troubleshooting/translations/fix_google_translate_errors.md

Lines changed: 34 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -9,32 +9,51 @@ title: Fix Google Translate Errors
99
FlutterFlow integrates with Google Translate to help localize your app automatically. This guide outlines how to identify and resolve common issues with the translation integration.
1010

1111
:::info[Prerequisites]
12-
- Google Translate integration has been added to the project.
13-
- At least one supported language has been configured under **App Settings > Localization**.
14-
- Refer to the **[Google Translate Integration](/concepts/localization/#add-multi-language-support)** guide.
12+
- Google Translate integration must be enabled for the project.
13+
- At least one supported language must be added in **App Settings > Localization**.
14+
- Review the [Google Translate Integration](/concepts/localization/#add-multi-language-support) guide for setup instructions.
1515
:::
1616

17-
## Common Translation Issues:
17+
## Common Translation Issues and Fixes:
1818

19-
- **Long Text Blocks:** Exceeding limits or timeouts — translate externally if needed.
20-
- **Unsupported Characters:** Emojis or symbols may cause errors. Remove or replace.
21-
- **Language Limits:** Max 10 languages supported. Reduce if necessary.
19+
- **Long Text Forms**
20+
**Problem:** Attempting to translate long blocks of text in forms or widgets can lead to API timeouts or failures.
21+
**Solution:** Remove long text elements and translate them outside of FlutterFlow using external tools like Google Translate. Once translated, manually paste the content back into your project. Ensure the input field is empty before retrying automatic translation.
22+
23+
- **Special Characters**
24+
**Problem:** Some special characters—such as emojis, accented symbols, or non-Latin characters—may not be supported by the Google Translate API and can cause translation to fail.
25+
**Solution:** Review the text and replace or remove any unsupported special characters. Then attempt the translation again.
26+
27+
- **Exceeding Language Limit**
28+
**Problem:** Adding more than 10 language options in your project may result in translation failure.
29+
**Solution:** Limit your project to a maximum of 10 supported languages for translation to work reliably with Google Translate.
2230

2331
## Steps to Troubleshoot Translation Failures:
2432

2533
1. **Locate the Problem Area**
26-
Identify whether the error occurs on a specific widget, page, or text field to narrow down the source of the issue.
34+
Identify the specific widget, page, or field where translation fails. Focusing on the problematic component will make resolution faster.
35+
36+
2. **Use the Translate All Button**
37+
In **App Settings > Localization**, click the **Translate All** button. The process will stop at the first failure, indicating the field or element causing the issue.
2738

28-
2. **Check the Browser Console**
29-
Use Chrome DevTools to inspect the console for errors related to failed translation requests.
39+
3. **Check Chrome Developer Console**
40+
Open the Chrome DevTools console and monitor for any error logs related to translation requests. This can help identify issues such as invalid characters, request failures, or unsupported content.
3041

31-
3. **Use the Translate All Button**
32-
Clicking **Translate All** will begin the process and stop at the first problematic field, helping you identify where the issue occurs.
42+
4. **Remove and Isolate Problematic Text**
43+
Temporarily delete the suspected text and retry the translation. If the translation proceeds successfully, that text is likely causing the failure. Manually translate and reinsert it.
3344

34-
4. **Temporarily Remove Problem Text**
35-
If a specific field is causing an issue, delete the content, run the translation process, and then re-add the translated content manually.
45+
:::note
46+
Using shorter, plain-text strings without special characters improves success rates with the Google Translate API.
47+
:::
3648

49+
:::info[Additional Help]
50+
If the issue persists after troubleshooting, reach out to [[email protected]](mailto:[email protected]) with the following:
3751

38-
If issues persist after following the steps above, contact [[email protected]](mailto:[email protected]) for assistance.
52+
- Screenshot or screen recording of the failure
53+
- Console error logs (if available)
54+
- A description of where the failure occurs (page/widget/text field)
55+
56+
This will help the support team resolve the issue faster.
57+
:::
3958

4059

0 commit comments

Comments
 (0)