Web3Auth Not Redirecting After OTP Verification & Stuck in Browser

Help - Plug n Play PnP React Native SDK
1

React Native SDK Version : 8.1.0
Platform : React Native

Issue Description:

After entering the OTP for verification, instead of redirecting back to the app, we are getting stuck in the browser with a loading screen. When we reload the browser screen, we encounter the following error:

Something went wrong. There seems to be some bug in the code. Please contact support to fix this. Init parameters not found. It might be because storage is not available. Please retry the login in a different browser. Used storage method: localStorage

Screenshot_20250225-102704.Chrome
Screenshot_20250225-102704.Chrome1220×2712 79.1 KB

Screenshot_20250225-102736.Chrome
Screenshot_20250225-102736.Chrome1220×2712 160 KB

config
config1110×1318 113 KB

index
index1356×1090 92.8 KB

init
init1320×1550 251 KB

auth-page
auth-page1156×1470 111 KB

2

Hi Himanshu,

Thanks for reaching out! I understand you’re experiencing issues with the Web3Auth SDK for React Native. From what you’ve shared, it seems like the redirect isn’t working after the OTP verification, and you’re seeing an error about initialization parameters not being found.

Here’s what I gathered:

  • SDK: Web3Auth PnP React Native SDK
  • Version: 8.1.0
  • Platform: React Native
  • Error: Stuck after OTP verification, error with Init parameters not found

I see you’ve attached several screenshots, but unfortunately, I can’t view them directly here. It would help if you could ensure your authentication flow configurations are correctly set, particularly around where the parameters are initialized and stored.

In case there’s a caching issue or something specific to a browser, you might wish to clear the browser’s local storage or try using a different browser as the error suggests. Additionally, reviewing your initialization code for any missing parameters could be helpful.

If you haven’t already, double-check the environment where this is occurring and try restarting the device or browser to see if it’s isolated to a specific condition.

The support team will look into this further. Meanwhile, let me know if you need any more information or assistance.

Best,
[Your 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

3

Hey @himanshujain5690174
Can you pass enableLogging as true in Web3Auth constructor and get me some logs via debugging the android device or via Flipper? This isn’t a known bug.

4

Can you share your GitHub so I can invite you? That way, you can access the full codebase and provide better assistance.

image
image1227×248 15.4 KB

5

Hey @himanshujain5690174,

I appreciate you reaching out! Just to clarify, deep-level support where we go through the full codebase is something we offer to our enterprise customers as part of dedicated support.

That said, I’m happy to help if you can share some logs from debugging the device. Since this isn’t a known issue on our side affecting production, getting those logs would help us pinpoint the problem.

For debugging, you can refer to these resources:

  • iOS Debugging Guide: Link
  • Android Debugging Guide: Link

If you’re looking for a more hands-on, dedicated support experience, I’d recommend considering our enterprise plan, where we offer direct assistance via a dedicated Telegram/Slack group.