Page MenuHomePhabricator

[landing] Reset messageSentRef.current on error
ClosedPublic

Authored by ashoat on Wed, Oct 2, 8:40 PM.
Tags
None
Referenced Files
F2936473: D13581.diff
Thu, Oct 10, 11:12 AM
Unknown Object (File)
Sat, Oct 5, 10:56 PM
Unknown Object (File)
Thu, Oct 3, 5:29 AM
Unknown Object (File)
Thu, Oct 3, 4:56 AM
Unknown Object (File)
Thu, Oct 3, 4:42 AM
Unknown Object (File)
Thu, Oct 3, 4:42 AM
Unknown Object (File)
Thu, Oct 3, 4:42 AM
Unknown Object (File)
Thu, Oct 3, 4:41 AM
Subscribers

Details

Summary

Some folks reported issues with this flow earlier today. The reports came in within a single hour period, so I suspect transient network issues.

I spent some time looking at the code here that handles talking to the relay server, and one potential risk here is that if there's an error after the URL redirect occurs, we'll never retry that step. Probably a good idea to reset this, so that if a retry is necessitated after a URL redirect, we can retry the process from the start (including redoing the URL redirect).

Depends on D13580

Test Plan

I tested this one the same as the previous two, which is to say I followed this doc on Notion for both physical iOS and Android devices

Ideally I'd test the isError state here, but it would be really expensive since I'd need to patch @farcaster/auth-kit to force isError, but that package distributes transpiled source

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

This revision was not accepted when it landed; it landed in state Draft.Wed, Oct 2, 8:43 PM
This revision was landed with ongoing or failed builds.
This revision was automatically updated to reflect the committed changes.