Create an Internal Distribution (Preview) build for sharing your app in internally in production mode.
This is the only way to share your iPhone app without submitting it to TestFlight and is often used for QA testing or internal demos.
📝 Docs
[00:00] An internal distribution build is for when you want to install your app in production mode without publishing into TestFlight. This could be used for example for QA testing or internal demos. In general, it's preferable to do things like user acceptance testing and stakeholder demos in test flight builds, but this method of sharing builds [00:20] can be necessary sometimes. Let's look at the EIS JSON. We want to use the preview build configuration. Notice that the only difference between this and the development configuration is that we are not enabling the dev client. For the preview build, we'll be using the same ad hoc provisioning profile [00:39] and the distribution certificate as we did for the previous build. So there's nothing additional to set up. Now open the terminal and type in e a s build profile preview platform Ios. Even though all of our certificates are set up, the e s c l I will still ask you to log in to your Apple account so you could verify everything is up to date. Every [00:59] time you build with the ad hoc profile, you'll have the opportunity to add or remove devices from the profile. For now, we can reuse the profile as is and skip setting up push notifications. And now we wait for the build to run. Now when the build is finished, we want to open the camera app and scan the QR code and install [01:19] the app. Notice that this time, we didn't need to start the development server. That's because we didn't include the dev client. So the app is using just the version of JavaScript that was bundled inside, and you won't be able to update it on the fly.
Member comments are a way for members to communicate, interact, and ask questions about a lesson.
The instructor or someone from the community might respond to your question Here are a few basic guidelines to commenting on egghead.io
Be on-Topic
Comments are for discussing a lesson. If you're having a general issue with the website functionality, please contact us at support@egghead.io.
Avoid meta-discussion
Code Problems?
Should be accompanied by code! Codesandbox or Stackblitz provide a way to share code and discuss it in context
Details and Context
Vague question? Vague answer. Any details and context you can provide will lure more interesting answers!