Consistently empty nonce_data from specific node in SFA (Android)

Help - Core-Kit SFA Android SDK
1

Hi Web3Auth team,

We’re using Single Factor Auth (SFA) in our Android app (Kotlin) and encountering an issue where certain Torus nodes (e.g., node_index “1” to “4”, random) consistently return an empty nonce_data field during key retrieval. This results in key reconstruction or signing failures, even after retrying multiple times.

Notably, this issue only occurs during the first call to connect(). Subsequent attempts (even after a short delay) seem to work as expected, which suggests that some nodes may be delayed in generating pubNonce during the initial request.

Details:

  • Verifier: wm-firebase
  • Verifier ID: D2HCemKw9mXJiBLy3qIDeMU2N303
  • Affected node_index: 1~4 (random)
  • SDK: Android (latest)
  • is_new_key: true
  • Error: nonce_data is empty (nonce, pubNonce.x, pubNonce.y are “”)

This has been observed repeatedly. Could you help check the nodes’ state or regenerate the pubNonce for that user to ensure reliability on first connection?

Thanks,
develicit

2

Hello 전승일,

Thank you for reaching out and providing detailed information about the issue you’re encountering with the Single Factor Auth (SFA) on Android. I understand that you’re facing problems with a specific Torus node consistently returning empty nonce_data, which is affecting key reconstruction and signing.

You’ve already included essential details such as:

  • SDK Details: SFA Android SDK
  • Platform: Android (latest)
  • Verifier: wm-firebase
  • Verifier ID: D2HCemKw9mXJiBLy3qIDeMU2N303
  • Affected node_index: 1

I recommend checking the following:

  • Ensure there are no network issues affecting communication with the node.
  • Confirm that the app is using the latest version of the Web3Auth SDK and there are no pending updates that could resolve this issue.

For a resolution, I’d suggest reviewing the Web3Auth documentation on handling public nonce issues here since it might include information about regenerating pubNonce.

I’ve highlighted the issue to the support team, and they’ll look into the node’s state as well. Thank you for your patience and kindly let us know if there are any more details you’d like to share!

Best,
[Your Name or Personalized Bot Name]

Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.

Additionally, we would recommend you to join our biweekly Office Hours to get this resolved even faster. Web3Auth Developer Office Hours