Page MenuHomePhabricator

[keyserver][lib][native] Introduce siweNonceExpired
ClosedPublic

Authored by ashoat on Sun, May 12, 7:31 PM.
Tags
None
Referenced Files
Unknown Object (File)
Sat, May 25, 3:25 PM
Unknown Object (File)
Thu, May 23, 5:05 PM
Unknown Object (File)
Wed, May 22, 2:00 PM
Unknown Object (File)
Wed, May 22, 12:14 PM
Unknown Object (File)
Tue, May 21, 11:00 AM
Unknown Object (File)
Mon, May 20, 8:24 PM
Unknown Object (File)
Sun, May 19, 12:03 PM
Unknown Object (File)
Fri, May 17, 4:06 PM
Subscribers

Details

Summary

This function will be used to check if a SIWE nonce has expired during the new registration flow on native.

Would normally put @varun on the review here, but going to ask @inka instead because he is out.

Depends on D12005

Test Plan

I tested (or will test) this diff stack as follows:

  1. Be in a multi-keyserver environment, testing SIWE with iOS simulator
  2. Do a SIWE and then wait 2 minutes to let the nonce expire in the following screens:
    • FullscreenSIWEPanel for an account that doesn't exist yet when the new registration flow is disabled
    • FullscreenSIWEPanel for an account that doesn't exist yet when the new registration flow is enabled
    • FullscreenSIWEPanel for an account that does exist
    • New registration flow for an account that doesn't exist yet (RegistrationTerms)
    • New registration flow for an account that does exist (ExistingEthereumAccount)
  3. Make sure there are no duplicate Alerts, that in all cases an Alert is shown, and that the "back" action activates when the user confirms the Alert

Diff Detail

Repository
rCOMM Comm
Lint
Lint Not Applicable
Unit
Tests Not Applicable