-
Notifications
You must be signed in to change notification settings - Fork 9
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
ABW-1839 App spills some runtime warnings after the creation of an account on simulator #596
Conversation
@@ -98,6 +98,8 @@ public struct DerivePublicKeys: Sendable, FeatureReducer { | |||
case .device: | |||
return .task { | |||
do { | |||
try? await Task.sleep(for: .seconds(1)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, right?! Better than what we have now.
The runtime issues only went away when using 1000 ms..? What happens if you use 250ms?
It's better for sure, as it eliminates warnings and overengineering (the "noop" We're good with 500 + something... 700 is a safe bet I think. Will clean it up and make a proper PR tomorrow 👍 JFYI @CyonAlexRDX - we may also consider future-proofing |
# Conflicts: # App/BabylonWallet.xcodeproj/project.pbxproj
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Jira ticket: paste link here
Description
This PR solves the problem with warnings. In the scope I cleaned up the unnecessary
@MainActor
attributes, as well as eliminated the noopCreationOfAccount.ViewAction.onFirstTask
.Notes
The journey has been discussed here in Slack. I think it would be good to ultimately solve it in a more generic way, but the current implementation should be fine for now.
How to test
I'd suggest trying on at least two devices, just to make sure, as this is kind of a critical path for first time users.
Happy path (or test variation 1)
Unhappy path (or test variation 2)
I'd also suggest smoke-testing for other onboarding paths (restore, ledger).
Video
As requested by @CyonAlexRDX:
RPReplay_Final1688030995.MP4
PR submission checklist