Unable to release lock lock cannot be released from storage layer status code

[le.van.thanh.line]

tKey.serviceProvider.postboxKey = new BN(boxKey, 16);
    await tKey.initialize();
    const { shareDescriptions } = tKey.getKeyDetails();
    let privKey: BN;
    if (shareDescriptions) {
      await (tKey.modules
        .securityQuestions as SecurityQuestionsModule).inputShareFromSecurityQuestions(
        password
      );

      const reconstructKey = await tKey.reconstructKey();
      privKey = reconstructKey.privKey;
    } else {
      const initializeNewKey = await tKey._initializeNewKey({
        initializeModules: true,
      });

      await (tKey.modules
        .securityQuestions as SecurityQuestionsModule).generateNewShareWithSecurityQuestions(
        password,
        QUESTIONS
      );
      privKey = initializeNewKey.privKey;
    }
    if (!privKey) {
      throw new Error("reconstructKey null");
    }
  
    const newShareKey = await tKey.generateNewShare();

At step generateNewShare I received the error Unable to release lock lock cannot be released from storage layer status code

I see 3 API calls and bulk_set_stream api sending data up to 8MB. Then call releaseLock to receive status = 2.

How to solve this?

[vjgee]

@le.van.thanh.line Thanks for your patience.

Your issue has been forwarded to our Dev team and we will get back with further updates.

[le.van.thanh.line]

Please check it soon, it happens in our release environment, users can’t login :((

[vjgee]

Absolutely! Could you share your Dapp URL as well so we can check? I’ve already flagged this.

[le.van.thanh.line]

I checked today and the data sent was up to 11MB.
I will send you boxKey, is that okay?

[vjgee]

Can you please check your device system time where you get this error to be correct and set to automatic?

[le.van.thanh.line]

It was correct. It only happens on some accounts. After we create multiple ShareA

[vjgee]

Ok, I am connecting with one of our Devs and will provide an update in the next hour.

Apologies for the inconvenience and appreciate for your patience while we get this resolved.

Can you share your Dapp URL? I will remove it immediately if you don’t want to share it publicly.

[le.van.thanh.line]

@le.van.thanh.line

boxKey

Sorry, we currently do not want to share the Dapp URL. I can share with you the boxKey for the error account

[vjgee]

I have sent you a secure message. Please navigate to the left hand side Menu . Scroll down to find Messages > Inbox and you can share the details securely.

[vjgee]

Our team are working on the issue and will provide constant updates on the progress.

[vjgee]

Our team are putting a fix in place for the issue and will let you know once compete.

Thanks for your patience.

[vjgee]

@le.van.thanh.line Thanks for your continued patience.

Our team mentioned they have fixed this issue and any new users should not face any problem going forward.

[le.van.thanh.line]

Is there any way to prevent old accounts from slowing down?

[yoonyoul]

@vjgee I appreciate if you check the last question about slowing down to get shareA because of big size of metadata.

and please let us know if there is any way to reduce size of the metadata or prevent metadata getting bigger.

[vjgee]

Although you can create as many shares as you want, we recommend you create no more than a total of 6 shares, including your device shares and recovery shares. This is because the more shares you create, it increases the size of the tKey state, which can cause performance issues in the frontend and can slow down the login process. Ideally, you should create 2 recovery shares and ask the user for their trusted devices and only store the device share on them.