Merge pull request #2041 from ChainSafe/fix/has-mnemonic-share-check

Has mnemonic share check

packages/files-ui/src/Contexts/ThresholdKeyContext.tsx

@@ -157,8 +157,10 @@ const ThresholdKeyProvider = ({ children, network = "mainnet", enableLogging = f
     ...bs,
     ...bowser.parse(bs.userAgent)
   } as BrowserShare)), [parsedShares])
-  const hasMnemonicShare = useMemo(() => (keyDetails && (keyDetails.totalShares - parsedShares.length > 1)) || false,
-    [keyDetails, parsedShares.length])
+
+  const hasMnemonicShare = useMemo(() => parsedShares.filter((s) => s.module === SHARE_SERIALIZATION_MODULE_NAME).length > 0,
+    [parsedShares])
+
   const hasPasswordShare = useMemo(() => parsedShares.filter((s) => s.module === SECURITY_QUESTIONS_MODULE_NAME).length > 0,
     [parsedShares])
 
@@ -254,7 +256,6 @@ const ThresholdKeyProvider = ({ children, network = "mainnet", enableLogging = f
         // cached may be stale, resulting in a failure to reconstruct the key. This is 
         // identified through the nonce. Manually refreshing the metadata cache solves this problem
         if (error.message.includes("nonce")) {
-          // await TKeySdk._syncShareMetadata()
           const { privKey } = await TKeySdk.reconstructKey(false)
           const privKeyString = privKey.toString("hex")
           if (privKeyString.length < 64) {
@@ -626,6 +627,10 @@ const ThresholdKeyProvider = ({ children, network = "mainnet", enableLogging = f
         requiredShareStore.share.share,
         "mnemonic"
       )) as string
+      await TKeySdk.addShareDescription(
+        shareCreated.newShareIndex.toString("hex"),
+        JSON.stringify({ module: SHARE_SERIALIZATION_MODULE_NAME }),
+        true)
       const keyDetails = await TKeySdk.getKeyDetails()
       setKeyDetails(keyDetails)
       return result