diff --git a/docs/_getting-started-macos-ios.md b/docs/_getting-started-macos-ios.md index 84204758fb3..1c806573c2a 100644 --- a/docs/_getting-started-macos-ios.md +++ b/docs/_getting-started-macos-ios.md @@ -1,3 +1,5 @@ +import ThemedImage from '@theme/ThemedImage'; + ## Installing dependencies You will need Node, Watchman, the React Native command line interface, Xcode and CocoaPods. @@ -27,7 +29,13 @@ The easiest way to install Xcode is via the [Mac App Store](https://itunes.apple You will also need to install the Xcode Command Line Tools. Open Xcode, then choose **Settings... (or Preferences...)** from the Xcode menu. Go to the Locations panel and install the tools by selecting the most recent version in the Command Line Tools dropdown. -![Xcode Command Line Tools](/docs/assets/GettingStartedXcodeCommandLineTools.png) + #### Installing an iOS Simulator in Xcode diff --git a/docs/_integration-with-existing-apps-ios.md b/docs/_integration-with-existing-apps-ios.md index 1670717d84f..a0255f672a4 100644 --- a/docs/_integration-with-existing-apps-ios.md +++ b/docs/_integration-with-existing-apps-ios.md @@ -1,5 +1,6 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import ThemedImage from '@theme/ThemedImage'; import constants from '@site/core/TabsConstants'; import CodeBlock from '@theme/CodeBlock'; import RNTemplateRepoLink from '@site/core/RNTemplateRepoLink'; @@ -68,7 +69,13 @@ Add `node_modules/` to your `.gitignore` file (here the ### CocoaPods diff --git a/docs/publishing-to-app-store.md b/docs/publishing-to-app-store.md index 98c0d9b9ae9..478f2d3562a 100644 --- a/docs/publishing-to-app-store.md +++ b/docs/publishing-to-app-store.md @@ -3,6 +3,8 @@ id: publishing-to-app-store title: Publishing to Apple App Store --- +import ThemedImage from '@theme/ThemedImage'; + The publishing process is the same as any other native iOS app, with some additional considerations to take into account. :::info @@ -13,9 +15,15 @@ If you are using Expo, read the Expo guide for [Deploying to App Stores](https:/ Building an app for distribution in the App Store requires using the `Release` scheme in Xcode. Apps built for `Release` will automatically disable the in-app Dev Menu, which will prevent your users from inadvertently accessing the menu in production. It will also bundle the JavaScript locally, so you can put the app on a device and test whilst not connected to the computer. -To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the Build Configuration dropdown to `Release`. +To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the **Build Configuration** dropdown to `Release`. -![](/docs/assets/ConfigureReleaseScheme.png) + #### Pro Tips diff --git a/website/static/docs/assets/ConfigureReleaseScheme.png b/website/static/docs/assets/ConfigureReleaseScheme.png index 1adaf1229a9..17343d2452e 100644 Binary files a/website/static/docs/assets/ConfigureReleaseScheme.png and b/website/static/docs/assets/ConfigureReleaseScheme.png differ diff --git a/website/static/docs/assets/ConfigureReleaseSchemeDark.png b/website/static/docs/assets/ConfigureReleaseSchemeDark.png new file mode 100644 index 00000000000..41da875b5ae Binary files /dev/null and b/website/static/docs/assets/ConfigureReleaseSchemeDark.png differ diff --git a/website/static/docs/assets/GettingStartedXcodeCommandLineTools.png b/website/static/docs/assets/GettingStartedXcodeCommandLineTools.png index a3a36dd8a53..1ae9efa7a79 100644 Binary files a/website/static/docs/assets/GettingStartedXcodeCommandLineTools.png and b/website/static/docs/assets/GettingStartedXcodeCommandLineTools.png differ diff --git a/website/static/docs/assets/GettingStartedXcodeCommandLineToolsDark.png b/website/static/docs/assets/GettingStartedXcodeCommandLineToolsDark.png new file mode 100644 index 00000000000..a8043e20104 Binary files /dev/null and b/website/static/docs/assets/GettingStartedXcodeCommandLineToolsDark.png differ diff --git a/website/versioned_docs/version-0.77/publishing-to-app-store.md b/website/versioned_docs/version-0.77/publishing-to-app-store.md index 98c0d9b9ae9..dabdfc826f5 100644 --- a/website/versioned_docs/version-0.77/publishing-to-app-store.md +++ b/website/versioned_docs/version-0.77/publishing-to-app-store.md @@ -3,6 +3,8 @@ id: publishing-to-app-store title: Publishing to Apple App Store --- +import ThemedImage from '@theme/ThemedImage'; + The publishing process is the same as any other native iOS app, with some additional considerations to take into account. :::info @@ -13,9 +15,15 @@ If you are using Expo, read the Expo guide for [Deploying to App Stores](https:/ Building an app for distribution in the App Store requires using the `Release` scheme in Xcode. Apps built for `Release` will automatically disable the in-app Dev Menu, which will prevent your users from inadvertently accessing the menu in production. It will also bundle the JavaScript locally, so you can put the app on a device and test whilst not connected to the computer. -To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the Build Configuration dropdown to `Release`. +To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the **Build Configuration** dropdown to `Release`. -![](/docs/assets/ConfigureReleaseScheme.png) + #### Pro Tips diff --git a/website/versioned_docs/version-0.78/publishing-to-app-store.md b/website/versioned_docs/version-0.78/publishing-to-app-store.md index 98c0d9b9ae9..dabdfc826f5 100644 --- a/website/versioned_docs/version-0.78/publishing-to-app-store.md +++ b/website/versioned_docs/version-0.78/publishing-to-app-store.md @@ -3,6 +3,8 @@ id: publishing-to-app-store title: Publishing to Apple App Store --- +import ThemedImage from '@theme/ThemedImage'; + The publishing process is the same as any other native iOS app, with some additional considerations to take into account. :::info @@ -13,9 +15,15 @@ If you are using Expo, read the Expo guide for [Deploying to App Stores](https:/ Building an app for distribution in the App Store requires using the `Release` scheme in Xcode. Apps built for `Release` will automatically disable the in-app Dev Menu, which will prevent your users from inadvertently accessing the menu in production. It will also bundle the JavaScript locally, so you can put the app on a device and test whilst not connected to the computer. -To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the Build Configuration dropdown to `Release`. +To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the **Build Configuration** dropdown to `Release`. -![](/docs/assets/ConfigureReleaseScheme.png) + #### Pro Tips diff --git a/website/versioned_docs/version-0.79/publishing-to-app-store.md b/website/versioned_docs/version-0.79/publishing-to-app-store.md index 98c0d9b9ae9..dabdfc826f5 100644 --- a/website/versioned_docs/version-0.79/publishing-to-app-store.md +++ b/website/versioned_docs/version-0.79/publishing-to-app-store.md @@ -3,6 +3,8 @@ id: publishing-to-app-store title: Publishing to Apple App Store --- +import ThemedImage from '@theme/ThemedImage'; + The publishing process is the same as any other native iOS app, with some additional considerations to take into account. :::info @@ -13,9 +15,15 @@ If you are using Expo, read the Expo guide for [Deploying to App Stores](https:/ Building an app for distribution in the App Store requires using the `Release` scheme in Xcode. Apps built for `Release` will automatically disable the in-app Dev Menu, which will prevent your users from inadvertently accessing the menu in production. It will also bundle the JavaScript locally, so you can put the app on a device and test whilst not connected to the computer. -To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the Build Configuration dropdown to `Release`. +To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the **Build Configuration** dropdown to `Release`. -![](/docs/assets/ConfigureReleaseScheme.png) + #### Pro Tips diff --git a/website/versioned_docs/version-0.80/publishing-to-app-store.md b/website/versioned_docs/version-0.80/publishing-to-app-store.md index 98c0d9b9ae9..dabdfc826f5 100644 --- a/website/versioned_docs/version-0.80/publishing-to-app-store.md +++ b/website/versioned_docs/version-0.80/publishing-to-app-store.md @@ -3,6 +3,8 @@ id: publishing-to-app-store title: Publishing to Apple App Store --- +import ThemedImage from '@theme/ThemedImage'; + The publishing process is the same as any other native iOS app, with some additional considerations to take into account. :::info @@ -13,9 +15,15 @@ If you are using Expo, read the Expo guide for [Deploying to App Stores](https:/ Building an app for distribution in the App Store requires using the `Release` scheme in Xcode. Apps built for `Release` will automatically disable the in-app Dev Menu, which will prevent your users from inadvertently accessing the menu in production. It will also bundle the JavaScript locally, so you can put the app on a device and test whilst not connected to the computer. -To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the Build Configuration dropdown to `Release`. +To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the **Build Configuration** dropdown to `Release`. -![](/docs/assets/ConfigureReleaseScheme.png) + #### Pro Tips diff --git a/website/versioned_docs/version-0.81/publishing-to-app-store.md b/website/versioned_docs/version-0.81/publishing-to-app-store.md index 98c0d9b9ae9..dabdfc826f5 100644 --- a/website/versioned_docs/version-0.81/publishing-to-app-store.md +++ b/website/versioned_docs/version-0.81/publishing-to-app-store.md @@ -3,6 +3,8 @@ id: publishing-to-app-store title: Publishing to Apple App Store --- +import ThemedImage from '@theme/ThemedImage'; + The publishing process is the same as any other native iOS app, with some additional considerations to take into account. :::info @@ -13,9 +15,15 @@ If you are using Expo, read the Expo guide for [Deploying to App Stores](https:/ Building an app for distribution in the App Store requires using the `Release` scheme in Xcode. Apps built for `Release` will automatically disable the in-app Dev Menu, which will prevent your users from inadvertently accessing the menu in production. It will also bundle the JavaScript locally, so you can put the app on a device and test whilst not connected to the computer. -To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the Build Configuration dropdown to `Release`. +To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the **Build Configuration** dropdown to `Release`. -![](/docs/assets/ConfigureReleaseScheme.png) + #### Pro Tips diff --git a/website/versioned_docs/version-0.82/publishing-to-app-store.md b/website/versioned_docs/version-0.82/publishing-to-app-store.md index 98c0d9b9ae9..dabdfc826f5 100644 --- a/website/versioned_docs/version-0.82/publishing-to-app-store.md +++ b/website/versioned_docs/version-0.82/publishing-to-app-store.md @@ -3,6 +3,8 @@ id: publishing-to-app-store title: Publishing to Apple App Store --- +import ThemedImage from '@theme/ThemedImage'; + The publishing process is the same as any other native iOS app, with some additional considerations to take into account. :::info @@ -13,9 +15,15 @@ If you are using Expo, read the Expo guide for [Deploying to App Stores](https:/ Building an app for distribution in the App Store requires using the `Release` scheme in Xcode. Apps built for `Release` will automatically disable the in-app Dev Menu, which will prevent your users from inadvertently accessing the menu in production. It will also bundle the JavaScript locally, so you can put the app on a device and test whilst not connected to the computer. -To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the Build Configuration dropdown to `Release`. +To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the **Build Configuration** dropdown to `Release`. -![](/docs/assets/ConfigureReleaseScheme.png) + #### Pro Tips diff --git a/website/versioned_docs/version-0.83/_getting-started-macos-ios.md b/website/versioned_docs/version-0.83/_getting-started-macos-ios.md index 0980dd0f1a7..1cf601b1248 100644 --- a/website/versioned_docs/version-0.83/_getting-started-macos-ios.md +++ b/website/versioned_docs/version-0.83/_getting-started-macos-ios.md @@ -1,3 +1,5 @@ +import ThemedImage from '@theme/ThemedImage'; + ## Installing dependencies You will need Node, Watchman, the React Native command line interface, Xcode and CocoaPods. @@ -27,7 +29,13 @@ The easiest way to install Xcode is via the [Mac App Store](https://itunes.apple You will also need to install the Xcode Command Line Tools. Open Xcode, then choose **Settings... (or Preferences...)** from the Xcode menu. Go to the Locations panel and install the tools by selecting the most recent version in the Command Line Tools dropdown. -![Xcode Command Line Tools](/docs/assets/GettingStartedXcodeCommandLineTools.png) + #### Installing an iOS Simulator in Xcode diff --git a/website/versioned_docs/version-0.83/_integration-with-existing-apps-ios.md b/website/versioned_docs/version-0.83/_integration-with-existing-apps-ios.md index f28e3c48bf9..804945d88d7 100644 --- a/website/versioned_docs/version-0.83/_integration-with-existing-apps-ios.md +++ b/website/versioned_docs/version-0.83/_integration-with-existing-apps-ios.md @@ -1,5 +1,6 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import ThemedImage from '@theme/ThemedImage'; import constants from '@site/core/TabsConstants'; import CodeBlock from '@theme/CodeBlock'; import RNTemplateRepoLink from '@site/core/RNTemplateRepoLink'; @@ -68,7 +69,13 @@ Add `node_modules/` to your `.gitignore` file (here the ### CocoaPods diff --git a/website/versioned_docs/version-0.83/publishing-to-app-store.md b/website/versioned_docs/version-0.83/publishing-to-app-store.md index 98c0d9b9ae9..dabdfc826f5 100644 --- a/website/versioned_docs/version-0.83/publishing-to-app-store.md +++ b/website/versioned_docs/version-0.83/publishing-to-app-store.md @@ -3,6 +3,8 @@ id: publishing-to-app-store title: Publishing to Apple App Store --- +import ThemedImage from '@theme/ThemedImage'; + The publishing process is the same as any other native iOS app, with some additional considerations to take into account. :::info @@ -13,9 +15,15 @@ If you are using Expo, read the Expo guide for [Deploying to App Stores](https:/ Building an app for distribution in the App Store requires using the `Release` scheme in Xcode. Apps built for `Release` will automatically disable the in-app Dev Menu, which will prevent your users from inadvertently accessing the menu in production. It will also bundle the JavaScript locally, so you can put the app on a device and test whilst not connected to the computer. -To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the Build Configuration dropdown to `Release`. +To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the **Build Configuration** dropdown to `Release`. -![](/docs/assets/ConfigureReleaseScheme.png) + #### Pro Tips diff --git a/website/versioned_docs/version-0.84/_getting-started-macos-ios.md b/website/versioned_docs/version-0.84/_getting-started-macos-ios.md index 84204758fb3..1c806573c2a 100644 --- a/website/versioned_docs/version-0.84/_getting-started-macos-ios.md +++ b/website/versioned_docs/version-0.84/_getting-started-macos-ios.md @@ -1,3 +1,5 @@ +import ThemedImage from '@theme/ThemedImage'; + ## Installing dependencies You will need Node, Watchman, the React Native command line interface, Xcode and CocoaPods. @@ -27,7 +29,13 @@ The easiest way to install Xcode is via the [Mac App Store](https://itunes.apple You will also need to install the Xcode Command Line Tools. Open Xcode, then choose **Settings... (or Preferences...)** from the Xcode menu. Go to the Locations panel and install the tools by selecting the most recent version in the Command Line Tools dropdown. -![Xcode Command Line Tools](/docs/assets/GettingStartedXcodeCommandLineTools.png) + #### Installing an iOS Simulator in Xcode diff --git a/website/versioned_docs/version-0.84/_integration-with-existing-apps-ios.md b/website/versioned_docs/version-0.84/_integration-with-existing-apps-ios.md index f28e3c48bf9..804945d88d7 100644 --- a/website/versioned_docs/version-0.84/_integration-with-existing-apps-ios.md +++ b/website/versioned_docs/version-0.84/_integration-with-existing-apps-ios.md @@ -1,5 +1,6 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import ThemedImage from '@theme/ThemedImage'; import constants from '@site/core/TabsConstants'; import CodeBlock from '@theme/CodeBlock'; import RNTemplateRepoLink from '@site/core/RNTemplateRepoLink'; @@ -68,7 +69,13 @@ Add `node_modules/` to your `.gitignore` file (here the ### CocoaPods diff --git a/website/versioned_docs/version-0.84/publishing-to-app-store.md b/website/versioned_docs/version-0.84/publishing-to-app-store.md index 98c0d9b9ae9..dabdfc826f5 100644 --- a/website/versioned_docs/version-0.84/publishing-to-app-store.md +++ b/website/versioned_docs/version-0.84/publishing-to-app-store.md @@ -3,6 +3,8 @@ id: publishing-to-app-store title: Publishing to Apple App Store --- +import ThemedImage from '@theme/ThemedImage'; + The publishing process is the same as any other native iOS app, with some additional considerations to take into account. :::info @@ -13,9 +15,15 @@ If you are using Expo, read the Expo guide for [Deploying to App Stores](https:/ Building an app for distribution in the App Store requires using the `Release` scheme in Xcode. Apps built for `Release` will automatically disable the in-app Dev Menu, which will prevent your users from inadvertently accessing the menu in production. It will also bundle the JavaScript locally, so you can put the app on a device and test whilst not connected to the computer. -To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the Build Configuration dropdown to `Release`. +To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the **Build Configuration** dropdown to `Release`. -![](/docs/assets/ConfigureReleaseScheme.png) + #### Pro Tips diff --git a/website/versioned_docs/version-0.85/_getting-started-macos-ios.md b/website/versioned_docs/version-0.85/_getting-started-macos-ios.md index 84204758fb3..1c806573c2a 100644 --- a/website/versioned_docs/version-0.85/_getting-started-macos-ios.md +++ b/website/versioned_docs/version-0.85/_getting-started-macos-ios.md @@ -1,3 +1,5 @@ +import ThemedImage from '@theme/ThemedImage'; + ## Installing dependencies You will need Node, Watchman, the React Native command line interface, Xcode and CocoaPods. @@ -27,7 +29,13 @@ The easiest way to install Xcode is via the [Mac App Store](https://itunes.apple You will also need to install the Xcode Command Line Tools. Open Xcode, then choose **Settings... (or Preferences...)** from the Xcode menu. Go to the Locations panel and install the tools by selecting the most recent version in the Command Line Tools dropdown. -![Xcode Command Line Tools](/docs/assets/GettingStartedXcodeCommandLineTools.png) + #### Installing an iOS Simulator in Xcode diff --git a/website/versioned_docs/version-0.85/_integration-with-existing-apps-ios.md b/website/versioned_docs/version-0.85/_integration-with-existing-apps-ios.md index f28e3c48bf9..804945d88d7 100644 --- a/website/versioned_docs/version-0.85/_integration-with-existing-apps-ios.md +++ b/website/versioned_docs/version-0.85/_integration-with-existing-apps-ios.md @@ -1,5 +1,6 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import ThemedImage from '@theme/ThemedImage'; import constants from '@site/core/TabsConstants'; import CodeBlock from '@theme/CodeBlock'; import RNTemplateRepoLink from '@site/core/RNTemplateRepoLink'; @@ -68,7 +69,13 @@ Add `node_modules/` to your `.gitignore` file (here the ### CocoaPods diff --git a/website/versioned_docs/version-0.85/publishing-to-app-store.md b/website/versioned_docs/version-0.85/publishing-to-app-store.md index 98c0d9b9ae9..dabdfc826f5 100644 --- a/website/versioned_docs/version-0.85/publishing-to-app-store.md +++ b/website/versioned_docs/version-0.85/publishing-to-app-store.md @@ -3,6 +3,8 @@ id: publishing-to-app-store title: Publishing to Apple App Store --- +import ThemedImage from '@theme/ThemedImage'; + The publishing process is the same as any other native iOS app, with some additional considerations to take into account. :::info @@ -13,9 +15,15 @@ If you are using Expo, read the Expo guide for [Deploying to App Stores](https:/ Building an app for distribution in the App Store requires using the `Release` scheme in Xcode. Apps built for `Release` will automatically disable the in-app Dev Menu, which will prevent your users from inadvertently accessing the menu in production. It will also bundle the JavaScript locally, so you can put the app on a device and test whilst not connected to the computer. -To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the Build Configuration dropdown to `Release`. +To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the **Build Configuration** dropdown to `Release`. -![](/docs/assets/ConfigureReleaseScheme.png) + #### Pro Tips diff --git a/website/versioned_docs/version-0.86/_getting-started-macos-ios.md b/website/versioned_docs/version-0.86/_getting-started-macos-ios.md index 84204758fb3..1c806573c2a 100644 --- a/website/versioned_docs/version-0.86/_getting-started-macos-ios.md +++ b/website/versioned_docs/version-0.86/_getting-started-macos-ios.md @@ -1,3 +1,5 @@ +import ThemedImage from '@theme/ThemedImage'; + ## Installing dependencies You will need Node, Watchman, the React Native command line interface, Xcode and CocoaPods. @@ -27,7 +29,13 @@ The easiest way to install Xcode is via the [Mac App Store](https://itunes.apple You will also need to install the Xcode Command Line Tools. Open Xcode, then choose **Settings... (or Preferences...)** from the Xcode menu. Go to the Locations panel and install the tools by selecting the most recent version in the Command Line Tools dropdown. -![Xcode Command Line Tools](/docs/assets/GettingStartedXcodeCommandLineTools.png) + #### Installing an iOS Simulator in Xcode diff --git a/website/versioned_docs/version-0.86/_integration-with-existing-apps-ios.md b/website/versioned_docs/version-0.86/_integration-with-existing-apps-ios.md index f28e3c48bf9..804945d88d7 100644 --- a/website/versioned_docs/version-0.86/_integration-with-existing-apps-ios.md +++ b/website/versioned_docs/version-0.86/_integration-with-existing-apps-ios.md @@ -1,5 +1,6 @@ import Tabs from '@theme/Tabs'; import TabItem from '@theme/TabItem'; +import ThemedImage from '@theme/ThemedImage'; import constants from '@site/core/TabsConstants'; import CodeBlock from '@theme/CodeBlock'; import RNTemplateRepoLink from '@site/core/RNTemplateRepoLink'; @@ -68,7 +69,13 @@ Add `node_modules/` to your `.gitignore` file (here the ### CocoaPods diff --git a/website/versioned_docs/version-0.86/publishing-to-app-store.md b/website/versioned_docs/version-0.86/publishing-to-app-store.md index 98c0d9b9ae9..dabdfc826f5 100644 --- a/website/versioned_docs/version-0.86/publishing-to-app-store.md +++ b/website/versioned_docs/version-0.86/publishing-to-app-store.md @@ -3,6 +3,8 @@ id: publishing-to-app-store title: Publishing to Apple App Store --- +import ThemedImage from '@theme/ThemedImage'; + The publishing process is the same as any other native iOS app, with some additional considerations to take into account. :::info @@ -13,9 +15,15 @@ If you are using Expo, read the Expo guide for [Deploying to App Stores](https:/ Building an app for distribution in the App Store requires using the `Release` scheme in Xcode. Apps built for `Release` will automatically disable the in-app Dev Menu, which will prevent your users from inadvertently accessing the menu in production. It will also bundle the JavaScript locally, so you can put the app on a device and test whilst not connected to the computer. -To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the Build Configuration dropdown to `Release`. +To configure your app to be built using the `Release` scheme, go to **Product** → **Scheme** → **Edit Scheme**. Select the **Run** tab in the sidebar, then set the **Build Configuration** dropdown to `Release`. -![](/docs/assets/ConfigureReleaseScheme.png) + #### Pro Tips