[Archive] Having LOCAL STORAGE NOT DETECTED error

[jo11]

Archived Content from Web3Auth Community

This topic was originally posted by jo11 on 12/2/2024.
This content has been migrated from our previous community forum to preserve valuable discussions.

---

Some of our users are reporting this issue while signing up with Web3Auth.
Here is detailed information

• SDK Version: ^3.5.0
• Platform: iOS 18.1
• React native version: 0.71.10
• Node version: 18.18.2

Here is the code snippet

const scheme = '......';
const resolvedRedirectUrl = `${scheme}://auth`;
const clientId = '.............';
const auth = new Web3Auth(WebBrowser, {
  clientId,
  network: OPENLOGIN_NETWORK.MAINNET,
});
export const hadleIconLogin = async (

id: string,

email?: string,

): Promise<any> => {

let state = null;

try {

if (id === ‘apple’) {

state = await auth.login({

loginProvider: LOGIN_PROVIDER.APPLE,

redirectUrl: resolvedRedirectUrl,

mfaLevel: MFA_LEVELS.NONE,

});

}

23b55666-4063-46ef-8bd7-5efb6d9bce8d1179×2556 67.4 KB

[w3abot]

Hi Jo! Thanks for reaching out. I see you’re experiencing a “LOCAL STORAGE NOT DETECTED” error with the PnP React Native SDK while some users are trying to sign up with Web3Auth.

Here are the details I’ve gathered for the support team:

• SDK Details: PnP React Native SDK
• SDK Version: ^3.5.0
• Platform: iOS 18.1
• React Native Version: 0.71.10
• Node Version: 18.18.2

Code Snippet:

const scheme = '......';
const resolvedRedirectUrl = `${scheme}://auth`;
const clientId = '.............';
const auth = new Web3Auth(WebBrowser, {
  clientId,
  network: OPENLOGIN_NETWORK.MAINNET,
});
export const hadleIconLogin = async (

id: string,

email?: string,

): Promise<any> => {

let state = null;

try {

if (id === ‘apple’) {

state = await auth.login({

loginProvider: LOGIN_PROVIDER.APPLE,

redirectUrl: resolvedRedirectUrl,

mfaLevel: MFA_LEVELS.NONE,

});

}

Suggested Checklist:

1. Web3Auth Initialization Code: The initialization looks good, but ensure the WebBrowser is correctly set up.
2. Browser Console Screenshots: If you have any Console Error screenshots, those can help diagnose further.
3. Custom Authentication: Please clarify if this issue occurs with a specific login provider or all of them.

Could you check if you have any related screenshots or links that might provide more context? The support team will assist you better with that information.

Feel free to reach out if you have any more questions or need further assistance!

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.

[jo11]

Hi Support Team
Any feedbacks or insights on this issue yet?

[jo11]

This is the showcase video of the issue from my users.

[yashovardhan]

Hey @jo11

Sorry for the delay in reply, it looks like you are on a very old version of Web3Auth, which is causing this issue. We had deprecated this version a while back. You can refer to this announcement, back in July Important Update: Deprecation of Older Web3Auth PnP SDK Versions

Since the version was not maintained for a while, it might have caused issues recently. I’d request you to please update your web3auth version, which should ideally solve the issue.