From e1aefb9037f60dfe21f46388adef675022421bf6 Mon Sep 17 00:00:00 2001 From: Aman Mittal Date: Wed, 8 May 2024 21:15:55 +0530 Subject: [PATCH] Minor fixes --- .../tutorial/eas/android-production-build.mdx | 2 +- .../tutorial/eas/configure-development-build.mdx | 8 ++++---- .../tutorial/eas/internal-distribution-builds.mdx | 2 +- docs/pages/tutorial/eas/introduction.mdx | 2 +- .../eas/ios-development-build-for-devices.mdx | 2 +- docs/pages/tutorial/eas/ios-production-build.mdx | 2 +- docs/pages/tutorial/eas/manage-app-versions.mdx | 14 +++++++++----- docs/pages/tutorial/eas/multiple-app-variants.mdx | 7 ++++--- docs/pages/tutorial/eas/next-steps.mdx | 2 +- docs/pages/tutorial/eas/team-development.mdx | 10 ++++++++-- docs/pages/tutorial/eas/using-github.mdx | 4 ++-- 11 files changed, 33 insertions(+), 22 deletions(-) diff --git a/docs/pages/tutorial/eas/android-production-build.mdx b/docs/pages/tutorial/eas/android-production-build.mdx index e8e85cb31d6d0..e3aecb67a264b 100644 --- a/docs/pages/tutorial/eas/android-production-build.mdx +++ b/docs/pages/tutorial/eas/android-production-build.mdx @@ -299,7 +299,7 @@ For subsequent releases in future, we can streamline the process by combining bu <> We successfully created a production-ready Android build, discussed manual and automated uploading to Google Play Store using eas submit, and automated the release - process with the --auto-submit flag. + process with the --auto-submit. } nextChapterDescription=" diff --git a/docs/pages/tutorial/eas/configure-development-build.mdx b/docs/pages/tutorial/eas/configure-development-build.mdx index b75e6b8192bb6..a84098e0f7f3c 100644 --- a/docs/pages/tutorial/eas/configure-development-build.mdx +++ b/docs/pages/tutorial/eas/configure-development-build.mdx @@ -17,7 +17,7 @@ In this chapter, we'll set up and configure a development build with EAS for our Let's start by learning about what are development builds and why we need them. -A [development build](/develop/development-builds/introduction/) is a debug version of our project. It is optimized for quick iterations when creating an app.IT contains the [`expo-dev-client`](/versions/latest/sdk/dev-client/) library, which offers a robust and complete development environment. This setup allows us to integrate any native library or change code inside the [native directories](/workflow/overview/#android-and-ios-native-projects) as required. +A [development build](/develop/development-builds/introduction/) is a debug version of our project. It is optimized for quick iterations when creating an app. It contains the [`expo-dev-client`](/versions/latest/sdk/dev-client/) library, which offers a robust and complete development environment. This setup allows us to integrate any native library or change code inside the [native directories](/workflow/overview/#android-and-ios-native-projects) as required. ### Key highlights @@ -41,7 +41,7 @@ To initialize our project for a development build, let's [`cd`](https://develope ### Start the development server -Run the `npx expo start` to start the [development server](/get-started/create-a-project/#start-the-development-server): +Run the `npx expo start` to start the [development server](/get-started/start-developing/#start-a-development-server): @@ -80,7 +80,7 @@ To log in, run the following command: -This command asks for our EAS email or username and password to complete the login. +This command asks for our Expo account email or username and password to complete the login. ### Initialize and link the project to EAS @@ -192,7 +192,7 @@ Currently, our focus is on the `development` profile, which includes the followi currentChapterIndex={0} name="EAS_TUTORIAL" summary=" -We successfully the EAS CLI to install, initialize, and configure our project, linking the project to EAS servers and preparing a development build." +We successfully used the EAS CLI to initialize, and configure our project, link it to EAS servers, and prepare a development build." nextChapterDescription="In the next chapter, let's create a development build for Android, install it on a device and an emulator, and get it running with the development server." nextChapterTitle="Create and run a cloud build for Android" nextChapterLink="/tutorial/eas/android-development-build/" diff --git a/docs/pages/tutorial/eas/internal-distribution-builds.mdx b/docs/pages/tutorial/eas/internal-distribution-builds.mdx index 43f4eb7e13bc7..60b6292d41a76 100644 --- a/docs/pages/tutorial/eas/internal-distribution-builds.mdx +++ b/docs/pages/tutorial/eas/internal-distribution-builds.mdx @@ -182,7 +182,7 @@ Since we have already set up multiple app variants, we can see both the developm We successfully created a production-ready iOS build, discussed distribution using TestFlight and Apple App Store using eas submit, and automated the release process with the{' '} - --auto-submit flag. + --auto-submit. } nextChapterDescription="In the next chapter, learn how to use the EAS Update to send OTA updates and share previews with our team." diff --git a/docs/pages/tutorial/eas/manage-app-versions.mdx b/docs/pages/tutorial/eas/manage-app-versions.mdx index a9305b000e814..3cdc281f5b0b2 100644 --- a/docs/pages/tutorial/eas/manage-app-versions.mdx +++ b/docs/pages/tutorial/eas/manage-app-versions.mdx @@ -23,11 +23,15 @@ We can manually manage developer-facing values by setting them as `android.versi ```json app.config.js { "ios": { + /* @info */ "buildNumber": "1" + /* @end */ /* @hide ... */ /* @end */ }, "android": { + /* @info */ "versionCode": "1" + /* @end */ } /* @hide ... */ /* @end */ } @@ -51,13 +55,13 @@ In **eas.json**: { "cli": { /* @hide ... */ /* @end */ - /* @info Add appVersionSource and set it to remote. */ + /* @info Add appVersionSource and set it to remote. */ "appVersionSource": "remote" /* @end */ }, "build": { "production": { - /* @info Set the autoIncrement property to true to automatically increment the versionCode or buildNumber */ + /* @info Set the autoIncrement property to true to automatically increment the versionCode or buildNumber. */ "autoIncrement": true /* @end */ } @@ -66,7 +70,7 @@ In **eas.json**: } ``` -When we create a new production build in the next two chapters, the `versionCode` for Android or `buildNumber` for iOS will increment automatically. +When we create a new production build in the next two chapters, the `versionCode` for Android and `buildNumber` for iOS will increment automatically. ## Summary @@ -75,9 +79,9 @@ When we create a new production build in the next two chapters, the `versionCode name="EAS_TUTORIAL" summary={ <> - We successfully explored app versioning differences, addressed the importance of unique + We successfully explored app versioning differences, addressed the importance of unique app versions to prevent store rejections, and enabled automated version updates in{' '} - eas.json for production. + eas.json for production builds. } nextChapterDescription="In the next chapter, learn about the process of creating a production build for Android." diff --git a/docs/pages/tutorial/eas/multiple-app-variants.mdx b/docs/pages/tutorial/eas/multiple-app-variants.mdx index 3e3fc7476150a..3734808e765a1 100644 --- a/docs/pages/tutorial/eas/multiple-app-variants.mdx +++ b/docs/pages/tutorial/eas/multiple-app-variants.mdx @@ -178,9 +178,10 @@ Now, our development build will run on both Android and iOS, displaying the modi name="EAS_TUTORIAL" summary={ <> - We successfully configured various build types, switched to app.config.js for - dynamic settings, added environment variables in eas.json, and started the - development server using a custom package.json script. + We successfully switched to app.config.js for dynamic settings, added + environment variables in eas.json to configure specific build profile, and + learned how to start the development server with a custom package.json{' '} + script. } nextChapterDescription="In the next chapter, learn about what are internal distribution builds, why we need them, and how to create them." diff --git a/docs/pages/tutorial/eas/next-steps.mdx b/docs/pages/tutorial/eas/next-steps.mdx index aaf89b735ed41..ebbdff5fe129f 100644 --- a/docs/pages/tutorial/eas/next-steps.mdx +++ b/docs/pages/tutorial/eas/next-steps.mdx @@ -65,7 +65,7 @@ But this is just the beginning. Here are some next steps to continue your journe diff --git a/docs/pages/tutorial/eas/team-development.mdx b/docs/pages/tutorial/eas/team-development.mdx index b03d720b652aa..d53e854964e6b 100644 --- a/docs/pages/tutorial/eas/team-development.mdx +++ b/docs/pages/tutorial/eas/team-development.mdx @@ -11,7 +11,7 @@ import { Collapsible } from '~/ui/components/Collapsible'; import Video from '~/components/plugins/Video'; import { ProgressTracker } from '~/ui/components/ProgressTracker'; -Updates generally fix small bugs and push small changes in between app store releases. They allow updating the non-native parts of our app, such as JavaScript code, styling, and images. +Updates generally fix small bugs and push small changes in between app store releases. They allow updating the non-native parts of our example app, such as JavaScript code, styling, and images. In this chapter, we'll use [EAS Update](/eas-update/introduction/) to share changes with our team. This will help [us and our team quickly share previews](/review/overview/) of the change. @@ -49,18 +49,24 @@ If a project doesn't use dynamic app config (uses **app.json** instead of **app. "build": { "development": { /* @hide ... */ /* @end */ + /* @info */ "channel": "development" + /* @end */ }, "ios-simulator": { /* @hide ... */ /* @end */ }, "preview": { /* @hide ... */ /* @end */ + /* @info */ "channel": "preview" + /* @end */ }, "production": { /* @hide ... */ /* @end */ + /* @info */ "channel": "production" + /* @end */ } } /* @hide ... */ /* @end */ @@ -97,7 +103,7 @@ After the new version of the development build is created, make sure to install Let's modify our example app's JavaScript code. If you are not using [Sticker Smash app](/tutorial/eas/introduction/#prerequisites), you can modify any piece of your code to see the changes in the app. -We'll modify the text of the first button in our app that says **Choose a photo** to **Select a photo**. +We'll modify the text of the first button in our example app that says **Choose a photo** to **Select a photo**. ```jsx App.js