Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make sure the Recovery Key option is shown on the IdentityConfirmationScreen when available. #3699

Merged
merged 2 commits into from
Jan 23, 2025

Conversation

pixlwave
Copy link
Member

@pixlwave pixlwave commented Jan 23, 2025

There was a race condition where 2 different states could be processed at the same time:
Even though the method is @MainActor, the fact it has an await means that if another Task is spawned when a previous one is suspended, there was no guarantee that they would resume in the same order. This PR calls the method using a for await in to process the states serially.

…nScreen when available.

There was a race condition where 2 different states could be processed at the same time.
@pixlwave pixlwave added the pr-bugfix for bug fix label Jan 23, 2025
@pixlwave pixlwave requested a review from a team as a code owner January 23, 2025 10:37
@pixlwave pixlwave requested review from stefanceriu and removed request for a team January 23, 2025 10:37
Copy link
Member

@stefanceriu stefanceriu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🙌

Copy link

codecov bot commented Jan 23, 2025

❌ 1 Tests Failed:

Tests completed Failed Passed Skipped
917 1 916 0
View the top 1 failed tests by shortest run time
CompletionSuggestionServiceTests testUserSuggestionsWithEmptyText()
Stack Traces | 11.6s run time
Asynchronous wait failed: Exceeded timeout of 10 seconds, with unfulfilled expectations: "Awaiting publisher". (.../Other/Extensions/XCTestCase.swift:43)

To view more test analytics, go to the Test Analytics Dashboard
📢 Thoughts on this report? Let us know!

The view model wasn't stored, so relying the current value publisher didn't have time to fire before deinit.
Copy link

Warnings
⚠️ You seem to have made changes to views. Please consider adding screenshots.

Generated by 🚫 Danger Swift against 2d88f34

@pixlwave pixlwave merged commit a70189d into develop Jan 23, 2025
13 checks passed
@pixlwave pixlwave deleted the doug/recovery-key-button branch January 23, 2025 12:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr-bugfix for bug fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants