Page MenuHomePhabricator

[lib] Disconnect FID when another device disconnects it
ClosedPublic

Authored by ashoat on Tue, Oct 15, 11:27 AM.
Tags
None
Referenced Files
F2982448: D13716.id45205.diff
Wed, Oct 16, 3:29 AM
F2982165: D13716.diff
Wed, Oct 16, 1:53 AM
F2979251: D13716.id45205.diff
Tue, Oct 15, 3:35 PM
F2979250: D13716.id45201.diff
Tue, Oct 15, 3:35 PM
F2979207: D13716.id.diff
Tue, Oct 15, 3:34 PM
F2979195: D13716.diff
Tue, Oct 15, 3:34 PM
Subscribers

Details

Summary

This addresses ENG-9684.

Depends on D13715

Test Plan
  1. I started with a test account that has been connected to an FID on staging
  2. I opened up a mobile app and a web app logged in as this user
  3. I disconnected the FID on mobile
  4. I refreshed the web app. Prior to these changes, refreshing would not cause the FID to be disconnected on web. After these changes, it does. I was able to check if the FID was connected by seeing if the “Tag Farcaster channel” option appeared for a community that the user is an admin of
  5. On mobile, I then reconnected the FID on staging following these instructions
  6. After reconnecting on mobile, I refreshed the web app and confirmed that the FID was reconnected on web too
  7. Then I added an artificial delay to the findUserIdentities RPC to force a timeout. I refreshed the web app and confirmed that the FID was *not* disconnected

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage

Event Timeline

lib/components/farcaster-data-handler.react.js
39–40

Note that findUserIdentities is unchanged here

ashoat published this revision for review.Tue, Oct 15, 11:28 AM
This revision is now accepted and ready to land.Tue, Oct 15, 11:32 AM