Fixing links

Author: pinkeshmars

docs/ff-integrations/authentication/authentication-types.md

@@ -19,8 +19,8 @@ standards like OAuth 2.0 and OpenID Connect. This makes it highly adaptable for
 backend, ensuring a secure and scalable solution.
 
 :::info
-Learn how to enable Firebase Authentication and integrate popular auth providers in your FlutterFlow
-app. [**Learn more here**](#)
+Learn how to enable [**Firebase Authentication**](../authentication/firebase-auth/auth-initial-setup.md) and integrate popular auth providers in your FlutterFlow
+app.
 :::
 
 ## Supabase Authentication
@@ -31,8 +31,8 @@ Supabase provides a powerful and flexible authentication solution, similar to Fi
 unique advantages like support for PostgreSQL.
 
 :::info
-Discover how to set up Supabase Authentication and link it with available auth providers within your
-FlutterFlow app. [**Learn more here**](#)
+Discover how to set up [**Supabase Authentication**](../authentication/supabase-auth/initial-setup.md) and link it with available auth providers within your
+FlutterFlow app.
 :::
 
 ## Custom Authentication
@@ -44,6 +44,6 @@ application. Whether you need to work with legacy systems or have specific secur
 custom authentication provides the necessary control.
 
 :::info
-Explore how to implement custom authentication strategies in your FlutterFlow app, ensuring your
-authentication flow aligns with your business requirements. [**Learn more here**](#)
+Explore how to implement [custom authentication](../authentication/custom-auth/custom-auth.md) strategies in your FlutterFlow app, ensuring your
+authentication flow aligns with your business requirements.
 :::

docs/ff-integrations/authentication/custom-auth/custom-auth.md

@@ -98,13 +98,13 @@ To enable custom authentication in FlutterFlow:
 
 Let's add a page that allows users to create accounts and log in. To speed up, you can add a page from the template. Here is the page added from the templates, and after some modification, it looks the below:
 
-Also, see how to [build a page layout](#) in case you want to build a page from scratch.
+Also, see how to [build a page layout](../../../ff-concepts/layout/building-layout.md) in case you want to build a page from scratch.
 
 ![auth-2-template.avif](../imgs/auth-2-template.avif)
 
 ### 3. Authenticate users
 
-On each page, on click of a button, you can add appropriate authentication related [API calls](#). For this example, we use [this](https://dummyjson.com/docs/auth).
+On each page, on click of a button, you can add appropriate authentication related [API calls](../../../resources/control-flow/backend-logic/api/rest-api.md). For this example, we use [this](https://dummyjson.com/docs/auth).
 
 <div style={{
     position: 'relative',
@@ -139,7 +139,7 @@ After successful authentication, you can save the auth related data using the 'L
 1. Inside the **TRUE** branch of the [previous API call](#3-authenticate-users), add the **Log in** (under *Backend/Database > Custom Authentication*) action.
 
 2. Under the **User Auth Properties**, you can set values for **Authentication Token**, **Refresh Token**, **Token Expiry Time**, and **User UID**. **Note that for the 'Persist Auth Sessions' option to work, you must set the Authentication Token**.
-3. **Set User Data** to store the result of the previous API call (i.e., auth details) in a Custom Data Type. See how to get the [JSON into Data Type](#).
+3. **Set User Data** to store the result of the previous API call (i.e., auth details) in a Custom Data Type. See how to get the [JSON into Data Type](../../../resources/control-flow/backend-logic/api/rest-api.md#json-to-data-type).
 
 <div style={{
     position: 'relative',

docs/ff-integrations/authentication/firebase-auth/apple-login.md

@@ -191,7 +191,7 @@ To enable Apple authentication in the Firebase:
 
 ### 4. Add an Apple sign-in button
 
-To allow users to authenticate, you need a login page with a button. You can create your own or use the one from the [widget template](#) or page template.
+To allow users to authenticate, you need a login page with a button. You can create your own or use the one from the widget template or page template.
 
 Here's how you can add the Apple sign-in button from our page template:
 
@@ -265,7 +265,7 @@ To let users log out of your app, you can use the [Logout](../logout-action.md)
 
 ### 7. Preparing to test the app
 
-For [testing your app](#) on a real device, you must configure the project in Xcode. This includes adding a team to your project and setting an appropriate signing certificate.
+For testing your app on a real device, you must configure the project in Xcode. This includes adding a team to your project and setting an appropriate signing certificate.
 
 Here's how you configure your project in Xcode:
 

docs/ff-integrations/authentication/firebase-auth/auth-initial-setup.md

@@ -125,7 +125,7 @@ Google Sign-in and Phone Sign-in. To learn more about the SHA-1 key, see
 this [link](https://developers.google.com/android/guides/client-auth).
 
 :::warning[Release Guidelines]
-While releasing the app, make sure to [**get the key from Play Console**](#).
+While releasing the app, make sure to [**get the key from Play Console**](#getting-sha-keys-for-release-mode).
 :::
 
 1. Open a terminal window:
@@ -172,6 +172,14 @@ While releasing the app, make sure to [**get the key from Play Console**](#).
   fingerprint.
 4. Enter the copied SHA-1 into the input box and click on Save.
 
+#### Getting SHA keys for release mode
+
+If you're releasing your app to the Play Store, you must add the SHA certificate fingerprints from the Play Console.
+
+To get the keys for the release app, navigate to **Play Store Console > Your project > Release Setup > App Signing** and copy the **SHA-1** and **SHA-256** keys.
+
+![release-sha1-key](../imgs/release-sha1-key.avif)
+
 ### Regenerate config files
 
 After adding the SHA-1 key you must re-generate the config files in FlutterFlow.
@@ -183,3 +191,4 @@ To regenerate the config files:
 
 ![regerenate](../imgs/regerenate.png)
 
+

docs/ff-integrations/authentication/firebase-auth/jwt-token-login.md

@@ -44,12 +44,12 @@ Adding JWT token authentication comprises the following steps:
 
 ### 1. Add login API
 
-You must [create an API](#) endpoint on your server that accepts email/username and password. If the credentials are valid, it generates the JWT token and passes it back in response.
+You must [create an API](../../../resources/control-flow/backend-logic/api/create-test-api-calls.md) endpoint on your server that accepts email/username and password. If the credentials are valid, it generates the JWT token and passes it back in response.
 
 At your server, you can generate the JWT token either using the [Firebase Admin SDK](https://firebase.google.com/docs/auth/admin/create-custom-tokens#create_custom_tokens_using_the_firebase_admin_sdk) or a [third-party JWT library](https://firebase.google.com/docs/auth/admin/create-custom-tokens#create_custom_tokens_using_a_third-party_jwt_library). You can find the detailed instructions [here](https://firebase.google.com/docs/auth/admin/create-custom-tokens).
 
 :::info
-Alternatively, you can integrate Supabase authentication into your app and use the JWT token generated after [**account creation**](#).
+Alternatively, you can integrate Supabase authentication into your app and use the JWT token generated after [**account creation**](../supabase-auth/auth-actions.md#log-in-action).
 :::
 
 The API endpoint should be similar to the following (Tip: Expand and see the '200 OK' section):
@@ -87,12 +87,12 @@ In most cases, you would make the app content available right after creating a n
 :::
 
 :::info
-If you want to try the JWT token authentication without creating an API endpoint right now, you can [**generate the JWT token locally**](#) for testing.
+If you want to try the JWT token authentication without creating an API endpoint right now, you can [**generate the JWT token locally**](#create-a-jwt-token-locally) for testing.
 :::
 
 ### 2. Adding login page
 
-Let's [add a sign-in page from the templates](#) and choose the **Authenticate Solo Alt** from under the **Auth** tab. Tip: After adding, remove the other social sign-in buttons.
+Let's add a sign-in page from the templates and choose the **Authenticate Solo Alt** from under the **Auth** tab. Tip: After adding, remove the other social sign-in buttons.
 
 ![login-page.avif](../imgs/login-page.avif)
 
@@ -105,16 +105,16 @@ Here are the step by step instructions:
 1. Select the **Widget** (e.g., Sign In) on which you want to define the action.
 
 2. Select **Actions** from the Properties Panel (the right menu), and click **Open**. This will open an **Action Flow Editor** in a new popup window.
-3. [Add the login api](#) and provide the **Action Output Variable Name**. ****If the call succeeds, this will be used to retrieve the token.
+3. Add the login api and provide the **Action Output Variable Name**. If the call succeeds, this will be used to retrieve the token.
 4. Inside the **TRUE** section, click on the **+** button and select **Add Action**.
 5. On the right side, search and select the **Log in** (under Firebase Authentication) action.
 6. Set the **Auth Provider** to **JWT token**.
 7. Now, you must provide the actual JWT token. To set the token from an API response:
     1. Click on the **UNSET** and select the **Action Outputs -> Action Output Variable Name** (that you specified in the API call section.)
     2. Set the **API Response Options** to **JSON Body** and **Available Options** to **JSON Path**.
     3. Enter the **JSON Path** to locate the token in API response, such as `$.token,` and click **Confirm**.
-8. (Optional) add the [snackbar action](#) to display the success message.
-9. (Optional) Inside the **False** section, add the [snackbar action](#) to display the failure message.
+8. (Optional) add the [snackbar action](../../../resources/ui/pages/page-elements.md#show-snackbar-action) to display the success message.
+9. (Optional) Inside the **False** section, add the snackbar action to display the failure message.
 
 <div style={{
     position: 'relative',
@@ -152,7 +152,7 @@ To confirm the successful integration and the creation of users, navigate to you
 
 ## Create a JWT token locally
 
-Sometimes you might want to build and test the JWT authentication before the login or create account API is ready. You can achieve this by creating the JWT token locally and passing it inside the [login action](#).
+Sometimes you might want to build and test the JWT authentication before the login or create account API is ready. You can achieve this by creating the JWT token locally and passing it inside the [login action](#3-add-login-action).
 
 :::warning
 Use this method only for testing purposes. Ideally, you should be doing this on the server side.
@@ -228,8 +228,8 @@ Here's an example of how you can use the *Authenticated User* object to filter t
 
 Once you log in via the JWT token, the *Authenticated User* object is available. This object contains the fields (i.e., logged-in user's data), especially **User Reference (users ref),** that you may need to provide while adding or retrieving Firestore documents.
 
-When such user reference is stored inside the Firestore documents, you can use them ****inside the **Single** or **Multiple Recipient** while defining the **Audience** inside the [Trigger Push Notification](#) action, as shown in the image below:
+When such user reference is stored inside the Firestore documents, you can use them inside the **Single** or **Multiple Recipient** while defining the **Audience** inside the [Trigger Push Notification](../../notifications/push-notifications/getting-started.md#trigger-push-notification) action, as shown in the image below:
 
 ![send-push-notification-to-users-created-via-JWT-token.png](../imgs/send-push-notification-to-users-created-via-JWT-token.png)
 
-To learn more about how to use user references for sending push notifications, please check the [push notification](#) section.
+To learn more about how to use user references for sending push notifications, please check the [push notification](../../notifications/push-notifications/getting-started.md) section.

docs/ff-integrations/authentication/firebase-auth/password-reset-action.md

@@ -46,7 +46,7 @@ Adding password reset comprises of following steps:
 
 ### 1. Building page
 
-Let's add a page that allows users to provide their email address. To speed up, you can add a page from the [template](#). Here is what the template page (named 'Forgot Password 01') looks like:
+Let's add a page that allows users to provide their email address. To speed up, you can add a page from the template. Here is what the template page (named 'Forgot Password 01') looks like:
 
 ![password reset build ui](../imgs/password-reset-build-ui.png)
 

docs/ff-integrations/authentication/firebase-auth/phone-login.md

@@ -62,7 +62,7 @@ Adding Phone sign-in comprises the following steps:
 
 ### 1. Setting up phone sign-in
 
-To use phone sign-in, you must [get the SHA-1 key](#) and [regenerate the configuration files](#). You can find the detailed instructions [here](#). **Note** that this step is often missed, so ensure you must complete this step before you proceed further.
+To use phone sign-in, you must [get the SHA-1 key](auth-initial-setup.md#generate-the-sha-1-key) and [regenerate the configuration files](auth-initial-setup.md#regenerate-config-files). You can find the detailed instructions [here](auth-initial-setup.md). **Note** that this step is often missed, so ensure you must complete this step before you proceed further.
 
 ### 2. Enabling phone authentication in Firebase
 
@@ -104,7 +104,7 @@ To enable authentication in the Firebase:
 
 ### 3. Building phone number page
 
-To allow users to authenticate using their phone number, you need to create a page to accept the user's phone number. We provide a collection of ready-to-use templates. You can use one of our templates or [create a page from scratch](#).
+To allow users to authenticate using their phone number, you need to create a page to accept the user's phone number. We provide a collection of ready-to-use templates. You can use one of our templates or create a page from scratch.
 
 Here is the page added from the templates, and after some modification, it looks the below:
 <div style={{
@@ -296,17 +296,17 @@ To test on a real device, add the SHA-256 key in the Firebase console and enable
 Skip if you find the below steps already completed by our automated Firebase integration.
 :::
 
-1. Get the SHA-256 key/fingerprint, add it to your Firebase project, and then regenerate the Firebase config files in FlutterFlow. **Note**: The instructions are similar to generating the SHA-1 key and are explained [here](#). You will find the SHA-256 key in the terminal just below the SHA-1 key. This is required for the Firebase to verify that the sign-in request is coming from a legitimate device.
+1. Get the SHA-256 key/fingerprint, add it to your Firebase project, and then regenerate the Firebase config files in FlutterFlow. **Note**: The instructions are similar to generating the SHA-1 key and are explained [here](auth-initial-setup.md#generate-the-sha-1-key). You will find the SHA-256 key in the terminal just below the SHA-1 key. This is required for the Firebase to verify that the sign-in request is coming from a legitimate device.
 
 :::warning
-While releasing the app, make sure to [**get the key from the Play Console**](#).
+While releasing the app, make sure to [**get the key from the Play Console**](auth-initial-setup.md#getting-sha-keys-for-release-mode).
 :::
 
 ![SHA-256 key](../imgs/sha-256-key.png)
 
 
 1. Open the [Google Developers Console](https://console.developers.google.com/) (Make sure your project is selected in the dropdown at the top), Click on the **Library** menu on the left, search for the **Google Play Integrity API,** and enable it.
-2. Now, download and test the app using the instructions [here](#).
+2. Now, download and test the app using the instructions [here](../../../testing-deployment-publishing/exporting-code/ff-cli.md).
 
 <div style={{
     position: 'relative',
@@ -388,7 +388,7 @@ To add the fictitious number:
 <details>
 <summary>Getting this error: "The given sign-in provider is disabled for this Firebase project. Enable it in the Firebase console, under the sign-in method tab of the Auth Section."</summary>
 <p>
-1. First, ensure you have clicked the "Save" button while [Enabling phone authentication in Firebase](#).
+1. First, ensure you have clicked the "Save" button while [Enabling phone authentication in Firebase](#2-enabling-phone-authentication-in-firebase).
 
 ![Enabling phone authentication in Firebase](../imgs/adding-authorized-domain.png)
 

docs/ff-integrations/authentication/imgs/release-sha1-key.avif

@@ -241,7 +241,7 @@ By enabling Firestore batch write, you can group multiple operations and send th
 
 Suppose you have an e-commerce application, and after a successful order, you need to update the product inventory count and create a new document in the 'orders' collection. Using a batch write, you can combine these operations and execute them together to ensure data consistency.
 
-To enable Firestore batch write, you must have multiple Firestore ([any combination of)](#) 
+To enable Firestore batch write, you must have multiple Firestore any combination of 
 actions; inside the action editor, at the top right side, enable **Batch Firestore Writes**.
 
 <figure>
@@ -261,7 +261,7 @@ com/embed/238400b5445b444db712f492584b0d6e?sid=7b496882-0280-4920-924c-640fddeff
 
 To do so:
 
-1. Ensure you have [**Query Collection**](#) or [**Document from Reference**](#) added on a widget with **Single Time Query** disabled.
+1. Ensure you have **Query Collection** or **Document from Reference** added on a widget with **Single Time Query** disabled.
 2. Now select the widget, head over to **Actions**, and click **+ Add Action**.
 3. Select the **On Data Change** tab. That means actions added under this will be called whenever the data changes.
 4. Now, you can 

docs/ff-integrations/database/cloud-firestore/firestore-actions.md

@@ -14,7 +14,7 @@ The simple search allows you to search the data present locally on a device. For
 :::caution[When to use Simple Search vs Algolia]
 We advise using a simple search only for the smaller Firestore collection (with limited records).
 Otherwise, it can be slow and/or expensive. For a more extensive collection, consider using the 
-[**Algolia search**](#).
+[**Algolia search**](../search/algolia-search.md).
 :::
 
 <div class="video-container"><iframe src="https://www.loom.