You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.10/getting-started.html b/docs/0.10/getting-started.html
index 2c7e39ad652..05513573b6a 100644
--- a/docs/0.10/getting-started.html
+++ b/docs/0.10/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.10/getting-started/index.html b/docs/0.10/getting-started/index.html
index 2c7e39ad652..05513573b6a 100644
--- a/docs/0.10/getting-started/index.html
+++ b/docs/0.10/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.11/getting-started.html b/docs/0.11/getting-started.html
index 3ce8df7e517..a018da34411 100644
--- a/docs/0.11/getting-started.html
+++ b/docs/0.11/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.11/getting-started/index.html b/docs/0.11/getting-started/index.html
index 3ce8df7e517..a018da34411 100644
--- a/docs/0.11/getting-started/index.html
+++ b/docs/0.11/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.12/getting-started.html b/docs/0.12/getting-started.html
index 5a642473d86..7ef41aaf639 100644
--- a/docs/0.12/getting-started.html
+++ b/docs/0.12/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.12/getting-started/index.html b/docs/0.12/getting-started/index.html
index 5a642473d86..7ef41aaf639 100644
--- a/docs/0.12/getting-started/index.html
+++ b/docs/0.12/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.13/getting-started.html b/docs/0.13/getting-started.html
index 70920cf4e98..e445e1edb0b 100644
--- a/docs/0.13/getting-started.html
+++ b/docs/0.13/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.13/getting-started/index.html b/docs/0.13/getting-started/index.html
index 70920cf4e98..e445e1edb0b 100644
--- a/docs/0.13/getting-started/index.html
+++ b/docs/0.13/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.14/getting-started.html b/docs/0.14/getting-started.html
index 18d7dfd86a6..0b25d0a2c96 100644
--- a/docs/0.14/getting-started.html
+++ b/docs/0.14/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.14/getting-started/index.html b/docs/0.14/getting-started/index.html
index 18d7dfd86a6..0b25d0a2c96 100644
--- a/docs/0.14/getting-started/index.html
+++ b/docs/0.14/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.15/getting-started.html b/docs/0.15/getting-started.html
index a8e9543e360..a9f82ada04c 100644
--- a/docs/0.15/getting-started.html
+++ b/docs/0.15/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.15/getting-started/index.html b/docs/0.15/getting-started/index.html
index a8e9543e360..a9f82ada04c 100644
--- a/docs/0.15/getting-started/index.html
+++ b/docs/0.15/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.16/getting-started.html b/docs/0.16/getting-started.html
index a031e4b1b68..5f2ae22bdf6 100644
--- a/docs/0.16/getting-started.html
+++ b/docs/0.16/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.16/getting-started/index.html b/docs/0.16/getting-started/index.html
index a031e4b1b68..5f2ae22bdf6 100644
--- a/docs/0.16/getting-started/index.html
+++ b/docs/0.16/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.17/getting-started.html b/docs/0.17/getting-started.html
index 82d9b76e456..bfa88d02711 100644
--- a/docs/0.17/getting-started.html
+++ b/docs/0.17/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.17/getting-started/index.html b/docs/0.17/getting-started/index.html
index 82d9b76e456..bfa88d02711 100644
--- a/docs/0.17/getting-started/index.html
+++ b/docs/0.17/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.18/getting-started.html b/docs/0.18/getting-started.html
index fed1bfca2b6..ad208393934 100644
--- a/docs/0.18/getting-started.html
+++ b/docs/0.18/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.18/getting-started/index.html b/docs/0.18/getting-started/index.html
index fed1bfca2b6..ad208393934 100644
--- a/docs/0.18/getting-started/index.html
+++ b/docs/0.18/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.19/getting-started.html b/docs/0.19/getting-started.html
index 618c7b67e02..9fd7bc3efc9 100644
--- a/docs/0.19/getting-started.html
+++ b/docs/0.19/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.19/getting-started/index.html b/docs/0.19/getting-started/index.html
index 618c7b67e02..9fd7bc3efc9 100644
--- a/docs/0.19/getting-started/index.html
+++ b/docs/0.19/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.20/getting-started.html b/docs/0.20/getting-started.html
index ff4b1f2acec..3363c976e00 100644
--- a/docs/0.20/getting-started.html
+++ b/docs/0.20/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.20/getting-started/index.html b/docs/0.20/getting-started/index.html
index ff4b1f2acec..3363c976e00 100644
--- a/docs/0.20/getting-started/index.html
+++ b/docs/0.20/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.21/getting-started.html b/docs/0.21/getting-started.html
index ba9e5d5d581..7ca074907e1 100644
--- a/docs/0.21/getting-started.html
+++ b/docs/0.21/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.21/getting-started/index.html b/docs/0.21/getting-started/index.html
index ba9e5d5d581..7ca074907e1 100644
--- a/docs/0.21/getting-started/index.html
+++ b/docs/0.21/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.22/getting-started.html b/docs/0.22/getting-started.html
index 3529fce9424..53871927275 100644
--- a/docs/0.22/getting-started.html
+++ b/docs/0.22/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.22/getting-started/index.html b/docs/0.22/getting-started/index.html
index 3529fce9424..53871927275 100644
--- a/docs/0.22/getting-started/index.html
+++ b/docs/0.22/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.23/getting-started.html b/docs/0.23/getting-started.html
index ad2b1829e8e..86cc44882b4 100644
--- a/docs/0.23/getting-started.html
+++ b/docs/0.23/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.23/getting-started/index.html b/docs/0.23/getting-started/index.html
index ad2b1829e8e..86cc44882b4 100644
--- a/docs/0.23/getting-started/index.html
+++ b/docs/0.23/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.24/getting-started.html b/docs/0.24/getting-started.html
index 7e38cf7c232..53a025cd524 100644
--- a/docs/0.24/getting-started.html
+++ b/docs/0.24/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.24/getting-started/index.html b/docs/0.24/getting-started/index.html
index 7e38cf7c232..53a025cd524 100644
--- a/docs/0.24/getting-started/index.html
+++ b/docs/0.24/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.25/getting-started.html b/docs/0.25/getting-started.html
index edb8ba094e1..7f67d5531e5 100644
--- a/docs/0.25/getting-started.html
+++ b/docs/0.25/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.25/getting-started/index.html b/docs/0.25/getting-started/index.html
index edb8ba094e1..7f67d5531e5 100644
--- a/docs/0.25/getting-started/index.html
+++ b/docs/0.25/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.26/getting-started.html b/docs/0.26/getting-started.html
index 7e9d6dd1d4c..4e67a4395de 100644
--- a/docs/0.26/getting-started.html
+++ b/docs/0.26/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.26/getting-started/index.html b/docs/0.26/getting-started/index.html
index 7e9d6dd1d4c..4e67a4395de 100644
--- a/docs/0.26/getting-started/index.html
+++ b/docs/0.26/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.27/getting-started.html b/docs/0.27/getting-started.html
index afb50d710d4..f8cfcaadb5d 100644
--- a/docs/0.27/getting-started.html
+++ b/docs/0.27/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.27/getting-started/index.html b/docs/0.27/getting-started/index.html
index afb50d710d4..f8cfcaadb5d 100644
--- a/docs/0.27/getting-started/index.html
+++ b/docs/0.27/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.28/getting-started.html b/docs/0.28/getting-started.html
index f0738a99d22..23e50a13c64 100644
--- a/docs/0.28/getting-started.html
+++ b/docs/0.28/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.28/getting-started/index.html b/docs/0.28/getting-started/index.html
index f0738a99d22..23e50a13c64 100644
--- a/docs/0.28/getting-started/index.html
+++ b/docs/0.28/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.29/getting-started.html b/docs/0.29/getting-started.html
index 24cc48cd940..fa53eaec3a0 100644
--- a/docs/0.29/getting-started.html
+++ b/docs/0.29/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.29/getting-started/index.html b/docs/0.29/getting-started/index.html
index 24cc48cd940..fa53eaec3a0 100644
--- a/docs/0.29/getting-started/index.html
+++ b/docs/0.29/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.30/getting-started.html b/docs/0.30/getting-started.html
index cdf7777b659..01970f1fd62 100644
--- a/docs/0.30/getting-started.html
+++ b/docs/0.30/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.30/getting-started/index.html b/docs/0.30/getting-started/index.html
index cdf7777b659..01970f1fd62 100644
--- a/docs/0.30/getting-started/index.html
+++ b/docs/0.30/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.31/getting-started.html b/docs/0.31/getting-started.html
index 51c9686f114..1604d0342c9 100644
--- a/docs/0.31/getting-started.html
+++ b/docs/0.31/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.31/getting-started/index.html b/docs/0.31/getting-started/index.html
index 51c9686f114..1604d0342c9 100644
--- a/docs/0.31/getting-started/index.html
+++ b/docs/0.31/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.32/getting-started.html b/docs/0.32/getting-started.html
index bea9be4bebd..67c4a92022f 100644
--- a/docs/0.32/getting-started.html
+++ b/docs/0.32/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.32/getting-started/index.html b/docs/0.32/getting-started/index.html
index bea9be4bebd..67c4a92022f 100644
--- a/docs/0.32/getting-started/index.html
+++ b/docs/0.32/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.33/getting-started.html b/docs/0.33/getting-started.html
index af69f2f6627..50e368d249a 100644
--- a/docs/0.33/getting-started.html
+++ b/docs/0.33/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.33/getting-started/index.html b/docs/0.33/getting-started/index.html
index af69f2f6627..50e368d249a 100644
--- a/docs/0.33/getting-started/index.html
+++ b/docs/0.33/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.34/getting-started.html b/docs/0.34/getting-started.html
index 22a04e39105..4ba16a49618 100644
--- a/docs/0.34/getting-started.html
+++ b/docs/0.34/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.34/getting-started/index.html b/docs/0.34/getting-started/index.html
index 22a04e39105..4ba16a49618 100644
--- a/docs/0.34/getting-started/index.html
+++ b/docs/0.34/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.35/getting-started.html b/docs/0.35/getting-started.html
index 9f978027ced..da03ccb3710 100644
--- a/docs/0.35/getting-started.html
+++ b/docs/0.35/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.35/getting-started/index.html b/docs/0.35/getting-started/index.html
index 9f978027ced..da03ccb3710 100644
--- a/docs/0.35/getting-started/index.html
+++ b/docs/0.35/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.36/getting-started.html b/docs/0.36/getting-started.html
index cb4f2a64050..d17a79d2f17 100644
--- a/docs/0.36/getting-started.html
+++ b/docs/0.36/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.36/getting-started/index.html b/docs/0.36/getting-started/index.html
index cb4f2a64050..d17a79d2f17 100644
--- a/docs/0.36/getting-started/index.html
+++ b/docs/0.36/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.37/getting-started.html b/docs/0.37/getting-started.html
index d6c3d7fb2cf..98d8b37aac1 100644
--- a/docs/0.37/getting-started.html
+++ b/docs/0.37/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.37/getting-started/index.html b/docs/0.37/getting-started/index.html
index d6c3d7fb2cf..98d8b37aac1 100644
--- a/docs/0.37/getting-started/index.html
+++ b/docs/0.37/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.38/getting-started.html b/docs/0.38/getting-started.html
index 33672ae0c6c..be70c5120ce 100644
--- a/docs/0.38/getting-started.html
+++ b/docs/0.38/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.38/getting-started/index.html b/docs/0.38/getting-started/index.html
index 33672ae0c6c..be70c5120ce 100644
--- a/docs/0.38/getting-started/index.html
+++ b/docs/0.38/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.39/getting-started.html b/docs/0.39/getting-started.html
index cbde9ddee67..6deed0de424 100644
--- a/docs/0.39/getting-started.html
+++ b/docs/0.39/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.39/getting-started/index.html b/docs/0.39/getting-started/index.html
index cbde9ddee67..6deed0de424 100644
--- a/docs/0.39/getting-started/index.html
+++ b/docs/0.39/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.40/getting-started.html b/docs/0.40/getting-started.html
index 6bc797f0638..57b266a7e2e 100644
--- a/docs/0.40/getting-started.html
+++ b/docs/0.40/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.40/getting-started/index.html b/docs/0.40/getting-started/index.html
index 6bc797f0638..57b266a7e2e 100644
--- a/docs/0.40/getting-started/index.html
+++ b/docs/0.40/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.41/getting-started.html b/docs/0.41/getting-started.html
index 60ae7a3f8c7..ffe1e2cb6d4 100644
--- a/docs/0.41/getting-started.html
+++ b/docs/0.41/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.41/getting-started/index.html b/docs/0.41/getting-started/index.html
index 60ae7a3f8c7..ffe1e2cb6d4 100644
--- a/docs/0.41/getting-started/index.html
+++ b/docs/0.41/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.42/getting-started.html b/docs/0.42/getting-started.html
index 05af0aa5a82..a40320f4aa8 100644
--- a/docs/0.42/getting-started.html
+++ b/docs/0.42/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.42/getting-started/index.html b/docs/0.42/getting-started/index.html
index 05af0aa5a82..a40320f4aa8 100644
--- a/docs/0.42/getting-started/index.html
+++ b/docs/0.42/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.43/getting-started.html b/docs/0.43/getting-started.html
index d6c50531b77..0c973dec039 100644
--- a/docs/0.43/getting-started.html
+++ b/docs/0.43/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.43/getting-started/index.html b/docs/0.43/getting-started/index.html
index d6c50531b77..0c973dec039 100644
--- a/docs/0.43/getting-started/index.html
+++ b/docs/0.43/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.44/getting-started.html b/docs/0.44/getting-started.html
index 0d466adcbae..709f6ed88b2 100644
--- a/docs/0.44/getting-started.html
+++ b/docs/0.44/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.44/getting-started/index.html b/docs/0.44/getting-started/index.html
index 0d466adcbae..709f6ed88b2 100644
--- a/docs/0.44/getting-started/index.html
+++ b/docs/0.44/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.45/getting-started.html b/docs/0.45/getting-started.html
index fde08c2dc42..de276da009e 100644
--- a/docs/0.45/getting-started.html
+++ b/docs/0.45/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.45/getting-started/index.html b/docs/0.45/getting-started/index.html
index fde08c2dc42..de276da009e 100644
--- a/docs/0.45/getting-started/index.html
+++ b/docs/0.45/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.46/getting-started.html b/docs/0.46/getting-started.html
index 938e74f3b11..cd0df9e6848 100644
--- a/docs/0.46/getting-started.html
+++ b/docs/0.46/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.46/getting-started/index.html b/docs/0.46/getting-started/index.html
index 938e74f3b11..cd0df9e6848 100644
--- a/docs/0.46/getting-started/index.html
+++ b/docs/0.46/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.47/getting-started.html b/docs/0.47/getting-started.html
index aa45e591180..e03748f20eb 100644
--- a/docs/0.47/getting-started.html
+++ b/docs/0.47/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.47/getting-started/index.html b/docs/0.47/getting-started/index.html
index aa45e591180..e03748f20eb 100644
--- a/docs/0.47/getting-started/index.html
+++ b/docs/0.47/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.48/getting-started.html b/docs/0.48/getting-started.html
index 71392e88d34..c3f612e98e9 100644
--- a/docs/0.48/getting-started.html
+++ b/docs/0.48/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.48/getting-started/index.html b/docs/0.48/getting-started/index.html
index 71392e88d34..c3f612e98e9 100644
--- a/docs/0.48/getting-started/index.html
+++ b/docs/0.48/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.49/getting-started.html b/docs/0.49/getting-started.html
index 50794a8adec..13e22c69ced 100644
--- a/docs/0.49/getting-started.html
+++ b/docs/0.49/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.49/getting-started/index.html b/docs/0.49/getting-started/index.html
index 50794a8adec..13e22c69ced 100644
--- a/docs/0.49/getting-started/index.html
+++ b/docs/0.49/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.5/getting-started.html b/docs/0.5/getting-started.html
index fe2e95fb35a..1175106d004 100644
--- a/docs/0.5/getting-started.html
+++ b/docs/0.5/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.5/getting-started/index.html b/docs/0.5/getting-started/index.html
index fe2e95fb35a..1175106d004 100644
--- a/docs/0.5/getting-started/index.html
+++ b/docs/0.5/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.50/getting-started.html b/docs/0.50/getting-started.html
index 178c006cbe5..8db65fa7c7f 100644
--- a/docs/0.50/getting-started.html
+++ b/docs/0.50/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.50/getting-started/index.html b/docs/0.50/getting-started/index.html
index 178c006cbe5..8db65fa7c7f 100644
--- a/docs/0.50/getting-started/index.html
+++ b/docs/0.50/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.51/getting-started.html b/docs/0.51/getting-started.html
index 6ff4ce4a255..662c368472f 100644
--- a/docs/0.51/getting-started.html
+++ b/docs/0.51/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.51/getting-started/index.html b/docs/0.51/getting-started/index.html
index 6ff4ce4a255..662c368472f 100644
--- a/docs/0.51/getting-started/index.html
+++ b/docs/0.51/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.52/getting-started.html b/docs/0.52/getting-started.html
index a81fe4a42a9..dc549a61881 100644
--- a/docs/0.52/getting-started.html
+++ b/docs/0.52/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.52/getting-started/index.html b/docs/0.52/getting-started/index.html
index a81fe4a42a9..dc549a61881 100644
--- a/docs/0.52/getting-started/index.html
+++ b/docs/0.52/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.53/getting-started.html b/docs/0.53/getting-started.html
index b5be9daa579..02137384a4a 100644
--- a/docs/0.53/getting-started.html
+++ b/docs/0.53/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.53/getting-started/index.html b/docs/0.53/getting-started/index.html
index b5be9daa579..02137384a4a 100644
--- a/docs/0.53/getting-started/index.html
+++ b/docs/0.53/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.54/getting-started.html b/docs/0.54/getting-started.html
index 36442e60062..79c6acaf956 100644
--- a/docs/0.54/getting-started.html
+++ b/docs/0.54/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.54/getting-started/index.html b/docs/0.54/getting-started/index.html
index 36442e60062..79c6acaf956 100644
--- a/docs/0.54/getting-started/index.html
+++ b/docs/0.54/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.55/getting-started.html b/docs/0.55/getting-started.html
index b9aa4f7988c..e3fa42b2d73 100644
--- a/docs/0.55/getting-started.html
+++ b/docs/0.55/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.55/getting-started/index.html b/docs/0.55/getting-started/index.html
index b9aa4f7988c..e3fa42b2d73 100644
--- a/docs/0.55/getting-started/index.html
+++ b/docs/0.55/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.56/getting-started.html b/docs/0.56/getting-started.html
index ba3c17cf579..b204cadd4ee 100644
--- a/docs/0.56/getting-started.html
+++ b/docs/0.56/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.56/getting-started/index.html b/docs/0.56/getting-started/index.html
index ba3c17cf579..b204cadd4ee 100644
--- a/docs/0.56/getting-started/index.html
+++ b/docs/0.56/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.57/getting-started.html b/docs/0.57/getting-started.html
index 61d15063917..3ef59e3e02d 100644
--- a/docs/0.57/getting-started.html
+++ b/docs/0.57/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.57/getting-started/index.html b/docs/0.57/getting-started/index.html
index 61d15063917..3ef59e3e02d 100644
--- a/docs/0.57/getting-started/index.html
+++ b/docs/0.57/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.58/getting-started.html b/docs/0.58/getting-started.html
index 83567362cf0..fcbb9625656 100644
--- a/docs/0.58/getting-started.html
+++ b/docs/0.58/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.58/getting-started/index.html b/docs/0.58/getting-started/index.html
index 83567362cf0..fcbb9625656 100644
--- a/docs/0.58/getting-started/index.html
+++ b/docs/0.58/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.59/getting-started.html b/docs/0.59/getting-started.html
index 1be613dba27..1c618247392 100644
--- a/docs/0.59/getting-started.html
+++ b/docs/0.59/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.59/getting-started/index.html b/docs/0.59/getting-started/index.html
index 1be613dba27..1c618247392 100644
--- a/docs/0.59/getting-started/index.html
+++ b/docs/0.59/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.6/getting-started.html b/docs/0.6/getting-started.html
index 82f144492d4..34ea10c43a2 100644
--- a/docs/0.6/getting-started.html
+++ b/docs/0.6/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.6/getting-started/index.html b/docs/0.6/getting-started/index.html
index 82f144492d4..34ea10c43a2 100644
--- a/docs/0.6/getting-started/index.html
+++ b/docs/0.6/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
This API only works in projects made with react-native init
or in those made with expo init or Create React Native App which have since ejected. For
more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ the guide on
+ the Expo documentation..
AppRegistry is the JS entry point to running all React Native apps. App root components should register themselves with AppRegistry.registerComponent, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking AppRegistry.runApplication.
This API only works in projects made with react-native init
or in those made with expo init or Create React Native App which have since ejected. For
more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ the guide on
+ the Expo documentation..
AppRegistry is the JS entry point to running all React Native apps. App root components should register themselves with AppRegistry.registerComponent, then the native system can load the bundle for the app and then actually run the app when it's ready by invoking AppRegistry.runApplication.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
You can enable a performance overlay to help you debug performance problems by selecting "Perf Monitor" in the Developer Menu.
-
Debugging in Ejected Apps
-
+
Native Debugging
+
Projects with Native Code Only
- The remainder of this guide only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on ejecting to use this API.
Accessing console logs
diff --git a/docs/0.60/getting-started.html b/docs/0.60/getting-started.html
index 79b33271d64..bffd1cecb54 100644
--- a/docs/0.60/getting-started.html
+++ b/docs/0.60/getting-started.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
diff --git a/docs/0.60/getting-started/index.html b/docs/0.60/getting-started/index.html
index 79b33271d64..bffd1cecb54 100644
--- a/docs/0.60/getting-started/index.html
+++ b/docs/0.60/getting-started/index.html
@@ -113,8 +113,8 @@ npm start # you can also use: expo start
Once you've set these up, you can launch your app on an Android Virtual Device by running npm run android, or on the iOS Simulator by running npm run ios (macOS only).
Caveats
Because you don't build any native code when using Expo to create a project, it's not possible to include custom native modules beyond the React Native APIs and components that are available in the Expo client app.
-
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
-
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
+
If you know that you'll eventually need to include your own native code, Expo is still a good way to get started. In that case you'll just need to "eject" eventually to create your own native builds. If you do eject, the "React Native CLI Quickstart" instructions will be required to continue working on your project.
+
Expo CLI configures your project to use the most recent React Native version that is supported by the Expo client app. The Expo client app usually gains support for a given React Native version about a week after the React Native version is released as stable. You can check this document to find out what versions are supported.
If you're integrating React Native into an existing project, you'll want to skip Expo CLI and go directly to setting up the native build environment. Select "React Native CLI Quickstart" above for instructions on configuring a native build environment for React Native.
Follow these instructions if you need to build native code in your project. For example, if you are integrating React Native into an existing application, or if you "ejected" from Expo, you'll need this section.
- This section only applies to projects made with react-native init
- or to those made with expo init or Create React Native App which have since ejected. For
- more information about ejecting, please see
- the guide on
- the Create React Native App repository.
+ The following section only applies to projects with native code exposed. If you are using the managed `expo-cli` workflow, see the guide on Linking in the Expo documentation for the appropriate alternative.
Linking gives you a general interface to interact with both incoming and outgoing app links.