Do not use .newPassword content type within simulator

[Supereg]

Do not use .newPassword content type within simulator

:recycle: Current situation & Problem

Previously, we would disable password auto-fill within the simulator to avoid the simulator proposing a pre-filled password that would otherwise interfere with our UI tests. This approach broke with iOS 17.2 simulator and our workaround seems to not always work. Instead, this PR just avoids using the .newPassword content type when running within the simulator.

:gear: Release Notes

• Avoid using .newPassword text content type when running within the simulator.

:books: Documentation

Inline docs were added.

:white_check_mark: Testing

--

:pencil: Code of Conduct & Contributing Guidelines

By submitting creating this pull request, you agree to follow our Code of Conduct and Contributing Guidelines:

• [x] I agree to follow the Code of Conduct and Contributing Guidelines.

[codecov[bot]]

Codecov Report

Attention: Patch coverage is 0% with 10 lines in your changes are missing coverage. Please review.

Project coverage is 0.00%. Comparing base (1ced521) to head (c6f477d).

Additional details and impacted files

[](https://app.codecov.io/gh/StanfordSpezi/SpeziAccount/pull/52?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=StanfordSpezi) ```diff @@ Coverage Diff @@ ## main #52 +/- ## ========================================== - Coverage 76.27% 0.00% -76.26% ========================================== Files 116 116 Lines 4002 4012 +10 ========================================== - Hits 3052 0 -3052 - Misses 950 4012 +3062 ``` | [Files](https://app.codecov.io/gh/StanfordSpezi/SpeziAccount/pull/52?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=StanfordSpezi) | Coverage Δ | | |---|---|---| | [...s/SpeziAccount/AccountValue/Keys/PasswordKey.swift](https://app.codecov.io/gh/StanfordSpezi/SpeziAccount/pull/52?src=pr&el=tree&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=StanfordSpezi#diff-U291cmNlcy9TcGV6aUFjY291bnQvQWNjb3VudFZhbHVlL0tleXMvUGFzc3dvcmRLZXkuc3dpZnQ=) | `0.00% <0.00%> (-81.25%)` | :arrow_down: | ... and [101 files with indirect coverage changes](https://app.codecov.io/gh/StanfordSpezi/SpeziAccount/pull/52/indirect-changes?src=pr&el=tree-more&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=StanfordSpezi) ------ [Continue to review full report in Codecov by Sentry](https://app.codecov.io/gh/StanfordSpezi/SpeziAccount/pull/52?src=pr&el=continue&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=StanfordSpezi). > **Legend** - [Click here to learn more](https://docs.codecov.io/docs/codecov-delta?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=StanfordSpezi) > `Δ = absolute (impact)`, `ø = not affected`, `? = missing data` > Powered by [Codecov](https://app.codecov.io/gh/StanfordSpezi/SpeziAccount/pull/52?src=pr&el=footer&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=StanfordSpezi). Last update [1ced521...c6f477d](https://app.codecov.io/gh/StanfordSpezi/SpeziAccount/pull/52?src=pr&el=lastupdated&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=StanfordSpezi). Read the [comment docs](https://docs.codecov.io/docs/pull-request-comments?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=StanfordSpezi).