I am currently using Web3Auth in my application, and while login and signup functionalities are working without issues, I am facing challenges with the following:
Fetching the private key after successful authentication.
Executing blockchain calls that rely on the private key.
Problem Details:
Issue: An abnormal closure error occurs when attempting to fetch the private key using Web3Auth’s API/method.
As a result, blockchain-related operations are failing due to the unavailability of the private key.
The private key fetching mechanism and blockchain calls were working previously, but the issue surfaced recently. No significant changes were made to the integration that might explain this behavior.
I would appreciate your guidance on resolving this issue. If logs or additional implementation details are required, please let me know.
Thank you for reaching out! It sounds like you’re encountering some challenging issues with fetching the private key and executing blockchain calls. Let’s gather the necessary details to assist you better.
Here’s what we have so far:
SDK Details: Plug n Play
Issue: Abnormal closure when fetching the private key after successful authentication.
To help resolve this, could you please provide us with the following additional information:
SDK Version Number: What version of the Plug n Play SDK are you using?
Platform: Are you implementing this in a web, mobile, or other environment?
Code Snippets: If possible, please share the initialization and login code snippets you are using for Web3Auth.
Browser Console Screenshots: Any errors or logs shown in the browser console when this issue occurs can be very insightful.
Verifier Name & Method of Login: If your implementation uses a custom authentication provider, sharing these details would help us pinpoint the issue.
Feel free to attach any links or images that might help clarify your situation as well.
Looking forward to your response so we can get to the bottom of this!
Thank you!
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.