From e707a6d4ed4c953de1c68e533f53a7a5f3805d47 Mon Sep 17 00:00:00 2001
From: Nidhi Kumari <nidhi.kumari@consensys.net>
Date: Fri, 27 Jan 2023 23:56:51 +0530
Subject: [PATCH] updated the previously owned state for nft (#1082)

Fixes
[17206](https://github.com/MetaMask/metamask-extension/issues/17206)

Ideally, when a user previously owned an NFT, and then received the same
one back, we'd put that NFT back into its own group. With the current
implementation, the NFT is always stuck in the Previously Owned
category, even when imported again. This PR is to update the Nft
Controllers to add the NFT back to its own group if we are re-importing
it.
---
 packages/assets-controllers/src/NftController.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/assets-controllers/src/NftController.ts b/packages/assets-controllers/src/NftController.ts
index 285cb5ed6d5..5829db103a0 100644
--- a/packages/assets-controllers/src/NftController.ts
+++ b/packages/assets-controllers/src/NftController.ts
@@ -619,7 +619,7 @@ export class NftController extends BaseController<NftConfig, NftState> {
           nftMetadata,
           existingEntry,
         );
-        if (differentMetadata) {
+        if (differentMetadata || !existingEntry.isCurrentlyOwned) {
           // TODO: Switch to indexToUpdate
           const indexToRemove = nfts.findIndex(
             (nft) =>