Lines Matching refs:and

9 …tures and fixed bugs in our app, we want to deliver those features and bug fixes out to our users …
10 …. On the other hand, we could make test builds, share them with a QA team, and release periodicall…
12 Depending on your project, you'll have some tolerance for how "fast" and how "safe" you'll need to …
18 …- (b) We can create builds for production use and separate builds for pre-production change testin…
20    - (a) We can test changes with TestFlight and Play Store Internal Track.
25    - (b) We can create update branches that are environment-based, like "production" and "staging".
28 … can mix, match, and tweak the parts above to create a process that is the right balance of releas…
36 This flow is the simplest and fastest flow, with the fewest amount of safety checks. It's great for…
54 1. Develop a project locally and test changes in a development build or in Expo Go.
55 …bmit them to app stores. These builds are for public use, and should be submitted/reviewed, and re…
69 …k release versions with branches. Instead, we'll have persistent "staging" and "production" branch…
71 **Creating builds:** (b) Create builds for production and separate builds for testing.
73 **Testing changes:** (a) Test changes on TestFlight and the Play Store Internal Track and/or (b) Te…
75 **Publishing updates:** (b) Create update branches that are environment-based, like "staging" and "…
87 1. Develop a project locally and test changes in Expo Go.
88 …wed and become available on app stores. Create another set of builds with channels named "staging"…
90 4. Merge changes into a branch named "staging". The GitHub Action will publish an update and make i…
95 …ent of the pace of development. This adds an extra chance to test your app and avoids your user ha…
96 … since deploying updates occurs when merging into GitHub branches named "staging" and "production".
101 - When merging to "production", the update would be re-built and re-published instead of moved from…
105 …build and update their Android and iOS apps separately all the time. It will result in separate co…
107 **Creating builds:** (a) Create builds for production only, or (b) create builds for production and…
109 **Testing changes:** (a) Test changes on TestFlight and the Play Store Internal Track and/or (b) Te…
111 …date branches that are environment- and platform-based, like "ios-staging", "ios-production", "and…
123 1. Develop a project locally and test changes in Expo Go.
124 …and "android-production". Then put the "ios-staging" build on TestFlight and submit the "ios-produ…
126 …ewise, merge changes for the Android app into the branch "android-staging" and when ready, into th…
130 - This flow gives you full control of which updates go to your Android and iOS builds. Updates will…
140 …and does not support automatic [runtime version policies](/eas-update/runtime-versions/#setting-ru…
144 **Creating builds:** (b) Create builds for production (one per major version) and separate builds f…
146 **Testing changes:** (a) Test changes on TestFlight and the Play Store Internal Track and/or (b) Te…
160 1. Develop a project locally and test changes in Expo Go or a [development build](/develop/developm…
161 …wed and become available on app stores. Create another set of builds with channels named "staging"…
164 …date branch "version-1". Test the update by opening the apps on TestFlight and the Play Store Inte…
170 …3. Merge commits into the "version-2" branch until the new features and fixes are ready and stable.
177 …5. Merge commits into the "version-2" branch until the new features and fixes are ready and stable.
178 … with channel named "production-rtv-2", which will eventually get reviewed and become available on…
183 …dates are tested on test builds which are distributed to internal testers, and branches are moved …
184 …and EAS Update branches. It also creates a mapping between GitHub commits and EAS Update updates. …
191 …ng with your team which branches are currently pointed at your test builds and your production bui…