Triggered auto assignment to @adelekennedy (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details. Please add this bug to a GH project, as outlined in the SO.

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

Triggered auto assignment to @dangrous (DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.

Proposal

Please re-state the problem that we are trying to solve in this issue.

User can open avatar edit modal when the app is loading. Remove photo option is shown even when the account has default avatar when the app is loading.

What is the root cause of that problem?

this is new feature

What changes do you think we should make in order to solve the problem?

We will disable this avatar while the app is loading in here

    disabled={isAvatarCropModalOpen || (disabled && !enablePreview) || isLoadingApp}

with

    const [isLoadingApp] = useOnyx(ONYXKEYS.IS_LOADING_APP);

What alternative solutions did you explore? (Optional)

Proposal

Please re-state the problem that we are trying to solve in this issue.

We can edit the avatar while the app is loading.

What is the root cause of that problem?

Before the account switcher PR, the avatar is only shown on the initial settings page and a skeleton will replace it if the app is "loading".

Now, we also show/move the editable avatar on the profile page.

But we never replace it with a skeleton when the app is loading.

What changes do you think we should make in order to solve the problem?

We can have the same skeleton condition from InitialSettingsPage and show the skeleton when satisfied.

{isEmptyObject(currentUserPersonalDetails) || currentUserPersonalDetails.displayName === undefined ? (
    <AvatarSkeleton size={CONST.AVATAR_SIZE.XLARGE} />
) : (
    <AvatarWithImagePicker .../>

We can use the existing AvatarSkeleton, but we need to make some adjustments to the component. Currently, the skeleton has a static size of 28.

1. Accept a size type props. (default to CONST.AVATAR_SIZE.SMALL)
2. Calculate the size using StyleUtils.getAvatarSize and use it on the radius and height

const StyleUtils = useStyleUtils();
const avatarSize = StyleUtils.getAvatarSize(size);
const skeletonCircleRadius = avatarSize / 2;

return (
    <SkeletonViewContentLoader
        animate
        height={avatarSize}

@dangrous this doesn't seem like a deploy blocker to me

Yeah I don't think this needs to block, not a regression just a minor issue with a new feature. But yeah, let's get this fixed soonish!

assigning rushat to this one

@rushatgabhane let us know what you're thinking about this one, thanks!

i guess we should add skeleton for avatar when it is loading

@dangrous, @rushatgabhane, @adelekennedy Whoops! This issue is 2 days overdue. Let's get this updated quick!

That sounds good @rushatgabhane!

@dangrous, @rushatgabhane, @adelekennedy Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!

@rushatgabhane @dangrous how are we doing with this one? I see it's been grouped up with other issues here should we drop the priority of this one?

PR is in C review!

This was deployed to production 9/19, so we can close on 9/26 assuming all goes well. No payment needed on this one since it was a bug from copilot, right?

@dangrous I think that makes sense - all payment for these issues are being grouped together?

yep!