Remove button is still present even after the Email account is removed.

[sandhiyakavi]

Description:
Remove button is still present even after the Email account is removed.

bandicam.2021-11-01.17-05-05-002.mp4

[maxceem]

@mahidulalvi-bonic would you like to handle this issue?

[ghost]

@maxceem, yes, when do you need it?

[maxceem]

@mahidulalvi-bonic preferable within 24 hours. But 48 would be also fine for this one.

[ghost]

Okay, should be done in 24. Thanks.

[ghost]

Hi @maxceem, I couldn't reproduce the issue using a Gmail & an Exchange account. From the video, it seems the screen still works like it used to before I worked on the delete functionality. And I also saw new changes in the dev branch, is it possible this is a regression?

I tried with dev branch of taas-app & taas-apis.

[maxceem]

hi @mahidulalvi-bonic I'm not sure if this is regression issue or existent issue which started showing up.

Did you try this on DEV https://platform.topcoder-dev.com/taas/myteams/16786/positions/e7c0d8c0-3e88-46ab-babf-55699bc7a8e6/candidates/interviews without running it locally?

I can see some warning in browser console which might be related:
react-dom.development.js:82 Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in a useEffect cleanup function. in Ju (created by Xd)

[ghost]

@maxceem, I just tried in dev with an Exchange account in the URL you gave above. Couldn't reproduce the issue.

[ghost]

I did try in incognito, could it be that you have an older version of the app installed?

[maxceem]

could it be that you have an older version of the app installed?

Not sure which app you mean, when we use link https://platform.topcoder-dev.com/taas/myteams/16786/positions/e7c0d8c0-3e88-46ab-babf-55699bc7a8e6/candidates/interviews we (I mean you and me) use the same version of TaaS App. Strange that it happens to me, but not to you.

If you cannot reproduce this issue, I guess you might leave it as I don't have other ideas why it is reproducible for me, but not for you.

[ghost]

Here is a recording how I saw

Screencast.2021-11-04.05.06.29.mp4

[ghost]

It could be a cached version of the web app.. Maybe try deleting all app data & cache from application tab in dev tools?

[maxceem]

It seems that for me it also doesn't happen every time. I tried it one more time and it worked good this time (even without cleaning cache), though I could still see warning in the browser console:

Warning: Can't perform a React state update on an unmounted component. This is a no-op, but it indicates a memory leak in your application. To fix, cancel all subscriptions and asynchronous tasks in a useEffect cleanup function.
    in Ju (created by Xd)

[ghost]

@maxceem, it would be great if you could make a short video of it, with the console and network tabs shown in dev tools. I still couldn't reproduce it.

[maxceem]

@mahidulalvi-bonic unassigning you for now as I also cannot reproduce it now.

@sdgun could you please try one more time? It seems that this issue has been fixed by fixing some other issue.

[sdgun]

@maxceem Tried with few users, this is not reproduced.

[maxceem]

Ok marking it as passing QA for now, but feel free to fail it again if you see this issue happen again.