Skip to content

Commit d8083d0

Browse files
committed
updated content, improved formatting
1 parent 5920f8d commit d8083d0

8 files changed

+28
-15
lines changed
File renamed without changes.
File renamed without changes.
File renamed without changes.

docs/troubleshooting/migrate-issues/local_build_providerinstaller_error.md renamed to docs/troubleshooting/test-mode/local_build_providerinstaller_error.md

Lines changed: 16 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -33,9 +33,15 @@ This error commonly occurs when building Flutter apps on Android emulators. It i
3333

3434
Run the following command in your project directory:
3535

36-
```js
36+
```bash
3737
flutter clean
38+
```
39+
40+
```bash
3841
flutter pub get
42+
```
43+
44+
```bash
3945
flutter run
4046
```
4147

@@ -45,14 +51,21 @@ This error commonly occurs when building Flutter apps on Android emulators. It i
4551
3. **Upgrade Flutter (If Problem Persists)**
4652

4753
If the issue continues, upgrading Flutter may help. Run the command below to upgrade:
48-
```js
54+
```bash
4955
flutter upgrade
5056
```
5157

5258
Ensure your Flutter SDK is up to date. You can verify the version with:
5359

54-
```js
60+
```bash
5561
flutter --version
5662
```
5763

64+
:::note
5865
This error is often related to Google Play Services not being properly initialized on the emulator. If you're still encountering issues, consider creating a new emulator using a system image that includes the Play Store.
66+
:::
67+
68+
:::info[Additional Resources]
69+
- Read the official **[Flutter Build Documentation](https://docs.flutter.dev/testing/build-modes)**.
70+
- Check **[Android Emulator System Images](https://developer.android.com/studio/run/managing-avds#system-images)**.
71+
:::

docs/troubleshooting/migrate-issues/slow_test_mode_load.md renamed to docs/troubleshooting/test-mode/slow_test_mode_load.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ If Test Mode takes several minutes to load or fails entirely, the issue may stem
1313
- You have already deployed or previewed a version of your app.
1414
:::
1515

16-
Below are the common causes and fixes:
16+
**Steps to Resolve Slow Loading:**
1717

1818
- **Check Your Internet Connection**
1919

@@ -36,7 +36,7 @@ Below are the common causes and fixes:
3636
Extensions like ad blockers or privacy tools can interfere with FlutterFlow’s platform. Temporarily disable them to check for improvement.
3737

3838
:::tip[Optimize Your Project]
39-
Projects with many pages, assets, or custom code can take longer to compile.
39+
Projects with many pages, assets, or custom code may take longer to compile. Follow these steps to optimize your project:
4040
- Remove unused images, fonts, or icons.
4141
- Consolidate or simplify custom code.
4242
- Limit the number of pages in a single testing session.

docs/troubleshooting/migrate-issues/test_api_calls.md renamed to docs/troubleshooting/test-mode/test_api_calls.md

Lines changed: 10 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -9,21 +9,21 @@ title: Test API Calls
99
Verifying an API response before integrating it into your app helps prevent runtime issues and ensures your data is structured correctly. This guide walks you through testing an API directly within FlutterFlow.
1010

1111
:::info[Prerequisites]
12-
- You must have a project open in FlutterFlow.
13-
- An API key or endpoint must be available if required by the API.
12+
- A project is open in FlutterFlow.
13+
- An API key or endpoint is available if required by the API.
1414
:::
1515

16-
## Steps to Test API Calls
16+
**Steps to Test API Calls:**
1717

18-
1. **Open the API Calls Panel**
18+
1. **Open the `API Calls` Panel**
1919

20-
From the left sidebar, go to the **API Calls** section.
20+
From the left sidebar, go to the `API Calls` section.
2121

2222
![](../assets/20250430121444122926.png)
2323

2424
2. **Select or Create an API Call**
2525

26-
Choose an existing API call or click **+ Add API Call** to create a new one.
26+
Choose an existing `API Call` or click `+ Add API Call` to create a new one.
2727

2828
![](../assets/20250430121444364083.png)
2929

@@ -33,19 +33,19 @@ Verifying an API response before integrating it into your app helps prevent runt
3333

3434
![](../assets/20250430121444571412.png)
3535

36-
4. **Click the Response & Test Tab**
36+
4. **Click the `Response & Test` Tab**
3737

38-
Navigate to the **Response & Test** tab to preview the response structure.
38+
Navigate to the `Response & Test` tab to preview the response structure.
3939

4040
![](../assets/20250430121444783602.png)
4141

4242
5. **Run the API Test**
4343

44-
Click the **Test API Call** button to trigger the request. If successful, you’ll see the API response in JSON format.
44+
Click the `Test API Call` button to trigger the request. If successful, the API response displays in JSON format.
4545

4646
![](../assets/20250430121445020637.png)
4747

48-
A valid API response will display a structured output like the example below:
48+
A valid API response displays a structured output like the example below::
4949

5050
![](../assets/20250430121445238952.png)
5151

0 commit comments

Comments
 (0)