docs(getting-started): add clarification about using EAS to build (#6492

) * docs(getting-started): add clarification about using EAS to build * docs(spellcheck): add EAS to the dictionary Co-authored-by: Mike Hardy <github@mikehardy.net>
invertase · Sep 8, 2022 · 1b3cf96 · 1b3cf96 · vercel · Sep 8, 2022
1 parent f10891a
commit 1b3cf96
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 1 deletion.
diff --git a/.spellcheck.dict.txt b/.spellcheck.dict.txt
@@ -53,6 +53,7 @@ DeviceCheck
 Diarmid
 Distribution
 dropdown
+EAS
 e2e
 EEA
 Ehesp

diff --git a/docs/index.md b/docs/index.md
@@ -311,7 +311,7 @@ The `app.json` for integration that included the optional crashlytics and perfor
 }
 ```
 
-Next, you need to use the `expo prebuild --clean` command as described in the ["Adding custom native code"](https://docs.expo.io/workflow/customizing/) guide to rebuild your app with the plugin changes. If this command isn't run, you'll encounter connection errors to Firebase.
+Next, you need to use the `expo prebuild --clean` command as described in the ["Adding custom native code"](https://docs.expo.io/workflow/customizing/) guide to rebuild your app with the plugin changes. If this command isn't run, you'll encounter connection errors to Firebase. Note, this is not required if you build your project with EAS (Expo Application Services).
 
 Config plugins are only required for React Native Firebase modules, which require custom native installation steps - e.g. modifying the Xcode project, `Podfile`, `build.gradle`, `AndroidManifest.xml` etc. Packages without native steps required will work out of the box.