update few Xcode related screenshots, add dark theme images (#5124)

Author: Simek

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)
+<ThemedImage
+alt="Xcode Command Line Tools configuration"
+sources={{
+    light: '/docs/assets/GettingStartedXcodeCommandLineTools.png',
+    dark: '/docs/assets/GettingStartedXcodeCommandLineToolsDark.png',
+  }}
+/>
 
 #### Installing an iOS Simulator in Xcode
 

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 <RNTemplateRepoLink href
 
 Install the Command Line Tools. Choose **Settings... (or Preferences...)** in 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)
+<ThemedImage
+alt="Xcode Command Line Tools configuration"
+sources={{
+    light: '/docs/assets/GettingStartedXcodeCommandLineTools.png',
+    dark: '/docs/assets/GettingStartedXcodeCommandLineToolsDark.png',
+  }}
+/>
 
 ### CocoaPods
 

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)
+<ThemedImage
+alt="Xcode Release Scheme configuration"
+sources={{
+    light: '/docs/assets/ConfigureReleaseScheme.png',
+    dark: '/docs/assets/ConfigureReleaseSchemeDark.png',
+  }}
+/>
 
 #### Pro Tips
 

website/static/docs/assets/ConfigureReleaseScheme.png

@@ -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)
+<ThemedImage
+alt="Docusaurus themed image"
+sources={{
+    light: '/docs/assets/ConfigureReleaseScheme.png',
+    dark: '/docs/assets/ConfigureReleaseSchemeDark.png',
+  }}
+/>
 
 #### Pro Tips
 

website/static/docs/assets/ConfigureReleaseSchemeDark.png

@@ -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)
+<ThemedImage
+alt="Docusaurus themed image"
+sources={{
+    light: '/docs/assets/ConfigureReleaseScheme.png',
+    dark: '/docs/assets/ConfigureReleaseSchemeDark.png',
+  }}
+/>
 
 #### Pro Tips
 

website/static/docs/assets/GettingStartedXcodeCommandLineTools.png

@@ -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)
+<ThemedImage
+alt="Docusaurus themed image"
+sources={{
+    light: '/docs/assets/ConfigureReleaseScheme.png',
+    dark: '/docs/assets/ConfigureReleaseSchemeDark.png',
+  }}
+/>
 
 #### Pro Tips