[Post Onboarding] Fetching profile data #17028
Assignees
Milestone
Comments
jrainville
added a commit
to status-im/status-go
that referenced
this issue
Jan 15, 2025
Needed for status-im/status-desktop#17028 When a user imports an old account, we start fetching the backups. Now, we show an activity center notification to let the user know, because the onboarding doesn't block during the fetching anymore, so it happens in the background. After a timeout, the notification turns into a failure state (full or partial). The user can then restart the fetching. I added a test to validate the logic of calculating if the fetching was a success. That logic used to be in Nim.
jrainville
added a commit
that referenced
this issue
Jan 15, 2025
Fixes #17028 When an old user imports an account, we now fetch the backups in the background and show an AC notification. When the fetch is successful, the AC notif switches to a success message. If after a timeout we detect that we didn't fetch anything or just part, we show an error and the possibility to try again.
4 tasks
jrainville
added a commit
to status-im/status-go
that referenced
this issue
Jan 15, 2025
Needed for status-im/status-desktop#17028 When a user imports an old account, we start fetching the backups. Now, we show an activity center notification to let the user know, because the onboarding doesn't block during the fetching anymore, so it happens in the background. After a timeout, the notification turns into a failure state (full or partial). The user can then restart the fetching. I added a test to validate the logic of calculating if the fetching was a success. That logic used to be in Nim.
jrainville
added a commit
that referenced
this issue
Jan 15, 2025
Fixes #17028 When an old user imports an account, we now fetch the backups in the background and show an AC notification. When the fetch is successful, the AC notif switches to a success message. If after a timeout we detect that we didn't fetch anything or just part, we show an error and the possibility to try again.
jrainville
added a commit
that referenced
this issue
Jan 16, 2025
Fixes #17028 When an old user imports an account, we now fetch the backups in the background and show an AC notification. When the fetch is successful, the AC notif switches to a success message. If after a timeout we detect that we didn't fetch anything or just part, we show an error and the possibility to try again.
jrainville
added a commit
that referenced
this issue
Jan 16, 2025
Fixes #17028 When an old user imports an account, we now fetch the backups in the background and show an AC notification. When the fetch is successful, the AC notif switches to a success message. If after a timeout we detect that we didn't fetch anything or just part, we show an error and the possibility to try again.
jrainville
added a commit
to status-im/status-go
that referenced
this issue
Jan 23, 2025
Needed for status-im/status-desktop#17028 When a user imports an old account, we start fetching the backups. Now, we show an activity center notification to let the user know, because the onboarding doesn't block during the fetching anymore, so it happens in the background. After a timeout, the notification turns into a failure state (full or partial). The user can then restart the fetching. I added a test to validate the logic of calculating if the fetching was a success. That logic used to be in Nim.
jrainville
added a commit
that referenced
this issue
Jan 23, 2025
Fixes #17028 When an old user imports an account, we now fetch the backups in the background and show an AC notification. When the fetch is successful, the AC notif switches to a success message. If after a timeout we detect that we didn't fetch anything or just part, we show an error and the possibility to try again.
jrainville
added a commit
to status-im/status-go
that referenced
this issue
Jan 24, 2025
Needed for status-im/status-desktop#17028 When a user imports an old account, we start fetching the backups. Now, we show an activity center notification to let the user know, because the onboarding doesn't block during the fetching anymore, so it happens in the background. After a timeout, the notification turns into a failure state (full or partial). The user can then restart the fetching. I added a test to validate the logic of calculating if the fetching was a success. That logic used to be in Nim.
jrainville
added a commit
that referenced
this issue
Jan 24, 2025
Fixes #17028 When an old user imports an account, we now fetch the backups in the background and show an AC notification. When the fetch is successful, the AC notif switches to a success message. If after a timeout we detect that we didn't fetch anything or just part, we show an error and the possibility to try again.
jrainville
added a commit
that referenced
this issue
Jan 24, 2025
Fixes #17028 When an old user imports an account, we now fetch the backups in the background and show an AC notification. When the fetch is successful, the AC notif switches to a success message. If after a timeout we detect that we didn't fetch anything or just part, we show an error and the possibility to try again.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
After successful onboarding via sync/pairing, display the "Fetching profile details" AC notifications:
When finished, display one of the toasts:
Figma: https://www.figma.com/design/Lw4nPYQcZOPOwTgETiiIYo/Desktop-Onboarding-Redesign?node-id=281-29292&m=dev
The text was updated successfully, but these errors were encountered: