🕷️ Crawler Inspector

URL Lookup

Direct Parameter Lookup

Raw Queries and Responses

1. Shard Calculation

Query:

Response:

Calculated Shard: 50 (from laksa182)

2. Crawled Status Check

Query:

curl -X POST \
  'http://laksa050.int.ahrefs:8124/' \
  -H 'Content-Type: text/plain' \
  -H 'X-ClickHouse-Database: crawler3' \
  -H 'Authorization: Basic YXBpOg==' \
  -d 'SELECT getAhrefsURLFromUnparsed(src_unparsed) AS found_url, ifNull(toUnixTimestamp(download_stamp), 0) AS crawl_time, ifNull(toUnixTimestamp(props_url_first_seen), 0) AS first_indexed_time, download_http_code AS http_code, src_unparsed AS src_unparsed, src_root_hash AS src_root_hash, history_drop_reason AS history_drop_reason, meta_title AS meta_title, meta_descriptions AS meta_descriptions, attrs_boilerpipe_text AS attrs_boilerpipe_text, attrs_markdown AS attrs_markdown, attrs_readable_markdown AS attrs_readable_markdown, meta_canonical AS meta_canonical, ml_categories_json AS ml_categories_json, ml_types_json AS ml_types_json, ml_intent_types_json AS ml_intent_types_json, meta_language AS meta_language, attrs_author AS attrs_author, ifNull(toUnixTimestamp(attrs_publish_time), 0) AS attrs_publish_time, ifNull(toUnixTimestamp(attrs_original_publish_time), 0) AS attrs_original_publish_time, ifNull(attrs_is_republished, 0) AS attrs_is_republished, ifNull(attrs_nr_words, 0) AS attrs_nr_words, ifNull(attrs_boilerpipe_nr_words, 0) AS attrs_boilerpipe_nr_words, ifNull(body_ext_links_number, 0) AS body_ext_links_number, ifNull(body_int_links_number, 0) AS body_int_links_number, ifNull(meta_nofollow, 0) AS meta_nofollow, ifNull(meta_noarchive, 0) AS meta_noarchive, ifNull(props_was_rendered, 0) AS props_was_rendered, ifNull(src_redirect, \'\') AS src_redirect, ifNull(download_time_msec, 0) AS download_time_msec, ifNull(download_ttfb_msec, 0) AS download_ttfb_msec, ifNull(download_size, 0) AS download_size FROM crawler3.page_info_local FINAL PREWHERE (src_root_hash, src_unparsed) IN ((getAhrefsRootHashFromUnparsed(getAhrefsUnparsedNoserviceFromURL(\'https://docs.expo.dev/build/setup/\')), getAhrefsUnparsedNoserviceFromURL(\'https://docs.expo.dev/build/setup/\'))) FORMAT JSONEachRow'

Response:

