with this change, the connect farcaster prompt appears after all the nux tips have been dismissed, instead of simultaneously
Depends on D14446
Paths
| Differential D14488 Authored by varun on Sun, Mar 23, 9:22 AM.
Tags None Referenced Files
Subscribers
Details
Diff Detail
Event TimelineHerald added a subscriber: tomek. · View Herald TranscriptSun, Mar 23, 9:22 AM2025-03-23 09:22:09 (UTC-7) Comment Actions
Harbormaster completed remote builds in B33850: Diff 47578.Wed, Mar 26, 8:13 PM2025-03-26 20:13:51 (UTC-7) Comment Actions Your test plan is super incomplete. Can you please update the test plan to go one-by-one through every scenario we've had to contemplate while working on this? Eg. fresh registration, log in of existing user with Farcaster connection, log in of existing user with no Farcaster connection, existing log-in that hasn't logged out since before the new registration flow (never got prompted to connect Farcaster), etc.
This revision now requires changes to proceed.Wed, Mar 26, 8:51 PM2025-03-26 20:51:50 (UTC-7) Comment Actions make cold start count a per-alert type count instead of a global count, migrations, stagger the connect farcaster and community directory prompts Harbormaster failed remote builds in B33865: Diff 47614!Mon, Mar 31, 3:50 PM2025-03-31 15:50:48 (UTC-7)
Revision Contents
Diff 47578 lib/utils/date-utils.js
lib/utils/farcaster-utils.js
native/components/connect-farcaster-alert-handler.react.js
native/components/display-community-directory-prompt.react.js
|