This is almost certainly because you're creating a new loadingStatusSelector on every render of this component. We don't do this anywhere else in the codebase... that should've been a strong signal to you that you're doing something wrong, especially in light of the issue you were seeing

When you use a new function like this that you're not familiar with, you need to be aware of what you don't know. You likely haven't read the code, and it appears that you haven't inspected its usage closely in other contexts. That should be a "red flag" to you that something could very likely be wrong with your code. As soon as you see an issue (or even better, BEFORE you see an issue) you should immediately suspect that you're doing something wrong, and start looking closely at existing usages and reading the implementation

By papering over this issue and hacking around it, you've likely introduced a second issue. Ask yourself: if loadingStatus === 'loading' doesn't handle disabling the buttons correctly, then why do you think that very same check will perform for deciding whether to display ActivityIndicator? I strongly suspect it will have the same issue

Typo

I think it would be good to add an exclamation mark

I'm concerned about the following scenario:

1. User opens EmojiAvatarCreation on device A
2. User messes around with it on device A, sets some pending state but DOES NOT save
3. User then opens EmojiAvatarCreation on device B and saves a new avatar
4. User then hits reset on device A. It should reset to the new saved avatar, but instead it resets to the original avatar, which is misleading

I think that we should just have onPressReset reset to the current state in Redux. Then we wouldn't need lastSavedAvatar, and arguably we wouldn't need props.route.params.emojiAvatarInfo either if we instead pass some ID indicating what kind of avatar it is.

It might be somewhat difficult to make the "fetch from Redux" part generic if it has to handles thread and user avatars, which is why I suspect you were using React Navigation params in the first place. This component is in native/profile, so it's not immediately clear to me if you intend on using it for thread avatars too... but if you do, I suspect it might be better to factor out a more generic component that takes a "selection function" prop (that selects the avatar from Redux), and two other components that compose the generic one.

Typo