[Technical Questions] Pushing changes to TestFlight

[MiguelAFH]

In what area do you have a technical challenge?

Other (non-StanfordBDHG-related) area

Description

Hello,
I am trying to push the latest version of our app to TestFlight to test on a physical phone. After taking a look online, it seems we have to archive the project in XCode and then do something else. However, when I try to do so, XCode build fails with the error:

/Users/miguel/Library/CloudStorage/OneDrive-Personal/Stanford/Winter2025/CS342/Project/2025-CoughSync/CoughSync.xcodeproj No profile for team '637867499T' matching 'CS342 2025 CoughSync' found: Xcode couldn't find any provisioning profiles matching '637867499T/CS342 2025 CoughSync'. Install the profile (by dragging and dropping it onto Xcode's dock item) or select a different one in the Signing & Capabilities tab of the target editor.

Can you point me in the right direction?

Reproduction

The app will sometimes get updated into TestFlight without us asking for it.

Expected behavior

Being able to push our app at will to test it on a physical device.

Additional context

No response

Code of Conduct

• I agree to follow this course's Code of Conduct and Contributing Guidelines

[PSchmiedmayer]

Hi @MiguelAFH,
A TestFlight release is automatically build and test every time you and your team merge a PR to the main branch as long as your application successfully compiles and doesn't contain any errors that would cause a failure on uploading it to App Store Connect: https://github.com/CS342/2025-CoughSync/actions/workflows/beta-deployment.yml

it seems like you and your team have merged a few elements into the main branch that are failing on uploading them to App Store Connect, e.g.,: https://github.com/CS342/2025-CoughSync/actions/runs/13312015704/job/37177494417#step:19:2029. It seems like the icon you have bundled in the app is not according to the Apple Specification. Please ensure that you follow the following article and fix this in subsequent PRs to ensure that the beta deployment is continuing to function as expected: https://developer.apple.com/documentation/xcode/configuring-your-app-icon

[MiguelAFH]

Thank you Paul, that is our bad.

I have looked into the resource you shared and made the adjustment for Single Size icon for iOS. This involved removing all the icons other than the 1024x1024 one.
I have executed all tests in my local env but my PR is failing on the Build and Test / Test using xcodebuild or run fastlane step. The error I get is this:

/opt/homebrew/Cellar/ruby/3.4.2/lib/ruby/3.4.0/rubygems/dependency.rb:303:in 'Gem::Dependency#to_specs': Could not find 'nkf' (>= 0) - did find: [nkf-0.2.0] (Gem::MissingSpecVersionError)
Checked in 'GEM_PATH=/Users/githubaction/.local/share/fastlane/3.4.0:/opt/homebrew/Cellar/fastlane/2.226.0_1/libexec' , execute `gem env` for more information

I found a similar issue under Discussions, but ours seem to be a problem with the pipeline. Any ideas on what would this be?

[PSchmiedmayer]

Interesting; this seems like an issue with the GitHub Action runners. I just installed it again on our runners and saw that you restarted the workflow. Let's see if it works now.

I am not sure if the GitHub hosted runners will work, they might need to fix it that on their side. We might need to create an issue in https://github.com/actions/runner-images on this.

[MiguelAFH]

It worked this time! Another question, I don't want to make the same mistake as before of merging the PR if that check won't pass. I see all the tests are passing in the PR other than the code coverage. When I look at the actions you shared, I see the TestFlight step. However, I don't see the same test on the actions from the new PR. How can I make sure this change will pass the TestFlight step correctly?

[PSchmiedmayer]

We build and test the app in the action but can not really test if it would be successfully uploaded to App Store Connect without doing that step as part of the test (which we also don't want to do as it is not yet merged and ready for release). So those things will only really be caught on the main branch and might need to be resolved with subsequent PRs.