Frequent Failures on Bitrise – pr_smoke_e2e_pipeline

### What is this about?

Over the last five days, we've observed an increase in failures on Bitrise when running the `pr_smoke_e2e_pipeline`. The last successful run was on **7th February** ([link](https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/9d5e0a93-d0de-4aa4-a5d1-80660b8c5be5?tab=workflows)), but since then, failures have become more frequent.

## Details & Observations
- **Affected pipeline:** [`pr_smoke_e2e_pipeline`](https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/cd2cc86a-5b1d-4625-b9b3-bcb87a0d38cf?tab=workflows)
- **Failures started occurring consistently after:** **7th February**
- **Potential areas to investigate:**
- Flaky tests?
- Environment changes on Bitrise?
- Dependencies updated?

## Next Steps
- Review recent commits and changes since the last passing build
- Check logs for common failure patterns

### Scenario

_No response_

### Design

_No response_

### Technical Details

_No response_

### Threat Modeling Framework

_No response_

### Acceptance Criteria

_No response_

### Stakeholder review needed before the work gets merged

- [ ] Engineering (needed in most cases)
- [ ] Design
- [ ] Product
- [ ] QA (automation tests are required to pass before merging PRs but not all changes are covered by automation tests - please review if QA is needed beyond automation tests)
- [ ] Security
- [ ] Legal
- [ ] Marketing
- [ ] Management (please specify)
- [ ] Other (please specify)

### References

_No response_

Start with the Bitrise pr_smoke_e2e_pipeline logs and review commits made since the last successful run on 7th February. Look for a recurring failure pattern and determine whether it comes from flaky tests, an environment change, or updated dependencies. Done means the pipeline runs reliably again with the failure cause addressed.

Written by the indexing model from the issue text.