Got Error: Unable to resolve enough promises with using node-sdk

Hello!
I’m trying to implement SFA Node SDK, but get same error “Unable to resolve enough promises.” at node_modules/@toruslabs/torus.js/dist/torusUtils.cjs.js:640:20

  1. errors: (5) [undefined, undefined, undefined, undefined, undefined]
  2. predicate: predicate: ‘invalid result from nodes, threshold number of public key results are not matching’
  3. responses: array of 5 responses with results.keys array(with some data)

Basic flow with custom JWT works well with same verifier and chains

What i do:

  1. create verifier for custom JWT(used the same for basic flow)

  2. get instance of Web3AuthSFA(from @web3auth/single-factor-auth) and init

  3. get JWT from my provider(backend for now), parse it to get id field(sub) and call

    import { Web3Auth } from ‘@web3auth/node-sdk’;
    web3auth.connect({
    verifier: ‘nft-ticket-verifier’,
    verifierId: sub,
    idToken: accessToken,
    });

when i got error

  • SDK Version: “@web3auth/node-sdk”: “^3.2.0”
  • Verifier Details:
    • Verifier Name: nft-ticket-verifier
    • JWKS Endpoint: https://raw.githubusercontent.com/Sotatek-HuynhVu/web3auth-test/main/nft-ticket-jwks.json
    • Sample idToken(JWT): eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6Im5mdC10aWNrZXQifQ.eyJzdWIiOiJuMnpobjkiLCJuYW1lIjoiTW9oYW1tYWQgWWFzaG92YXJkaGFuIE1pc2hyYSIsImVtYWlsIjoidGVzdEBnbWFpbC5jb20iLCJhdWQiOiIyMDI0IiwiaXNzIjoiaHR0cHM6Ly93ZWIzYXV0aC5pbyIsImlhdCI6MTcwNTM3Njg0NywiZXhwIjoxNzA1MzgwNDQ3fQ.GckxqDnfqzPzSKBQQZ98vC9O55f4yIg7RJZm2N-rk85TmU0uhkeDEUPbJFb4FEvdbSF-K8p4ucmEh0gNLLCsnXwelxDtmbRBv8Do-79Z86DOYXsAd3-HFTkWWwNRmV6-oDQCV9msvzyKRcoK5G-JvceKpklFnCHJFNojt9u7mYGxHnoi9w5Xv-Q5GVjLqcSxdbl1ng4pgIbrKU5ZLcf4n_NzsnGGVo3A8GtBE8GvUJRrjuEovW3x1qsQlglOER_euT8qmRjv3_54iaQj5Lc_S15RTk_tou1tgyZiQ2DCnMkBFkcuyABMjtYGOeA3IlByJv8WSyWnTTW-ebwC-b64dw

Please help me!

@huynh.vu Welcome Aboard!

Your issue has been forwarded to our Dev team and we will get back at the earliest with an update.

Thanks, please notify me when this issue is resolved :pray:

@huynh.vu Our team mentioned this issue has been resolved and you should not have any further issues.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.