Ended up testing the connect farcaster flow and it works. A couple things worth noting:

1. The connect farcaster bottom sheet appears at the same time as the NUX tips if the user installs the app and logs in. Not sure if this edge case is worth addressing

2. The bottom sheet appears at the same time as the SIWE backup message screen when a SIWE user who doesn't have a backup message yet logs in. This seems unlikely to happen since the backup message generation is now part of the registration flow

Alternately, does this occur for every fresh install login?

Yes, it occurs the first time a user logs in after fresh install

Does it not occur on every single login because the NUX doesn't display on subsequent logins?

In D14444#401312, @ashoat wrote:

Does it not occur on every single login because the NUX doesn't display on subsequent logins?

That's right. When the NUX is displayed, we write to AsyncStorage so that it doesn't appear again for that install

Feels like there are probably ways to dismiss the modal without setting the fid to null here. Ideally we can catch all methods of closing the modal, but if that's really hard, one alternative would just be to set the fid to null as soon as we show the modal.

the onClosed callback gets called by BottomSheet's onChange callback:

const onChange = React.useCallback(
  (index: number) => {
    if (index === -1) {
      onClosed();
    }
  },
  [onClosed],
);

i think this should handle all methods of closing the modal

In D14444#401325, @varun wrote:

Feels like there are probably ways to dismiss the modal without setting the fid to null here. Ideally we can catch all methods of closing the modal, but if that's really hard, one alternative would just be to set the fid to null as soon as we show the modal.

the onClosed callback gets called by BottomSheet's onChange callback:

const onChange = React.useCallback(
  (index: number) => {
    if (index === -1) {
      onClosed();
    }
  },
  [onClosed],
);

i think this should handle all methods of closing the modal

Nice find!! Worth confirming that it works for the hardware back button on Android.

The connect farcaster bottom sheet appears at the same time as the NUX tips if the user installs the app and logs in. Not sure if this edge case is worth addressing

Could probably be addressed in a separate diff. If you remove the DISABLE_CONNECT_FARCASTER_ALERT change from this one, we could land this diff sooner and address the NUX tips appearing at the same time later, and then flip DISABLE_CONNECT_FARCASTER_ALERT after that.