Page MenuHomePhabricator

[lib] Invalidate UserIdentityCache when changing FID
ClosedPublic

Authored by ashoat on Oct 16 2024, 8:52 PM.
Tags
None
Referenced Files
F3523295: D13737.id45264.diff
Mon, Dec 23, 8:56 AM
F3522076: D13737.id45239.diff
Mon, Dec 23, 5:41 AM
F3521024: D13737.diff
Mon, Dec 23, 1:59 AM
F3519547: D13737.id45264.diff
Sun, Dec 22, 10:23 PM
F3519546: D13737.id45239.diff
Sun, Dec 22, 10:23 PM
F3519531: D13737.id.diff
Sun, Dec 22, 10:23 PM
F3519513: D13737.diff
Sun, Dec 22, 10:23 PM
Unknown Object (File)
Wed, Nov 27, 6:49 PM
Subscribers

Details

Summary

When we change the current user's FID, we should invalidate their entry in the UserIdentityCache. Otherwise, FarcasterDataHandler will continue to use the old value, and can end up wiping the FID if handleCurrentUserFID is run again before the app is killed (this can happen if the app is backgrounded/foregrounded).

This addresses ENG-9704.

Depends on D13736

Test Plan
  1. Open mobile app when Farcaster account not linked
  2. Link Farcaster account
  3. Background the app
  4. Foreground the app
  5. Confirm that the Farcaster account is not unlinked

Diff Detail

Repository
rCOMM Comm
Lint
No Lint Coverage
Unit
No Test Coverage