diff --git a/src/fragments/start/getting-started/reactnative/setup.mdx b/src/fragments/start/getting-started/reactnative/setup.mdx
index 287bd4fe934..02ad68b4b96 100644
--- a/src/fragments/start/getting-started/reactnative/setup.mdx
+++ b/src/fragments/start/getting-started/reactnative/setup.mdx
@@ -126,6 +126,14 @@ When you initialize a new Amplify project, a few things happen:
- It modifies the **.gitignore** file, adding some generated files to the ignore list
- A cloud project is created for you in the AWS Amplify Console that can be accessed by running `amplify console`. The Console provides a list of backend environments, deep links to provisioned resources per Amplify category, status of recent deployments, and instructions on how to promote, clone, pull, and delete backend resources
+
+
+
+**Note:** if you are using Expo EAS build, you will need to force commit the `amplifyconfiguration.json` file to local git repository before running the `eas build` command. This is because the `amplifyconfiguration.json` file is excluded in the default `.gitignore`, and the `eas build` command will not include untracked files in the build. When build completes you must remove the `amplifyconfiguration.json` file from the git repository and never commit and push it to the remote repository.
+
+
+
+
## Set up frontend
Next, configure Amplify so it can interact with backend services by adding the following code below the last import:
diff --git a/src/pages/[platform]/reference/amplify_outputs/index.mdx b/src/pages/[platform]/reference/amplify_outputs/index.mdx
index 817555cd952..4f6de200e84 100644
--- a/src/pages/[platform]/reference/amplify_outputs/index.mdx
+++ b/src/pages/[platform]/reference/amplify_outputs/index.mdx
@@ -35,6 +35,14 @@ You can also manually create this file for a specified Amplify app ID and branch
{/* @TODO full type/interface to reference */}
+
+
+
+**Note:** if you are using Expo EAS build, you will need to force commit the `amplify_outputs.json` file to local git repository before running `eas build` command. This is because the `amplify_outputs.json` file is excluded in the default `.gitignore`, and the `eas build` command will not include untracked files in the build. When build completes you must remove the `amplifyconfiguration.json` file from the git repository and never commit and push it to the remote repository.
+
+
+
+
## Extending Amplify outputs file
The `amplify_outputs.json` file is not just a static artifact; it is designed to be extendable to suit the evolving needs of your application. By leveraging the `addOutput` method from your `backend`, you can programmatically add configurations. This is particularly useful for customizing outputs that are not directly exposed through the Amplify constructs or for dynamically adjusting your app's configuration in response to changes in your backend strategy.
diff --git a/src/pages/gen1/[platform]/start/getting-started/setup/index.mdx b/src/pages/gen1/[platform]/start/getting-started/setup/index.mdx
index e6c3142dd03..45bc5062232 100644
--- a/src/pages/gen1/[platform]/start/getting-started/setup/index.mdx
+++ b/src/pages/gen1/[platform]/start/getting-started/setup/index.mdx
@@ -567,6 +567,14 @@ When you initialize a new Amplify project, a few things happen:
- It creates a file called `amplifyconfiguration.json` in your designated **Source Directory Path** that holds all the configuration for the services you create with Amplify. This is how the Amplify JavaScript client library is able to get the necessary information to connect to your backend services.
- It modifies the `.gitignore` file, adding some generated files to the ignore list
+
+
+
+**Note:** if you are using Expo EAS build, you will need to force commit the `amplifyconfiguration.json` file to local git repository before running the `eas build` command. This is because the `amplifyconfiguration.json` file is excluded in the default `.gitignore`, and the `eas build` command will not include untracked files in the build. When build completes you must remove the `amplifyconfiguration.json` file from the git repository and never commit and push it to the remote repository.
+
+
+
+
## Install Amplify Libraries
diff --git a/src/pages/gen1/[platform]/start/project-setup/create-application/index.mdx b/src/pages/gen1/[platform]/start/project-setup/create-application/index.mdx
index 8ccfeda5354..6c8a4074fb9 100644
--- a/src/pages/gen1/[platform]/start/project-setup/create-application/index.mdx
+++ b/src/pages/gen1/[platform]/start/project-setup/create-application/index.mdx
@@ -258,6 +258,14 @@ When you initialize a new Amplify project, a few things happen:
- It modifies the `.gitignore` file, adding some generated files to the ignore list
- A cloud project is created for you in the AWS Amplify Console that can be accessed by running `amplify console`. The Console provides a list of backend environments, deep links to provisioned resources per Amplify category, status of recent deployments, and instructions on how to promote, clone, pull, and delete backend resources.
+
+
+
+**Note:** if you are using Expo EAS build, you will need to force commit the `amplifyconfiguration.json` file to local git repository before running the `eas build` command. This is because the `amplifyconfiguration.json` file is excluded in the default `.gitignore`, and the `eas build` command will not include untracked files in the build. When build completes you must remove the `amplifyconfiguration.json` file from the git repository and never commit and push it to the remote repository.
+
+
+
+
As you add or remove categories and make updates to your backend configuration using the Amplify CLI, the configuration in `amplifyconfiguration.json` will update automatically.
## Install Amplify libraries