Following the process for distributing an app...
- Build for Release
- Archive
- Export the .ipa for development (sanity testing in our case)
- Export the .ipa for the App Store
- Push the App Store build to App Store Connect
- Make the build available in TestFlight to App Store Connect Users
- Make the build available in TestFlight to External Users
- Publish in App Store 🙂
Q1: Can steps 1 and 2 be combined using a single xcodebuild command with the archive parameter and Release configuration specified? It doesn't always work as expected now that we are using the 'New Build System' (Xcode 10.2). Sometimes it doesn't build a static library we have in the project 😕.
Q2: Step 3 has the issue of getting Push Notifications to work. That is, Push Notifications only work for App Store builds if the app was downloaded from the store (or TestFlight). How do you indicate to your server this is not an App Store build and to use the APN debug sandbox instead. That being the case, why not skip step 3 and just have Sanity testers in the TestFlight Users group?
Thoughts?
