[Technical Questions] Build and Test failing

[shamit05]

In what area do you have a technical challenge?

Other (non-StanfordBDHG-related) area

Description

The build and test check is failing when trying to merge branches. It gives the following error:

(error = Error Domain=FBSOpenApplicationServiceErrorDomain Code=4 "Simulator device failed to launch shamit.edu.stanford.cs342.2025.feedbridge." UserInfo={BSErrorCodeDescription=InvalidRequest, NSUnderlyingError=0x60000121ff90 {Error Domain=FBSOpenApplicationServiceErrorDomain Code=4 "The request to open "shamit.edu.stanford.cs342.2025.feedbridge" failed." UserInfo={NSLocalizedDescription=The request to open "shamit.edu.stanford.cs342.2025.feedbridge" failed., BSErrorCodeDescription=InvalidRequest, FBSOpenApplicationRequestID=0x6043, NSUnderlyingError=0x60000121d020 {Error Domain=FBSOpenApplicationErrorDomain Code=4 "Application info provider (FBSApplicationLibrary) returned nil for "shamit.edu.stanford.cs342.2025.feedbridge"" UserInfo={BSErrorCodeDescription=NotFound, NSLocalizedFailureReason=Application info provider (FBSApplicationLibrary) returned nil for "shamit.edu.stanford.cs342.2025.feedbridge"}}}}, FBSOpenApplicationRequestID=0x6043, SimCallingSelector=launchApplicationWithID:options:pid:error:, NSLocalizedDescription=Simulator device failed to launch shamit.edu.stanford.cs342.2025.feedbridge.})

Reproduction

Under signing, I have the bundle identifier as shamit.edu.stanford.cs342.2025.feedbridge, because if I use edu.stanford.cs342.2025.feedbridge, it gives the error: cannot be registered to your development team because it is not available. Change your bundle identifier to a unique string to try again.

Look at the job here:
https://github.com/CS342/2025-Feedbridge/actions/runs/13797864700/job/38593725884

Expected behavior

It should run properly.

Additional context

Does this possibly have something to do with signing capabilities?

Code of Conduct

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

[nriedman]

Hi @shamit05! Seeing an error about the simulator failing to launch is actually expected behavior as we uninstall and reinstall the application between tests. However, the bundle identifier should not be changed (especially in main). This may be causing the failure -- the build fails because the UI tests fail.

Can you provide more specific information about the error that appears when you use the regular bundle id? Does it have to do with "signing capabilities"? Changing it locally is fine, but when you commit to the branch you should avoid committing that change.

[shamit05]

We pushed to main after changing the bundle identifier back to what it was before (edu.stanford.cs342.2025.feedbridge). However, it is still giving the same error:

[01:58:18]: ▸ ::error file=/Users/runner/work/2025-Feedbridge/2025-Feedbridge/Feedbridge.xcodeproj::No profiles for 'edu.stanford.cs342.2025.feedbridge' were found: Xcode couldn't find any iOS App Development provisioning profiles matching 'edu.stanford.cs342.2025.feedbridge'. Automatic signing is disabled and unable to generate a profile. To enable automatic signing, pass -allowProvisioningUpdates to xcodebuild. (in target 'Feedbridge' from project 'Feedbridge')
[01:58:18]: ▸ note: Disabling previews because SWIFT_VERSION is set and SWIFT_OPTIMIZATION_LEVEL=-O, expected -Onone (in target 'Feedbridge' from project 'Feedbridge')
[01:58:18]: ▸ note: Run script build phase 'SwiftPackageListPlugin' will be run during every build because the option to run the script phase "Based on dependency analysis" is unchecked. (in target 'Feedbridge' from project 'Feedbridge')
[01:58:18]: ▸ ** ARCHIVE FAILED **
[01:58:18]: ▸ The following build commands failed:
[01:58:18]: ▸ 	Archiving project Feedbridge with scheme Feedbridge
[01:58:18]: ▸ (1 failure)

[shamit05]

You can see the full logs here: https://github.com/CS342/2025-Feedbridge/actions/runs/13824582711/job/38678836402

[nriedman]

Try enabling automatic signing in Release:

(Example of what that looks like, check the "Automatically manage signing" box/button in the Release section).

Having this checked in debug might throw an error locally due to provisioning profile/developer account being missing, but looks like it might help here.