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). 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 created a build for a store, learn how to submit your app to app stores with EAS Submit. You will only be able to submit to an app store if you built specifically for that purpose. 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. If you want to rather manually generate your credentials, refer to the manual iOS credentials guide for more information.If you have already built your app with expo build:ios, you can use the same credentials here.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 want to manually generate your keystore, please see the manual Android credentials guide for more information.If you have previously built your app with expo build:android, you can use the same credentials here.

The keystore is stored securely on EAS servers. 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.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.

Deep Work for android instal