Skip to content

Commit cc5db88

Browse files
authored
Merge branch 'main' into patch-2
2 parents d32cb77 + 53aee79 commit cc5db88

File tree

3 files changed

+9
-5
lines changed

3 files changed

+9
-5
lines changed

docs/ff-integrations/database/local-sql/quickstart.md

Lines changed: 6 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -49,13 +49,18 @@ If you don't yet have an SQLite database, you can easily create one using tools
4949

5050
For this example, we'll create a "Notes" table with `ID`, `Title`, `Details`, `DueDate`, and `IsCompleted` as columns.
5151

52+
:::warning
53+
It is advisable to avoid using any SQL reserved keywords such as `type` and `data` as column names to prevent potential build errors or unexpected behavior. SQLite reserves certain words for its SQL syntax, and using these as identifiers without proper handling may cause issues. For a comprehensive list of reserved keywords, refer to the [**SQL reserved words**](https://en.wikipedia.org/wiki/List_of_SQL_reserved_words).
54+
:::
55+
5256
Here's how you can create and configure the database:
5357

5458
<div class="video-container"><iframe src="https://www.loom.
5559
com/embed/c5f43ee65e954df2856d78e035ab8bba?sid=fcaccfa1-fb0c-4f67-9953-d51e7227e596" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe></div>
56-
5760
<p></p>
5861

62+
63+
5964
:::info[Important to note]
6065
SQLite does not have dedicated date-time or boolean data types. For storing date-time values like `DueDate`, we use the integer data type and represent the date-time as a [**UNIX timestamp**](https://www.unixtimestamp.com/). Similarly, for boolean values, such as checking if a note is completed, SQLite uses integers where `0` represents `false` (or not completed) and `1` represents `true` (or completed).
6166
:::

docs/ff-integrations/maps/google-maps/place-picker-widget.md

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -45,11 +45,10 @@ Here's an example from the Demo app:
4545

4646
<p></p>
4747

48-
:::note[Prerequisites]
48+
:::info[Prerequisites]
49+
- The Place Picker **requires a Google Maps API key**. See how to [**create and add API keys**](generate-maps-keys.md#add-maps-apis) to FlutterFlow.
4950
- Ensure you have enabled **Places API** from Cloud console. [**Check out the Setup docs.**](generate-maps-keys.md#add-places-apis)
5051
- Enable **Google Maps Platform Billing** via your Cloud console. Please note: Failing to enable the Google Maps Platform Billing will not show any place in an autocomplete list.
51-
- Add API keys as suggested in [**Getting Started**](generate-maps-keys.md#add-keys-to-flutterflow) guide.
52-
5352
:::
5453
<figure>
5554

docs/ff-integrations/payments/stripe.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -266,7 +266,7 @@ Before you release the app to production, complete the following steps:
266266

267267
1. **Stripe Settings Adjustment**: In FlutterFlow's Stripe settings, verify the Merchant country code is a 3-digit code, like "USA" instead of "US". If needed, remove previously deployed functions in the Firebase console and redeploy them after updating the country code.
268268
2. **User Authentication Requirement**: Stripe payments require an authenticated user session. Ensure you're attempting the Stripe action after a user has successfully logged in to the app.
269-
3. **Cloud Functions Permissions**: Check that your cloud functions have the 'Cloud Functions Invoker' permission set for allUsers in the Google Cloud console. This permission is typically assigned by default, but it's good practice to double-check.
269+
3. **Cloud Functions Permissions**: Check that your cloud functions have the **Cloud Functions Invoker** permission set for **allUsers** in the Google Cloud console. To do this, go to the Cloud Console, directly search for the **initStripePayment** function, open the function, switch to the **Permissions** tab, and confirm the permissions status. This permission is typically assigned by default, but it's good practice to double-check.
270270
271271
![unknown-error-occured](imgs/unknown-error-occured.avif)
272272
</p>

0 commit comments

Comments
 (0)