SpeziTemplateApplication testOnboardingFlow failing #80
-
What Stanford Spezi module is your challenge related to?SpeziTemplateApplication DescriptionI've updated to the latest package versions and incorporated the changes from THIS PR into my Spezi Template Application; however, the I'm not sure how to proceed in debugging this and would appreciate some help. ![]() ![]() ReproductionRun the Expected behavior
Additional contextThis is for the Stanford360 Team for CS 342. The test is failing on the CI as shown here. Code of Conduct
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
@kkellybonilla Thank you for reaching out! I just checked out the branch and GitHub Action run at https://github.com/CS342/2025-Stanford-360/actions/runs/13195705266?pr=8. If you download the Artifacts at the bottom of the screen, you can see the video recording of the test on the runner: If you watch the video, it seems like the simulator completely crashed at that point, which is not your fault; it was a bug in Xcode and the iOS simulator by Apple. Unfortunately, we see that in about 5% of CI runs, and it only got worse in newer Xcode versions. We are not the only ones struggling with that; it is a known issue. The best suggestion out there is to reset all simulators, and we do exactly that before the run. In short, I would suggest just re-running the test in the CI. In these cases, there is a button to "Re-run jobs" and then an option to restart only failing ones on GitHub: Regarding your local test: This seems to be a separate issue. It might be that your Firestore emulator is not running or might have an old user account there that fails to create a new account. I would suggest shutting down any instances of the emulator (control + C) and then restarting the emulator at the root of your project folder using |
Beta Was this translation helpful? Give feedback.
@kkellybonilla Thank you for reaching out!
I just checked out the branch and GitHub Action run at https://github.com/CS342/2025-Stanford-360/actions/runs/13195705266?pr=8. If you download the Artifacts at the bottom of the screen, you can see the video recording of the test on the runner:
If you watch the video, it seems like the simulator completely crashed at that point, which is not your fault; it was a bug in Xcode and the iOS simulator by Apple. Unfortunately, we see that in about 5% of CI runs, and it only got worse in newer Xcode versions. We are not the only ones struggling with that; it is a known issue. The best suggestion out there is to reset all simulators, and we do exactly…