Page MenuHomePhabricator

[native] disable navigation in `RestoreBackupScreen`
ClosedPublic

Authored by kamil on Feb 24 2025, 6:35 AM.
Tags
None
Referenced Files
F5109354: D14398.id47269.diff
Tue, Apr 1, 6:21 PM
F5107547: D14398.id.diff
Tue, Apr 1, 11:33 AM
F5103665: D14398.id47232.diff
Mon, Mar 31, 11:38 PM
Unknown Object (File)
Mon, Mar 31, 1:04 PM
Unknown Object (File)
Sat, Mar 29, 4:16 PM
Unknown Object (File)
Mon, Mar 17, 9:39 PM
Unknown Object (File)
Fri, Mar 14, 4:30 AM
Unknown Object (File)
Fri, Mar 14, 4:26 AM
Subscribers

Details

Summary

Part of ENG-10240.

Using the same approach as for Register account screen.

Test Plan
  1. It is not possible to get back using header
  2. It is not possible to use system back button
  3. Swipe back gesture is not working
  4. After restore user is navigated to app
  5. After failure and confirming alert user is navigated back to credentials

Tested on physical iOS and physical Android.

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable

Event Timeline

kamil held this revision as a draft.
kamil published this revision for review.Feb 24 2025, 6:48 AM
tomek added inline comments.
native/account/restore-backup-screen.react.js
54–56 ↗(On Diff #47232)

Why do we have to filter out some actions? In the linked code from the registration flow, we don't have to do any filtering.

This revision is now accepted and ready to land.Feb 24 2025, 8:33 AM

Just confirming – is this screen only used when the restore is in-progress? If the button to start is on this screen too, we might want to only prevent the user from navigating away after the button is pressed

native/account/restore-backup-screen.react.js
54–56 ↗(On Diff #47232)

Presumably this is so a successful login can still dismiss this screen

Just confirming – is this screen only used when the restore is in-progress?

Yes

If the button to start is on this screen too, we might want to only prevent the user from navigating away after the button is pressed

The button is on a different screen and also has some async action prior to navigating to this screen where we should prevent user from navigating away, I handled this in the next diff in the stack - D14397.

native/account/restore-backup-screen.react.js
54–56 ↗(On Diff #47232)

Why do we have to filter out some actions? In the linked code from the registration flow, we don't have to do any filtering.

We do, see this line.

Presumably this is so a successful login can still dismiss this screen

Exactly, according to D11867

This revision was landed with ongoing or failed builds.Feb 25 2025, 4:34 AM
This revision was automatically updated to reflect the committed changes.