{"found_url":"https:\/\/docs.expo.dev\/build\/setup\/","crawl_time":1776349234,"first_indexed_time":1627971018,"http_code":200,"src_unparsed":"dev,expo!docs,\/build\/setup\/ s443","src_root_hash":"9098366656517426850","history_drop_reason":null,"meta_title":"Create your first build - Expo Documentation","meta_descriptions":["Learn how to create a build for your app with EAS Build."],"attrs_boilerpipe_text":"Learn how to create a build for your app with EAS Build.\nEdit page\nFor the complete documentation index, see\nllms.txt\n. Use this Use this file to discover all available pages.\nEAS Build allows you to build a ready-to-submit binary of your app for the Google Play Store or Apple App Store. In this guide, let's learn how to do that.\nAlternatively, if you prefer to install the app directly to your Android device\/emulator or install it in the iOS Simulator, we will point you toward resources that explain how to do that.\nFor a small app, builds for Android and iOS platforms trigger within a few minutes. If you encounter any issues along the way, you can reach out on\nDiscord and Forums\n.\nPrerequisites\nEAS Build is a rapidly evolving service. Before you set out to create a build for your project we recommend consulting the\nlimitations\npage and the other prerequisites below.\nA React Native Android and\/or iOS project that you want to build\nAn Expo user account\n1\nInstall the latest EAS CLI\nEAS CLI is the command-line app that you will use to interact with EAS services from your terminal. To install it, run the command:\n- \nnpm\ninstall\n-g\neas-cli\nYou can also use the above command to check if a new version of EAS CLI is available. We encourage you to always stay up to date with the latest version.\nWe recommend using\nnpm\ninstead of\nyarn\nfor global package installations. You may alternatively use\nnpx eas-cli@latest\n. Remember to use that instead of\neas\nwhenever it's called for in the documentation.\n2\nLog in to your Expo account\nIf you are already signed in to an Expo account using Expo CLI, you can skip the steps described in this section. If you are not, run the following command to log in:\n- \neas\nlogin\nYou can check whether you are logged in by running\neas whoami\n.\n3\nConfigure the project\nTo configure an Android or an iOS project for EAS Build, run the following command:\n- \neas\nbuild:configure\nTo learn more about what happens behind the scenes, see\nbuild configuration process reference\n.\nFor development, we recommend creating a\ndevelopment build\n, which is a debug build of your app and contains the\nexpo-dev-client\nlibrary. It helps you iterate as quickly as possible and provides a more flexible, reliable, and complete development environment. To install the library, run the following command:\n- \nnpx\nexpo install expo-dev-client\nAdditional configuration may be required for some scenarios:\nDoes your app code depend on environment variables?\nAdd them to your build configuration\n.\nIs your project inside of a monorepo?\nFollow these instructions\n.\nDo you use private npm packages?\nAdd your npm token\n.\nDoes your app depend on specific versions of tools like Node, Yarn, npm, CocoaPods, or Xcode?\nSpecify these versions in your build configuration\n.\n4\nRun a build\nBuild for Android Emulator\/device or iOS Simulator\nThe easiest way to try out EAS Build is to create a build that you can run on your Android device\/emulator or iOS Simulator. It's quicker than uploading it to a store, and you don't need store developer membership accounts. If you'd like to try this, read about\ncreating an installable APK for Android\nand\ncreating a simulator build for iOS\n.\nBuild for app stores\nBefore the build process can start for app stores, you will need to have a store developer account and generate or provide app signing credentials.\nWhether you have experience with generating app signing credentials or not, EAS CLI does the heavy lifting. You can opt-in for EAS CLI to handle the app signing credentials process. Check out the steps for\nAndroid app signing credentials\nor\niOS app signing credentials\nprocess below for more information.\nGoogle Play Developer membership is required to distribute to the Google Play Store.\nApple Developer Program membership is required to build for the Apple App Store.\nAfter you have confirmed that you have a Google Play Store or Apple App Store account and decided whether or not EAS CLI should handle app signing credentials, you can proceed with the following set of commands to build for the platform's store:\n- \neas\nbuild\n--platform\nandroid\nYou can attach a message to the build by passing\n--message\nto the build command, for example,\neas build --platform ios --message \"Some message\"\n. The message will appear on the website. It comes in handy when you want to leave a note with the purpose of the build for your team.\nAlternatively, you can use\n--platform all\noption to build for Android and iOS at the same time:\n- \neas\nbuild\n--platform\nall\nIf you have released your app to stores previously and have existing\napp signing credentials\nthat you want to use,\nfollow these instructions to configure them\n.\nAndroid app signing credentials\nIf you have not yet generated a keystore for your app, you can let EAS CLI take care of that for you by selecting\nGenerate new keystore\n, and then you are done. The keystore is stored securely on EAS servers.\nIf you have previously built your app with\nexpo build:android\n, you can use the same credentials here.\nIf you want to manually generate your keystore, see the\nmanual Android credentials guide\nfor more information.\niOS app signing credentials\nIf you have not generated a provisioning profile and\/or distribution certificate yet, you can let EAS CLI take care of that for you by signing into your Apple Developer Program account and following the prompts.\nIf you have already built your app with\nexpo build:ios\n, you can use the same credentials here.\nIf you want to rather manually generate your credentials, refer to the\nmanual iOS credentials guide\nfor more information.\n5\nWait for the build to complete\nBy default, the\neas build\ncommand will wait for your build to complete, but you can interrupt it if you prefer not to wait. Monitor the progress and read the logs by following the link to the build details page that EAS CLI prompts once the build process gets started. You can also find this page by visiting\nyour build dashboard\nor running the following command:\n- \neas\nbuild:list\nIf you are a member of an organization and your build is on its behalf, you will find the build details on\nthe build dashboard for that account\n.\nDid your build fail?\nDouble check that you followed any applicable instructions in the\nconfiguration step\nand refer to the\ntroubleshooting guide\nif needed.\n6\nDeploy the build\nIf you have made it to this step, congratulations! Depending on which path you chose, you now either have a build that is ready to upload to an app store, or you have a build that you can install directly on an Android device\/iOS Simulator.\nDistribute your app to an app store\nYou will only be able to submit to an app store if you built specifically for that purpose. If you created a build for a store,\nlearn how to submit your app to app stores with EAS Submit\n.\nInstall and run the app\nYou will only be able to install the app directly to your Android device\/iOS Simulator if you explicitly built it for that purpose. If you built for app store distribution, you will need to upload to an app store and then install it from there (for example, from Apple's TestFlight app).\nTo learn how to install the app directly to your Android device\/iOS Simulator, navigate to your build details page from\nyour build dashboard\nand click the \"Install\" button.\nNext steps\nWe walked you through the steps to create your first build with EAS Build without going into too much depth on any particular part of the process.\nWhen you are ready to learn more, we recommend proceeding through the following topics to learn more:\nYou may also want to dig through the reference section to learn more about the topics that interest you most, such as:","attrs_markdown":"[Docs](https:\/\/docs.expo.dev\/)\n\n[Blog](https:\/\/expo.dev\/blog)[Changelog](https:\/\/expo.dev\/changelog)\n\n[Star Us on GitHub](https:\/\/github.com\/expo\/expo)\n\nAuto\n\nHide navigation\n\nSearch or Ask AI\n\n`Ctrl` `K`\n\n[Home](https:\/\/docs.expo.dev\/)\n\n[Guides](https:\/\/docs.expo.dev\/guides\/overview)\n\n[EAS](https:\/\/docs.expo.dev\/eas)\n\n[Reference](https:\/\/docs.expo.dev\/versions\/latest)\n\n[Learn](https:\/\/docs.expo.dev\/tutorial\/overview)\n\n[Introduction](https:\/\/docs.expo.dev\/eas)\n\n[Configuration with eas.json](https:\/\/docs.expo.dev\/eas\/json)\n\n[EAS CLI](https:\/\/docs.expo.dev\/eas\/cli)\n\nEnvironment variables\n\nAI\n\n[MCP Server](https:\/\/docs.expo.dev\/eas\/ai\/mcp)\n\nEAS Workflows\n\n[Introduction](https:\/\/docs.expo.dev\/eas\/workflows\/introduction)\n\n[Get started](https:\/\/docs.expo.dev\/eas\/workflows\/get-started)\n\n[Pre-packaged jobs](https:\/\/docs.expo.dev\/eas\/workflows\/pre-packaged-jobs)\n\n[Syntax](https:\/\/docs.expo.dev\/eas\/workflows\/syntax)\n\n[Automating EAS CLI commands](https:\/\/docs.expo.dev\/eas\/workflows\/automating-eas-cli)\n\n[Limitations](https:\/\/docs.expo.dev\/eas\/workflows\/limitations)\n\nExamples\n\nEAS Build\n\n[Introduction](https:\/\/docs.expo.dev\/build\/introduction)\n\n[Create your first build](https:\/\/docs.expo.dev\/build\/setup)\n\n[Configure with eas.json](https:\/\/docs.expo.dev\/build\/eas-json)\n\n[Internal distribution](https:\/\/docs.expo.dev\/build\/internal-distribution)\n\n[Automate submissions](https:\/\/docs.expo.dev\/build\/automate-submissions)\n\n[Using EAS Update](https:\/\/docs.expo.dev\/build\/updates)\n\n[Trigger builds from CI](https:\/\/docs.expo.dev\/build\/building-on-ci)\n\n[Trigger builds from GitHub App](https:\/\/docs.expo.dev\/build\/building-from-github)\n\n[Expo Orbit](https:\/\/docs.expo.dev\/build\/orbit)\n\nApp signing\n\nCustom builds\n\nReference\n\nEAS Submit\n\n[Introduction](https:\/\/docs.expo.dev\/submit\/introduction)\n\n[Submit to the Google Play Store](https:\/\/docs.expo.dev\/submit\/android)\n\n[Submit to the Apple App Store](https:\/\/docs.expo.dev\/submit\/ios)\n\n[Configure with eas.json](https:\/\/docs.expo.dev\/submit\/eas-json)\n\nEAS Hosting\n\n[Introduction](https:\/\/docs.expo.dev\/eas\/hosting\/introduction)\n\n[Get started with EAS Hosting](https:\/\/docs.expo.dev\/eas\/hosting\/get-started)\n\n[Deployments and aliases](https:\/\/docs.expo.dev\/eas\/hosting\/deployments-and-aliases)\n\n[Custom domain](https:\/\/docs.expo.dev\/eas\/hosting\/custom-domain)\n\n[Monitor API routes](https:\/\/docs.expo.dev\/eas\/hosting\/api-routes)\n\n[Web deployments with EAS Workflows](https:\/\/docs.expo.dev\/eas\/hosting\/workflows)\n\nReference\n\nEAS Update\n\n[Introduction](https:\/\/docs.expo.dev\/eas-update\/introduction)\n\n[Get started](https:\/\/docs.expo.dev\/eas-update\/getting-started)\n\nPreview\n\nDeployment\n\nConcepts\n\nTroubleshooting\n\nReference\n\nEAS Metadata\n\n[Introduction](https:\/\/docs.expo.dev\/eas\/metadata)\n\n[Get started](https:\/\/docs.expo.dev\/eas\/metadata\/getting-started)\n\nReference\n\nEAS Insights\n\n[Introduction](https:\/\/docs.expo.dev\/eas-insights\/introduction)\n\nDistribution\n\n[Overview](https:\/\/docs.expo.dev\/distribution\/introduction)\n\n[App stores best practices](https:\/\/docs.expo.dev\/distribution\/app-stores)\n\n[App transfers](https:\/\/docs.expo.dev\/distribution\/app-transfers)\n\n[Understanding app size](https:\/\/docs.expo.dev\/distribution\/app-size)\n\nReference\n\n[Webhooks](https:\/\/docs.expo.dev\/eas\/webhooks)\n\nExpo accounts\n\nBilling\n\n[Archive](https:\/\/docs.expo.dev\/archive)\n\n[Expo Snack](https:\/\/snack.expo.dev\/)\n\n[Discord and Forums](https:\/\/chat.expo.dev\/)\n\n[Newsletter](https:\/\/expo.dev\/mailing-list\/signup)\n\n# Create your first build\n[Edit page](https:\/\/github.com\/expo\/expo\/edit\/main\/docs\/pages\/build\/setup.mdx)\n\nCopy page\n\nLearn how to create a build for your app with EAS Build.\n\n[Edit page](https:\/\/github.com\/expo\/expo\/edit\/main\/docs\/pages\/build\/setup.mdx)\n\nCopy page\n***\n> For the complete documentation index, see [llms.txt](https:\/\/docs.expo.dev\/llms.txt). Use this Use this file to discover all available pages.\n\nEAS Build allows you to build a ready-to-submit binary of your app for the Google Play Store or Apple App Store. In this guide, let's learn how to do that.\n\nAlternatively, if you prefer to install the app directly to your Android device\/emulator or install it in the iOS Simulator, we will point you toward resources that explain how to do that.\n\nFor a small app, builds for Android and iOS platforms trigger within a few minutes. If you encounter any issues along the way, you can reach out on [Discord and Forums](https:\/\/chat.expo.dev\/).\n\n## Prerequisites\nEAS Build is a rapidly evolving service. Before you set out to create a build for your project we recommend consulting the [limitations](https:\/\/docs.expo.dev\/build-reference\/limitations) page and the other prerequisites below.\n\nA React Native Android and\/or iOS project that you want to build\n\nDon't have a project yet? No problem. It's quick and easy to create a \"Hello world\" app that you can use with this guide.\n\nRun the following command to create a new project:\n\nTerminal\n\nCopy\n\n`- ``npx create-expo-app@latest my-app --template default@sdk-55`\n\nEAS Build also works well with projects created by `npx create-react-native-app`, `npx react-native`, `ignite-cli`, and other project bootstrapping tools.\n\nAn Expo user account\n\nEAS Build is available to anyone with an Expo account, regardless of whether you pay for EAS or use our Free plan. You can sign up at <https:\/\/expo.dev\/signup>.\n\nPaid subscribers get quality improvements such as additional build concurrencies, priority access to minimize the time your builds spend queueing, and increased limits on build timeouts. Learn more about different plans and benefits at [EAS pricing](https:\/\/expo.dev\/pricing).\n\n1\n\n## Install the latest EAS CLI\nEAS CLI is the command-line app that you will use to interact with EAS services from your terminal. To install it, run the command:\n\nTerminal\n\nCopy\n\n`- ``npm install -g eas-cli`\n\nYou can also use the above command to check if a new version of EAS CLI is available. We encourage you to always stay up to date with the latest version.\n\n> We recommend using `npm` instead of `yarn` for global package installations. You may alternatively use `npx eas-cli@latest`. Remember to use that instead of `eas` whenever it's called for in the documentation.\n\n2\n\n## Log in to your Expo account\nIf you are already signed in to an Expo account using Expo CLI, you can skip the steps described in this section. If you are not, run the following command to log in:\n\nTerminal\n\nCopy\n\n`- ``eas login`\n\nYou can check whether you are logged in by running `eas whoami`.\n\n3\n\n## Configure the project\nTo configure an Android or an iOS project for EAS Build, run the following command:\n\nTerminal\n\nCopy\n\n`- ``eas build:configure`\n\nTo learn more about what happens behind the scenes, see [build configuration process reference](https:\/\/docs.expo.dev\/build-reference\/build-configuration).\n\nFor development, we recommend creating a [development build](https:\/\/docs.expo.dev\/develop\/development-builds\/introduction), which is a debug build of your app and contains the [`expo-dev-client`](https:\/\/docs.expo.dev\/versions\/latest\/sdk\/dev-client) library. It helps you iterate as quickly as possible and provides a more flexible, reliable, and complete development environment. To install the library, run the following command:\n\nTerminal\n\nCopy\n\n`- ``npx expo install expo-dev-client`\n\nAdditional configuration may be required for some scenarios:\n\n- Does your app code depend on environment variables? [Add them to your build configuration](https:\/\/docs.expo.dev\/eas\/environment-variables).\n- Is your project inside of a monorepo? [Follow these instructions](https:\/\/docs.expo.dev\/build-reference\/build-with-monorepos).\n- Do you use private npm packages? [Add your npm token](https:\/\/docs.expo.dev\/build-reference\/private-npm-packages).\n- Does your app depend on specific versions of tools like Node, Yarn, npm, CocoaPods, or Xcode? [Specify these versions in your build configuration](https:\/\/docs.expo.dev\/build\/eas-json).\n\n4\n\n## Run a build\n### Build for Android Emulator\/device or iOS Simulator\nThe easiest way to try out EAS Build is to create a build that you can run on your Android device\/emulator or iOS Simulator. It's quicker than uploading it to a store, and you don't need store developer membership accounts. If you'd like to try this, read about [creating an installable APK for Android](https:\/\/docs.expo.dev\/tutorial\/eas\/android-development-build) and [creating a simulator build for iOS](https:\/\/docs.expo.dev\/tutorial\/eas\/ios-development-build-for-simulators).\n\n### Build for app stores\nBefore the build process can start for app stores, you will need to have a store developer account and generate or provide app signing credentials.\n\nWhether you have experience with generating app signing credentials or not, EAS CLI does the heavy lifting. You can opt-in for EAS CLI to handle the app signing credentials process. Check out the steps for [Android app signing credentials](https:\/\/docs.expo.dev\/build\/setup#android-app-signing-credentials) or [iOS app signing credentials](https:\/\/docs.expo.dev\/build\/setup#ios-app-signing-credentials) process below for more information.\n\nGoogle Play Developer membership is required to distribute to the Google Play Store.\n\nYou can build and sign your app using EAS Build, but you can't upload it to the Google Play Store unless you have a membership, a one-time \\$25 USD fee.\n\nApple Developer Program membership is required to build for the Apple App Store.\n\nIf you are going to use EAS Build to create release builds for the Apple App Store, you need access to an account with a \\$99 USD [Apple Developer Program](https:\/\/developer.apple.com\/programs) membership.\n\nAfter you have confirmed that you have a Google Play Store or Apple App Store account and decided whether or not EAS CLI should handle app signing credentials, you can proceed with the following set of commands to build for the platform's store:\n\nAndroid\n\niOS\n\nTerminal\n\nCopy\n\n`- ``eas build --platform android`\n\nTerminal\n\nCopy\n\n`- ``eas build --platform ios`\n\n> You can attach a message to the build by passing `--message` to the build command, for example, `eas build --platform ios --message \"Some message\"`. The message will appear on the website. It comes in handy when you want to leave a note with the purpose of the build for your team.\n\nAlternatively, you can use `--platform all` option to build for Android and iOS at the same time:\n\nTerminal\n\nCopy\n\n`- ``eas build --platform all`\n\n> If you have released your app to stores previously and have existing [app signing credentials](https:\/\/docs.expo.dev\/app-signing\/app-credentials) that you want to use, [follow these instructions to configure them](https:\/\/docs.expo.dev\/app-signing\/existing-credentials).\n#### Android app signing credentials\n- If you have not yet generated a keystore for your app, you can let EAS CLI take care of that for you by selecting `Generate new keystore`, and then you are done. The keystore is stored securely on EAS servers.\n- If you have previously built your app with `expo build:android`, you can use the same credentials here.\n- If you want to manually generate your keystore, see the [manual Android credentials guide](https:\/\/docs.expo.dev\/app-signing\/local-credentials#android-credentials) for more information.\n#### iOS app signing credentials\n- If you have not generated a provisioning profile and\/or distribution certificate yet, you can let EAS CLI take care of that for you by signing into your Apple Developer Program account and following the prompts.\n- If you have already built your app with `expo build:ios`, you can use the same credentials here.\n- If you want to rather manually generate your credentials, refer to the [manual iOS credentials guide](https:\/\/docs.expo.dev\/app-signing\/local-credentials#ios-credentials) for more information.\n\n5\n\n## Wait for the build to complete\nBy default, the `eas build` command will wait for your build to complete, but you can interrupt it if you prefer not to wait. Monitor the progress and read the logs by following the link to the build details page that EAS CLI prompts once the build process gets started. You can also find this page by visiting [your build dashboard](https:\/\/expo.dev\/builds) or running the following command:\n\nTerminal\n\nCopy\n\n`- ``eas build:list`\n\nIf you are a member of an organization and your build is on its behalf, you will find the build details on [the build dashboard for that account](https:\/\/expo.dev\/accounts\/%5Baccount%5D\/builds).\n\n> Did your build fail? Double check that you followed any applicable instructions in the [configuration step](https:\/\/docs.expo.dev\/build\/setup#3-configure-the-project) and refer to the [troubleshooting guide](https:\/\/docs.expo.dev\/build-reference\/troubleshooting) if needed.\n\n6\n\n## Deploy the build\nIf you have made it to this step, congratulations! Depending on which path you chose, you now either have a build that is ready to upload to an app store, or you have a build that you can install directly on an Android device\/iOS Simulator.\n\n### Distribute your app to an app store\nYou will only be able to submit to an app store if you built specifically for that purpose. If you created a build for a store, [learn how to submit your app to app stores with EAS Submit](https:\/\/docs.expo.dev\/submit\/introduction).\n\n### Install and run the app\nYou will only be able to install the app directly to your Android device\/iOS Simulator if you explicitly built it for that purpose. If you built for app store distribution, you will need to upload to an app store and then install it from there (for example, from Apple's TestFlight app).\n\nTo learn how to install the app directly to your Android device\/iOS Simulator, navigate to your build details page from [your build dashboard](https:\/\/expo.dev\/accounts\/%5Baccount%5D\/builds) and click the \"Install\" button.\n## Next steps\nWe walked you through the steps to create your first build with EAS Build without going into too much depth on any particular part of the process.\n\nWhen you are ready to learn more, we recommend proceeding through the following topics to learn more:\n\n- [Configuration with eas.json](https:\/\/docs.expo.dev\/build\/eas-json)\n- [Internal distribution](https:\/\/docs.expo.dev\/build\/internal-distribution)\n- [Updates](https:\/\/docs.expo.dev\/build\/updates)\n- [Automating submissions](https:\/\/docs.expo.dev\/build\/automate-submissions)\n- [Triggering builds from CI](https:\/\/docs.expo.dev\/build\/building-on-ci)\n\nYou may also want to dig through the reference section to learn more about the topics that interest you most, such as:\n\n- [Build webhooks](https:\/\/docs.expo.dev\/eas\/webhooks)\n- [Build server infrastructure](https:\/\/docs.expo.dev\/build-reference\/infrastructure)\n- How the [Android](https:\/\/docs.expo.dev\/build-reference\/android-builds) and [iOS](https:\/\/docs.expo.dev\/build-reference\/ios-builds) build processes work\n\n[Previous (EAS Build) Introduction](https:\/\/docs.expo.dev\/build\/introduction)\n\n[Next (EAS Build) Configure with eas.json](https:\/\/docs.expo.dev\/build\/eas-json)\n\nWas this doc helpful?\n\n- [Share your feedback]()\n- [Ask a question on the forums](https:\/\/chat.expo.dev\/)\n- [Edit this page](https:\/\/github.com\/expo\/expo\/edit\/main\/docs\/pages\/build\/setup.mdx)\n- View [llms.txt](https:\/\/docs.expo.dev\/llms.txt) and [llms-full.txt](https:\/\/docs.expo.dev\/llms-eas.txt)\n- Last updated on\n  February 28, 2026\n\nSign up for the Expo Newsletter\n\nUnsubscribe at any time. Read our [privacy policy](https:\/\/expo.dev\/privacy).\n\nYour Privacy Choices\n\nOn this page\n\n[Prerequisites](https:\/\/docs.expo.dev\/build\/setup\/#prerequisites)\n\n[Install the latest EAS CLI](https:\/\/docs.expo.dev\/build\/setup\/#install-the-latest-eas-cli)\n\n[Log in to your Expo account](https:\/\/docs.expo.dev\/build\/setup\/#log-in-to-your-expo-account)\n\n[Configure the project](https:\/\/docs.expo.dev\/build\/setup\/#configure-the-project)\n\n[Run a build](https:\/\/docs.expo.dev\/build\/setup\/#run-a-build)\n\n[Build for Android Emulator\/device or iOS Simulator](https:\/\/docs.expo.dev\/build\/setup\/#build-for-android-emulatordevice-or-ios-simulator)\n\n[Build for app stores](https:\/\/docs.expo.dev\/build\/setup\/#build-for-app-stores)\n\n[Wait for the build to complete](https:\/\/docs.expo.dev\/build\/setup\/#wait-for-the-build-to-complete)\n\n[Deploy the build](https:\/\/docs.expo.dev\/build\/setup\/#deploy-the-build)\n\n[Distribute your app to an app store](https:\/\/docs.expo.dev\/build\/setup\/#distribute-your-app-to-an-app-store)\n\n[Install and run the app](https:\/\/docs.expo.dev\/build\/setup\/#install-and-run-the-app)\n\n[Next steps](https:\/\/docs.expo.dev\/build\/setup\/#next-steps)\n\nWe value your privacy\n\nWe use cookies to collect data and improve our services. [Learn more](https:\/\/expo.dev\/privacy\/cookies)\n\nDecline\n\nAccept\n\nCustomize","attrs_readable_markdown":"Learn how to create a build for your app with EAS Build.\n\n[Edit page](https:\/\/github.com\/expo\/expo\/edit\/main\/docs\/pages\/build\/setup.mdx)\n***\n> For the complete documentation index, see [llms.txt](https:\/\/docs.expo.dev\/llms.txt). Use this Use this file to discover all available pages.\n\nEAS Build allows you to build a ready-to-submit binary of your app for the Google Play Store or Apple App Store. In this guide, let's learn how to do that.\n\nAlternatively, if you prefer to install the app directly to your Android device\/emulator or install it in the iOS Simulator, we will point you toward resources that explain how to do that.\n\nFor a small app, builds for Android and iOS platforms trigger within a few minutes. If you encounter any issues along the way, you can reach out on [Discord and Forums](https:\/\/chat.expo.dev\/).\n\n## Prerequisites\nEAS Build is a rapidly evolving service. Before you set out to create a build for your project we recommend consulting the [limitations](https:\/\/docs.expo.dev\/build-reference\/limitations) page and the other prerequisites below.\n\nA React Native Android and\/or iOS project that you want to build\n\nAn Expo user account\n\n1\n\n## Install the latest EAS CLI\nEAS CLI is the command-line app that you will use to interact with EAS services from your terminal. To install it, run the command:\n\n`- ``npm install -g eas-cli`\n\nYou can also use the above command to check if a new version of EAS CLI is available. We encourage you to always stay up to date with the latest version.\n\n> We recommend using `npm` instead of `yarn` for global package installations. You may alternatively use `npx eas-cli@latest`. Remember to use that instead of `eas` whenever it's called for in the documentation.\n\n2\n\n## Log in to your Expo account\nIf you are already signed in to an Expo account using Expo CLI, you can skip the steps described in this section. If you are not, run the following command to log in:\n\n`- ``eas login`\n\nYou can check whether you are logged in by running `eas whoami`.\n\n3\n\n## Configure the project\nTo configure an Android or an iOS project for EAS Build, run the following command:\n\n`- ``eas build:configure`\n\nTo learn more about what happens behind the scenes, see [build configuration process reference](https:\/\/docs.expo.dev\/build-reference\/build-configuration).\n\nFor development, we recommend creating a [development build](https:\/\/docs.expo.dev\/develop\/development-builds\/introduction), which is a debug build of your app and contains the [`expo-dev-client`](https:\/\/docs.expo.dev\/versions\/latest\/sdk\/dev-client) library. It helps you iterate as quickly as possible and provides a more flexible, reliable, and complete development environment. To install the library, run the following command:\n\n`- ``npx expo install expo-dev-client`\n\nAdditional configuration may be required for some scenarios:\n\n- Does your app code depend on environment variables? [Add them to your build configuration](https:\/\/docs.expo.dev\/eas\/environment-variables).\n- Is your project inside of a monorepo? [Follow these instructions](https:\/\/docs.expo.dev\/build-reference\/build-with-monorepos).\n- Do you use private npm packages? [Add your npm token](https:\/\/docs.expo.dev\/build-reference\/private-npm-packages).\n- Does your app depend on specific versions of tools like Node, Yarn, npm, CocoaPods, or Xcode? [Specify these versions in your build configuration](https:\/\/docs.expo.dev\/build\/eas-json).\n\n4\n\n## Run a build\n### Build for Android Emulator\/device or iOS Simulator\nThe easiest way to try out EAS Build is to create a build that you can run on your Android device\/emulator or iOS Simulator. It's quicker than uploading it to a store, and you don't need store developer membership accounts. If you'd like to try this, read about [creating an installable APK for Android](https:\/\/docs.expo.dev\/tutorial\/eas\/android-development-build) and [creating a simulator build for iOS](https:\/\/docs.expo.dev\/tutorial\/eas\/ios-development-build-for-simulators).\n\n### Build for app stores\nBefore the build process can start for app stores, you will need to have a store developer account and generate or provide app signing credentials.\n\nWhether you have experience with generating app signing credentials or not, EAS CLI does the heavy lifting. You can opt-in for EAS CLI to handle the app signing credentials process. Check out the steps for [Android app signing credentials](https:\/\/docs.expo.dev\/build\/setup#android-app-signing-credentials) or [iOS app signing credentials](https:\/\/docs.expo.dev\/build\/setup#ios-app-signing-credentials) process below for more information.\n\nGoogle Play Developer membership is required to distribute to the Google Play Store.\n\nApple Developer Program membership is required to build for the Apple App Store.\n\nAfter you have confirmed that you have a Google Play Store or Apple App Store account and decided whether or not EAS CLI should handle app signing credentials, you can proceed with the following set of commands to build for the platform's store:\n\n`- ``eas build --platform android`\n\n> You can attach a message to the build by passing `--message` to the build command, for example, `eas build --platform ios --message \"Some message\"`. The message will appear on the website. It comes in handy when you want to leave a note with the purpose of the build for your team.\n\nAlternatively, you can use `--platform all` option to build for Android and iOS at the same time:\n\n`- ``eas build --platform all`\n\n> If you have released your app to stores previously and have existing [app signing credentials](https:\/\/docs.expo.dev\/app-signing\/app-credentials) that you want to use, [follow these instructions to configure them](https:\/\/docs.expo.dev\/app-signing\/existing-credentials).\n#### Android app signing credentials\n- If you have not yet generated a keystore for your app, you can let EAS CLI take care of that for you by selecting `Generate new keystore`, and then you are done. The keystore is stored securely on EAS servers.\n- If you have previously built your app with `expo build:android`, you can use the same credentials here.\n- If you want to manually generate your keystore, see the [manual Android credentials guide](https:\/\/docs.expo.dev\/app-signing\/local-credentials#android-credentials) for more information.\n#### iOS app signing credentials\n- If you have not generated a provisioning profile and\/or distribution certificate yet, you can let EAS CLI take care of that for you by signing into your Apple Developer Program account and following the prompts.\n- If you have already built your app with `expo build:ios`, you can use the same credentials here.\n- If you want to rather manually generate your credentials, refer to the [manual iOS credentials guide](https:\/\/docs.expo.dev\/app-signing\/local-credentials#ios-credentials) for more information.\n\n5\n\n## Wait for the build to complete\nBy default, the `eas build` command will wait for your build to complete, but you can interrupt it if you prefer not to wait. Monitor the progress and read the logs by following the link to the build details page that EAS CLI prompts once the build process gets started. You can also find this page by visiting [your build dashboard](https:\/\/expo.dev\/builds) or running the following command:\n\n`- ``eas build:list`\n\nIf you are a member of an organization and your build is on its behalf, you will find the build details on [the build dashboard for that account](https:\/\/expo.dev\/accounts\/%5Baccount%5D\/builds).\n\n> Did your build fail? Double check that you followed any applicable instructions in the [configuration step](https:\/\/docs.expo.dev\/build\/setup#3-configure-the-project) and refer to the [troubleshooting guide](https:\/\/docs.expo.dev\/build-reference\/troubleshooting) if needed.\n\n6\n\n## Deploy the build\nIf you have made it to this step, congratulations! Depending on which path you chose, you now either have a build that is ready to upload to an app store, or you have a build that you can install directly on an Android device\/iOS Simulator.\n\n### Distribute your app to an app store\nYou will only be able to submit to an app store if you built specifically for that purpose. If you created a build for a store, [learn how to submit your app to app stores with EAS Submit](https:\/\/docs.expo.dev\/submit\/introduction).\n\n### Install and run the app\nYou will only be able to install the app directly to your Android device\/iOS Simulator if you explicitly built it for that purpose. If you built for app store distribution, you will need to upload to an app store and then install it from there (for example, from Apple's TestFlight app).\n\nTo learn how to install the app directly to your Android device\/iOS Simulator, navigate to your build details page from [your build dashboard](https:\/\/expo.dev\/accounts\/%5Baccount%5D\/builds) and click the \"Install\" button.\n## Next steps\nWe walked you through the steps to create your first build with EAS Build without going into too much depth on any particular part of the process.\n\nWhen you are ready to learn more, we recommend proceeding through the following topics to learn more:\n\nYou may also want to dig through the reference section to learn more about the topics that interest you most, such as:","meta_canonical":null,"ml_categories_json":"{\"\/Computers_and_Electronics\":858,\"\/Computers_and_Electronics\/Software\":799,\"\/Computers_and_Electronics\/Software\/Software_Utilities\":692,\"\/Internet_and_Telecom\":363,\"\/Internet_and_Telecom\/Web_Services\":312,\"\/Internet_and_Telecom\/Web_Services\/Web_Design_and_Development\":290}","ml_types_json":"{\"\/Document\":770,\"\/Document\/Manual\":761}","ml_intent_types_json":"{\"Informational\":966}","meta_language":"en","attrs_author":null,"attrs_publish_time":0,"attrs_original_publish_time":1627971018,"attrs_is_republished":0,"attrs_nr_words":"1889","attrs_boilerpipe_nr_words":"1343","body_ext_links_number":7,"body_int_links_number":135,"meta_nofollow":0,"meta_noarchive":0,"props_was_rendered":1,"src_redirect":"","download_time_msec":98,"download_ttfb_msec":95,"download_size":29887}

3. Robots.txt Check

Query:

Response:

4. Spam/Ban Check

Query:

Response:

5. Seen Status Check

ℹ️ Skipped - page is already crawled

📄

INDEXABLE

✅

CRAWLED

8 days ago

🤖

ROBOTS ALLOWED

Page Info Filters

Filter	Status	Condition	Details
HTTP status	PASS	`download_http_code = 200`	HTTP 200
Age cutoff	PASS	`download_stamp > now() - 6 MONTH`	0.3 months ago
History drop	PASS	`isNull(history_drop_reason)`	No drop reason
Spam/ban	PASS	`fh_dont_index != 1 AND ml_spam_score = 0`	ml_spam_score=0
Canonical	PASS	`meta_canonical IS NULL OR = '' OR = src_unparsed`	Not set

Page Details

Property

Value

URL

https://docs.expo.dev/build/setup/

Last Crawled

2026-04-16 14:20:34 (8 days ago)

First Indexed

2021-08-03 06:10:18 (4 years ago)

HTTP Status Code

200

Content

Meta Title

Create your first build - Expo Documentation

Meta Description

Learn how to create a build for your app with EAS Build.

Meta Canonical

null

Boilerpipe Text

Learn how to create a build for your app with EAS Build. Edit page For the complete documentation index, see llms.txt . Use this Use this file to discover all available pages. EAS Build allows you to build a ready-to-submit binary of your app for the Google Play Store or Apple App Store. In this guide, let's learn how to do that. Alternatively, if you prefer to install the app directly to your Android device/emulator or install it in the iOS Simulator, we will point you toward resources that explain how to do that. For a small app, builds for Android and iOS platforms trigger within a few minutes. If you encounter any issues along the way, you can reach out on Discord and Forums . Prerequisites EAS Build is a rapidly evolving service. Before you set out to create a build for your project we recommend consulting the limitations page and the other prerequisites below. A React Native Android and/or iOS project that you want to build An Expo user account 1 Install the latest EAS CLI EAS CLI is the command-line app that you will use to interact with EAS services from your terminal. To install it, run the command: - npm install -g eas-cli You can also use the above command to check if a new version of EAS CLI is available. We encourage you to always stay up to date with the latest version. We recommend using npm instead of yarn for global package installations. You may alternatively use npx eas-cli@latest . Remember to use that instead of eas whenever it's called for in the documentation. 2 Log in to your Expo account If you are already signed in to an Expo account using Expo CLI, you can skip the steps described in this section. If you are not, run the following command to log in: - eas login You can check whether you are logged in by running eas whoami . 3 Configure the project To configure an Android or an iOS project for EAS Build, run the following command: - eas build:configure To learn more about what happens behind the scenes, see build configuration process reference . For development, we recommend creating a development build , which is a debug build of your app and contains the expo-dev-client library. It helps you iterate as quickly as possible and provides a more flexible, reliable, and complete development environment. To install the library, run the following command: - npx expo install expo-dev-client Additional configuration may be required for some scenarios: Does your app code depend on environment variables? Add them to your build configuration . Is your project inside of a monorepo? Follow these instructions . Do you use private npm packages? Add your npm token . Does your app depend on specific versions of tools like Node, Yarn, npm, CocoaPods, or Xcode? Specify these versions in your build configuration . 4 Run a build Build for Android Emulator/device or iOS Simulator The easiest way to try out EAS Build is to create a build that you can run on your Android device/emulator or iOS Simulator. It's quicker than uploading it to a store, and you don't need store developer membership accounts. If you'd like to try this, read about creating an installable APK for Android and creating a simulator build for iOS . Build for app stores Before the build process can start for app stores, you will need to have a store developer account and generate or provide app signing credentials. Whether you have experience with generating app signing credentials or not, EAS CLI does the heavy lifting. You can opt-in for EAS CLI to handle the app signing credentials process. Check out the steps for Android app signing credentials or iOS app signing credentials process below for more information. Google Play Developer membership is required to distribute to the Google Play Store. Apple Developer Program membership is required to build for the Apple App Store. After you have confirmed that you have a Google Play Store or Apple App Store account and decided whether or not EAS CLI should handle app signing credentials, you can proceed with the following set of commands to build for the platform's store: - eas build --platform android You can attach a message to the build by passing --message to the build command, for example, eas build --platform ios --message "Some message" . The message will appear on the website. It comes in handy when you want to leave a note with the purpose of the build for your team. Alternatively, you can use --platform all option to build for Android and iOS at the same time: - eas build --platform all If you have released your app to stores previously and have existing app signing credentials that you want to use, follow these instructions to configure them . Android app signing credentials If you have not yet generated a keystore for your app, you can let EAS CLI take care of that for you by selecting Generate new keystore , and then you are done. The keystore is stored securely on EAS servers. If you have previously built your app with expo build:android , you can use the same credentials here. If you want to manually generate your keystore, see the manual Android credentials guide for more information. iOS app signing credentials If you have not generated a provisioning profile and/or distribution certificate yet, you can let EAS CLI take care of that for you by signing into your Apple Developer Program account and following the prompts. If you have already built your app with expo build:ios , you can use the same credentials here. If you want to rather manually generate your credentials, refer to the manual iOS credentials guide for more information. 5 Wait for the build to complete By default, the eas build command will wait for your build to complete, but you can interrupt it if you prefer not to wait. Monitor the progress and read the logs by following the link to the build details page that EAS CLI prompts once the build process gets started. You can also find this page by visiting your build dashboard or running the following command: - eas build:list If you are a member of an organization and your build is on its behalf, you will find the build details on the build dashboard for that account . Did your build fail? Double check that you followed any applicable instructions in the configuration step and refer to the troubleshooting guide if needed. 6 Deploy the build If you have made it to this step, congratulations! Depending on which path you chose, you now either have a build that is ready to upload to an app store, or you have a build that you can install directly on an Android device/iOS Simulator. Distribute your app to an app store You will only be able to submit to an app store if you built specifically for that purpose. If you created a build for a store, learn how to submit your app to app stores with EAS Submit . Install and run the app You will only be able to install the app directly to your Android device/iOS Simulator if you explicitly built it for that purpose. If you built for app store distribution, you will need to upload to an app store and then install it from there (for example, from Apple's TestFlight app). To learn how to install the app directly to your Android device/iOS Simulator, navigate to your build details page from your build dashboard and click the "Install" button. Next steps We walked you through the steps to create your first build with EAS Build without going into too much depth on any particular part of the process. When you are ready to learn more, we recommend proceeding through the following topics to learn more: You may also want to dig through the reference section to learn more about the topics that interest you most, such as:

Markdown

[Docs](https://docs.expo.dev/) [Blog](https://expo.dev/blog)[Changelog](https://expo.dev/changelog) [Star Us on GitHub](https://github.com/expo/expo) Auto Hide navigation Search or Ask AI `Ctrl` `K` [Home](https://docs.expo.dev/) [Guides](https://docs.expo.dev/guides/overview) [EAS](https://docs.expo.dev/eas) [Reference](https://docs.expo.dev/versions/latest) [Learn](https://docs.expo.dev/tutorial/overview) [Introduction](https://docs.expo.dev/eas) [Configuration with eas.json](https://docs.expo.dev/eas/json) [EAS CLI](https://docs.expo.dev/eas/cli) Environment variables AI [MCP Server](https://docs.expo.dev/eas/ai/mcp) EAS Workflows [Introduction](https://docs.expo.dev/eas/workflows/introduction) [Get started](https://docs.expo.dev/eas/workflows/get-started) [Pre-packaged jobs](https://docs.expo.dev/eas/workflows/pre-packaged-jobs) [Syntax](https://docs.expo.dev/eas/workflows/syntax) [Automating EAS CLI commands](https://docs.expo.dev/eas/workflows/automating-eas-cli) [Limitations](https://docs.expo.dev/eas/workflows/limitations) Examples EAS Build [Introduction](https://docs.expo.dev/build/introduction) [Create your first build](https://docs.expo.dev/build/setup) [Configure with eas.json](https://docs.expo.dev/build/eas-json) [Internal distribution](https://docs.expo.dev/build/internal-distribution) [Automate submissions](https://docs.expo.dev/build/automate-submissions) [Using EAS Update](https://docs.expo.dev/build/updates) [Trigger builds from CI](https://docs.expo.dev/build/building-on-ci) [Trigger builds from GitHub App](https://docs.expo.dev/build/building-from-github) [Expo Orbit](https://docs.expo.dev/build/orbit) App signing Custom builds Reference EAS Submit [Introduction](https://docs.expo.dev/submit/introduction) [Submit to the Google Play Store](https://docs.expo.dev/submit/android) [Submit to the Apple App Store](https://docs.expo.dev/submit/ios) [Configure with eas.json](https://docs.expo.dev/submit/eas-json) EAS Hosting [Introduction](https://docs.expo.dev/eas/hosting/introduction) [Get started with EAS Hosting](https://docs.expo.dev/eas/hosting/get-started) [Deployments and aliases](https://docs.expo.dev/eas/hosting/deployments-and-aliases) [Custom domain](https://docs.expo.dev/eas/hosting/custom-domain) [Monitor API routes](https://docs.expo.dev/eas/hosting/api-routes) [Web deployments with EAS Workflows](https://docs.expo.dev/eas/hosting/workflows) Reference EAS Update [Introduction](https://docs.expo.dev/eas-update/introduction) [Get started](https://docs.expo.dev/eas-update/getting-started) Preview Deployment Concepts Troubleshooting Reference EAS Metadata [Introduction](https://docs.expo.dev/eas/metadata) [Get started](https://docs.expo.dev/eas/metadata/getting-started) Reference EAS Insights [Introduction](https://docs.expo.dev/eas-insights/introduction) Distribution [Overview](https://docs.expo.dev/distribution/introduction) [App stores best practices](https://docs.expo.dev/distribution/app-stores) [App transfers](https://docs.expo.dev/distribution/app-transfers) [Understanding app size](https://docs.expo.dev/distribution/app-size) Reference [Webhooks](https://docs.expo.dev/eas/webhooks) Expo accounts Billing [Archive](https://docs.expo.dev/archive) [Expo Snack](https://snack.expo.dev/) [Discord and Forums](https://chat.expo.dev/) [Newsletter](https://expo.dev/mailing-list/signup) # Create your first build [Edit page](https://github.com/expo/expo/edit/main/docs/pages/build/setup.mdx) Copy page Learn how to create a build for your app with EAS Build. [Edit page](https://github.com/expo/expo/edit/main/docs/pages/build/setup.mdx) Copy page *** > For the complete documentation index, see [llms.txt](https://docs.expo.dev/llms.txt). Use this Use this file to discover all available pages. EAS Build allows you to build a ready-to-submit binary of your app for the Google Play Store or Apple App Store. In this guide, let's learn how to do that. Alternatively, if you prefer to install the app directly to your Android device/emulator or install it in the iOS Simulator, we will point you toward resources that explain how to do that. For a small app, builds for Android and iOS platforms trigger within a few minutes. If you encounter any issues along the way, you can reach out on [Discord and Forums](https://chat.expo.dev/). ## Prerequisites EAS Build is a rapidly evolving service. Before you set out to create a build for your project we recommend consulting the [limitations](https://docs.expo.dev/build-reference/limitations) page and the other prerequisites below. A React Native Android and/or iOS project that you want to build Don't have a project yet? No problem. It's quick and easy to create a "Hello world" app that you can use with this guide. Run the following command to create a new project: Terminal Copy `- ``npx create-expo-app@latest my-app --template default@sdk-55` EAS Build also works well with projects created by `npx create-react-native-app`, `npx react-native`, `ignite-cli`, and other project bootstrapping tools. An Expo user account EAS Build is available to anyone with an Expo account, regardless of whether you pay for EAS or use our Free plan. You can sign up at <https://expo.dev/signup>. Paid subscribers get quality improvements such as additional build concurrencies, priority access to minimize the time your builds spend queueing, and increased limits on build timeouts. Learn more about different plans and benefits at [EAS pricing](https://expo.dev/pricing). 1 ## Install the latest EAS CLI EAS CLI is the command-line app that you will use to interact with EAS services from your terminal. To install it, run the command: Terminal Copy `- ``npm install -g eas-cli` You can also use the above command to check if a new version of EAS CLI is available. We encourage you to always stay up to date with the latest version. > We recommend using `npm` instead of `yarn` for global package installations. You may alternatively use `npx eas-cli@latest`. Remember to use that instead of `eas` whenever it's called for in the documentation. 2 ## Log in to your Expo account If you are already signed in to an Expo account using Expo CLI, you can skip the steps described in this section. If you are not, run the following command to log in: Terminal Copy `- ``eas login` You can check whether you are logged in by running `eas whoami`. 3 ## Configure the project To configure an Android or an iOS project for EAS Build, run the following command: Terminal Copy `- ``eas build:configure` To learn more about what happens behind the scenes, see [build configuration process reference](https://docs.expo.dev/build-reference/build-configuration). For development, we recommend creating a [development build](https://docs.expo.dev/develop/development-builds/introduction), which is a debug build of your app and contains the [`expo-dev-client`](https://docs.expo.dev/versions/latest/sdk/dev-client) library. It helps you iterate as quickly as possible and provides a more flexible, reliable, and complete development environment. To install the library, run the following command: Terminal Copy `- ``npx expo install expo-dev-client` Additional configuration may be required for some scenarios: - Does your app code depend on environment variables? [Add them to your build configuration](https://docs.expo.dev/eas/environment-variables). - Is your project inside of a monorepo? [Follow these instructions](https://docs.expo.dev/build-reference/build-with-monorepos). - Do you use private npm packages? [Add your npm token](https://docs.expo.dev/build-reference/private-npm-packages). - Does your app depend on specific versions of tools like Node, Yarn, npm, CocoaPods, or Xcode? [Specify these versions in your build configuration](https://docs.expo.dev/build/eas-json). 4 ## Run a build ### Build for Android Emulator/device or iOS Simulator The easiest way to try out EAS Build is to create a build that you can run on your Android device/emulator or iOS Simulator. It's quicker than uploading it to a store, and you don't need store developer membership accounts. If you'd like to try this, read about [creating an installable APK for Android](https://docs.expo.dev/tutorial/eas/android-development-build) and [creating a simulator build for iOS](https://docs.expo.dev/tutorial/eas/ios-development-build-for-simulators). ### Build for app stores Before the build process can start for app stores, you will need to have a store developer account and generate or provide app signing credentials. Whether you have experience with generating app signing credentials or not, EAS CLI does the heavy lifting. You can opt-in for EAS CLI to handle the app signing credentials process. Check out the steps for [Android app signing credentials](https://docs.expo.dev/build/setup#android-app-signing-credentials) or [iOS app signing credentials](https://docs.expo.dev/build/setup#ios-app-signing-credentials) process below for more information. Google Play Developer membership is required to distribute to the Google Play Store. You can build and sign your app using EAS Build, but you can't upload it to the Google Play Store unless you have a membership, a one-time \$25 USD fee. Apple Developer Program membership is required to build for the Apple App Store. If you are going to use EAS Build to create release builds for the Apple App Store, you need access to an account with a \$99 USD [Apple Developer Program](https://developer.apple.com/programs) membership. After you have confirmed that you have a Google Play Store or Apple App Store account and decided whether or not EAS CLI should handle app signing credentials, you can proceed with the following set of commands to build for the platform's store: Android iOS Terminal Copy `- ``eas build --platform android` Terminal Copy `- ``eas build --platform ios` > You can attach a message to the build by passing `--message` to the build command, for example, `eas build --platform ios --message "Some message"`. The message will appear on the website. It comes in handy when you want to leave a note with the purpose of the build for your team. Alternatively, you can use `--platform all` option to build for Android and iOS at the same time: Terminal Copy `- ``eas build --platform all` > If you have released your app to stores previously and have existing [app signing credentials](https://docs.expo.dev/app-signing/app-credentials) that you want to use, [follow these instructions to configure them](https://docs.expo.dev/app-signing/existing-credentials). #### Android app signing credentials - If you have not yet generated a keystore for your app, you can let EAS CLI take care of that for you by selecting `Generate new keystore`, and then you are done. The keystore is stored securely on EAS servers. - If you have previously built your app with `expo build:android`, you can use the same credentials here. - If you want to manually generate your keystore, see the [manual Android credentials guide](https://docs.expo.dev/app-signing/local-credentials#android-credentials) for more information. #### iOS app signing credentials - If you have not generated a provisioning profile and/or distribution certificate yet, you can let EAS CLI take care of that for you by signing into your Apple Developer Program account and following the prompts. - If you have already built your app with `expo build:ios`, you can use the same credentials here. - If you want to rather manually generate your credentials, refer to the [manual iOS credentials guide](https://docs.expo.dev/app-signing/local-credentials#ios-credentials) for more information. 5 ## Wait for the build to complete By default, the `eas build` command will wait for your build to complete, but you can interrupt it if you prefer not to wait. Monitor the progress and read the logs by following the link to the build details page that EAS CLI prompts once the build process gets started. You can also find this page by visiting [your build dashboard](https://expo.dev/builds) or running the following command: Terminal Copy `- ``eas build:list` If you are a member of an organization and your build is on its behalf, you will find the build details on [the build dashboard for that account](https://expo.dev/accounts/%5Baccount%5D/builds). > Did your build fail? Double check that you followed any applicable instructions in the [configuration step](https://docs.expo.dev/build/setup#3-configure-the-project) and refer to the [troubleshooting guide](https://docs.expo.dev/build-reference/troubleshooting) if needed. 6 ## Deploy the build If you have made it to this step, congratulations! Depending on which path you chose, you now either have a build that is ready to upload to an app store, or you have a build that you can install directly on an Android device/iOS Simulator. ### Distribute your app to an app store You will only be able to submit to an app store if you built specifically for that purpose. If you created a build for a store, [learn how to submit your app to app stores with EAS Submit](https://docs.expo.dev/submit/introduction). ### Install and run the app You will only be able to install the app directly to your Android device/iOS Simulator if you explicitly built it for that purpose. If you built for app store distribution, you will need to upload to an app store and then install it from there (for example, from Apple's TestFlight app). To learn how to install the app directly to your Android device/iOS Simulator, navigate to your build details page from [your build dashboard](https://expo.dev/accounts/%5Baccount%5D/builds) and click the "Install" button. ## Next steps We walked you through the steps to create your first build with EAS Build without going into too much depth on any particular part of the process. When you are ready to learn more, we recommend proceeding through the following topics to learn more: - [Configuration with eas.json](https://docs.expo.dev/build/eas-json) - [Internal distribution](https://docs.expo.dev/build/internal-distribution) - [Updates](https://docs.expo.dev/build/updates) - [Automating submissions](https://docs.expo.dev/build/automate-submissions) - [Triggering builds from CI](https://docs.expo.dev/build/building-on-ci) You may also want to dig through the reference section to learn more about the topics that interest you most, such as: - [Build webhooks](https://docs.expo.dev/eas/webhooks) - [Build server infrastructure](https://docs.expo.dev/build-reference/infrastructure) - How the [Android](https://docs.expo.dev/build-reference/android-builds) and [iOS](https://docs.expo.dev/build-reference/ios-builds) build processes work [Previous (EAS Build) Introduction](https://docs.expo.dev/build/introduction) [Next (EAS Build) Configure with eas.json](https://docs.expo.dev/build/eas-json) Was this doc helpful? - [Share your feedback]() - [Ask a question on the forums](https://chat.expo.dev/) - [Edit this page](https://github.com/expo/expo/edit/main/docs/pages/build/setup.mdx) - View [llms.txt](https://docs.expo.dev/llms.txt) and [llms-full.txt](https://docs.expo.dev/llms-eas.txt) - Last updated on February 28, 2026 Sign up for the Expo Newsletter Unsubscribe at any time. Read our [privacy policy](https://expo.dev/privacy). Your Privacy Choices On this page [Prerequisites](https://docs.expo.dev/build/setup/#prerequisites) [Install the latest EAS CLI](https://docs.expo.dev/build/setup/#install-the-latest-eas-cli) [Log in to your Expo account](https://docs.expo.dev/build/setup/#log-in-to-your-expo-account) [Configure the project](https://docs.expo.dev/build/setup/#configure-the-project) [Run a build](https://docs.expo.dev/build/setup/#run-a-build) [Build for Android Emulator/device or iOS Simulator](https://docs.expo.dev/build/setup/#build-for-android-emulatordevice-or-ios-simulator) [Build for app stores](https://docs.expo.dev/build/setup/#build-for-app-stores) [Wait for the build to complete](https://docs.expo.dev/build/setup/#wait-for-the-build-to-complete) [Deploy the build](https://docs.expo.dev/build/setup/#deploy-the-build) [Distribute your app to an app store](https://docs.expo.dev/build/setup/#distribute-your-app-to-an-app-store) [Install and run the app](https://docs.expo.dev/build/setup/#install-and-run-the-app) [Next steps](https://docs.expo.dev/build/setup/#next-steps) We value your privacy We use cookies to collect data and improve our services. [Learn more](https://expo.dev/privacy/cookies) Decline Accept Customize

Readable Markdown

Learn how to create a build for your app with EAS Build. [Edit page](https://github.com/expo/expo/edit/main/docs/pages/build/setup.mdx) *** > For the complete documentation index, see [llms.txt](https://docs.expo.dev/llms.txt). Use this Use this file to discover all available pages. EAS Build allows you to build a ready-to-submit binary of your app for the Google Play Store or Apple App Store. In this guide, let's learn how to do that. Alternatively, if you prefer to install the app directly to your Android device/emulator or install it in the iOS Simulator, we will point you toward resources that explain how to do that. For a small app, builds for Android and iOS platforms trigger within a few minutes. If you encounter any issues along the way, you can reach out on [Discord and Forums](https://chat.expo.dev/). ## Prerequisites EAS Build is a rapidly evolving service. Before you set out to create a build for your project we recommend consulting the [limitations](https://docs.expo.dev/build-reference/limitations) page and the other prerequisites below. A React Native Android and/or iOS project that you want to build An Expo user account 1 ## Install the latest EAS CLI EAS CLI is the command-line app that you will use to interact with EAS services from your terminal. To install it, run the command: `- ``npm install -g eas-cli` You can also use the above command to check if a new version of EAS CLI is available. We encourage you to always stay up to date with the latest version. > We recommend using `npm` instead of `yarn` for global package installations. You may alternatively use `npx eas-cli@latest`. Remember to use that instead of `eas` whenever it's called for in the documentation. 2 ## Log in to your Expo account If you are already signed in to an Expo account using Expo CLI, you can skip the steps described in this section. If you are not, run the following command to log in: `- ``eas login` You can check whether you are logged in by running `eas whoami`. 3 ## Configure the project To configure an Android or an iOS project for EAS Build, run the following command: `- ``eas build:configure` To learn more about what happens behind the scenes, see [build configuration process reference](https://docs.expo.dev/build-reference/build-configuration). For development, we recommend creating a [development build](https://docs.expo.dev/develop/development-builds/introduction), which is a debug build of your app and contains the [`expo-dev-client`](https://docs.expo.dev/versions/latest/sdk/dev-client) library. It helps you iterate as quickly as possible and provides a more flexible, reliable, and complete development environment. To install the library, run the following command: `- ``npx expo install expo-dev-client` Additional configuration may be required for some scenarios: - Does your app code depend on environment variables? [Add them to your build configuration](https://docs.expo.dev/eas/environment-variables). - Is your project inside of a monorepo? [Follow these instructions](https://docs.expo.dev/build-reference/build-with-monorepos). - Do you use private npm packages? [Add your npm token](https://docs.expo.dev/build-reference/private-npm-packages). - Does your app depend on specific versions of tools like Node, Yarn, npm, CocoaPods, or Xcode? [Specify these versions in your build configuration](https://docs.expo.dev/build/eas-json). 4 ## Run a build ### Build for Android Emulator/device or iOS Simulator The easiest way to try out EAS Build is to create a build that you can run on your Android device/emulator or iOS Simulator. It's quicker than uploading it to a store, and you don't need store developer membership accounts. If you'd like to try this, read about [creating an installable APK for Android](https://docs.expo.dev/tutorial/eas/android-development-build) and [creating a simulator build for iOS](https://docs.expo.dev/tutorial/eas/ios-development-build-for-simulators). ### Build for app stores Before the build process can start for app stores, you will need to have a store developer account and generate or provide app signing credentials. Whether you have experience with generating app signing credentials or not, EAS CLI does the heavy lifting. You can opt-in for EAS CLI to handle the app signing credentials process. Check out the steps for [Android app signing credentials](https://docs.expo.dev/build/setup#android-app-signing-credentials) or [iOS app signing credentials](https://docs.expo.dev/build/setup#ios-app-signing-credentials) process below for more information. Google Play Developer membership is required to distribute to the Google Play Store. Apple Developer Program membership is required to build for the Apple App Store. After you have confirmed that you have a Google Play Store or Apple App Store account and decided whether or not EAS CLI should handle app signing credentials, you can proceed with the following set of commands to build for the platform's store: `- ``eas build --platform android` > You can attach a message to the build by passing `--message` to the build command, for example, `eas build --platform ios --message "Some message"`. The message will appear on the website. It comes in handy when you want to leave a note with the purpose of the build for your team. Alternatively, you can use `--platform all` option to build for Android and iOS at the same time: `- ``eas build --platform all` > If you have released your app to stores previously and have existing [app signing credentials](https://docs.expo.dev/app-signing/app-credentials) that you want to use, [follow these instructions to configure them](https://docs.expo.dev/app-signing/existing-credentials). #### Android app signing credentials - If you have not yet generated a keystore for your app, you can let EAS CLI take care of that for you by selecting `Generate new keystore`, and then you are done. The keystore is stored securely on EAS servers. - If you have previously built your app with `expo build:android`, you can use the same credentials here. - If you want to manually generate your keystore, see the [manual Android credentials guide](https://docs.expo.dev/app-signing/local-credentials#android-credentials) for more information. #### iOS app signing credentials - If you have not generated a provisioning profile and/or distribution certificate yet, you can let EAS CLI take care of that for you by signing into your Apple Developer Program account and following the prompts. - If you have already built your app with `expo build:ios`, you can use the same credentials here. - If you want to rather manually generate your credentials, refer to the [manual iOS credentials guide](https://docs.expo.dev/app-signing/local-credentials#ios-credentials) for more information. 5 ## Wait for the build to complete By default, the `eas build` command will wait for your build to complete, but you can interrupt it if you prefer not to wait. Monitor the progress and read the logs by following the link to the build details page that EAS CLI prompts once the build process gets started. You can also find this page by visiting [your build dashboard](https://expo.dev/builds) or running the following command: `- ``eas build:list` If you are a member of an organization and your build is on its behalf, you will find the build details on [the build dashboard for that account](https://expo.dev/accounts/%5Baccount%5D/builds). > Did your build fail? Double check that you followed any applicable instructions in the [configuration step](https://docs.expo.dev/build/setup#3-configure-the-project) and refer to the [troubleshooting guide](https://docs.expo.dev/build-reference/troubleshooting) if needed. 6 ## Deploy the build If you have made it to this step, congratulations! Depending on which path you chose, you now either have a build that is ready to upload to an app store, or you have a build that you can install directly on an Android device/iOS Simulator. ### Distribute your app to an app store You will only be able to submit to an app store if you built specifically for that purpose. If you created a build for a store, [learn how to submit your app to app stores with EAS Submit](https://docs.expo.dev/submit/introduction). ### Install and run the app You will only be able to install the app directly to your Android device/iOS Simulator if you explicitly built it for that purpose. If you built for app store distribution, you will need to upload to an app store and then install it from there (for example, from Apple's TestFlight app). To learn how to install the app directly to your Android device/iOS Simulator, navigate to your build details page from [your build dashboard](https://expo.dev/accounts/%5Baccount%5D/builds) and click the "Install" button. ## Next steps We walked you through the steps to create your first build with EAS Build without going into too much depth on any particular part of the process. When you are ready to learn more, we recommend proceeding through the following topics to learn more: You may also want to dig through the reference section to learn more about the topics that interest you most, such as:

ML Classification

ML Categories

/Computers_and_Electronics		85.8%
/Computers_and_Electronics/Software		79.9%
/Computers_and_Electronics/Software/Software_Utilities		69.2%
/Internet_and_Telecom		36.3%
/Internet_and_Telecom/Web_Services		31.2%
/Internet_and_Telecom/Web_Services/Web_Design_and_Development		29.0%

Raw JSON

{
    "/Computers_and_Electronics": 858,
    "/Computers_and_Electronics/Software": 799,
    "/Computers_and_Electronics/Software/Software_Utilities": 692,
    "/Internet_and_Telecom": 363,
    "/Internet_and_Telecom/Web_Services": 312,
    "/Internet_and_Telecom/Web_Services/Web_Design_and_Development": 290
}

ML Page Types

/Document		77.0%
/Document/Manual		76.1%

Raw JSON

{
    "/Document": 770,
    "/Document/Manual": 761
}

ML Intent Types

Informational

96.6%

Raw JSON

{
    "Informational": 966
}

Content Metadata

Language

Author

null

Publish Time

not set

Original Publish Time

2021-08-03 06:10:18 (4 years ago)

Republished

Word Count (Total)

1,889

Word Count (Content)

1,343

Links

External Links

Internal Links

135

Technical SEO

Meta Nofollow

Meta Noarchive

JS Rendered

Yes

Redirect Target

null

Performance

Download Time (ms)

TTFB (ms)

Download Size (bytes)

29,887

Shard

50 (laksa)

Root Hash

9098366656517426850

Unparsed URL

dev,expo!docs,/build/setup/ s443