Web3Auth Error - "Unable to Detect Device Share" React Native

Help - Plug n Play React Native SDK
1

Hi @yashovardhan - as stated in earliar thread, I am describing the problem once again here.

This is an intermittent issue and comes up on fresh login to web3auth. Following is screenshot of iOS device.

image
image640×1278 63.4 KB

Code details.

Packages:
“@web3auth/react-native-sdk”: “3.5.0”
“react-native”: “0.70.5”

const resolvedRedirectUrlForAndroid =
  Constants.appOwnership == AppOwnership.Expo || Constants.appOwnership == AppOwnership.Guest
    ? Linking.createURL("web3auth", {})
    : Linking.createURL("web3auth", { scheme: scheme });

const resolvedRedirectUrl = "loot8auth://openlogin";

const web3auth = new Web3Auth(WebBrowser, {
        clientId,
        network: Constants.expoConfig.extra.ENVIRONMENT == AppEnvironment.PRODUCTION ? OPENLOGIN_NETWORK.CYAN : OPENLOGIN_NETWORK.TESTNET
      });

const info = await web3auth.login({
            redirectUrl: Platform.OS === 'ios' ? resolvedRedirectUrl :  resolvedRedirectUrlForAndroid,
            mfaLevel: "none",
            curve: "secp256k1",
            extraLoginOptions: {
              login_hint: provider == LOGIN_PROVIDER.EMAIL_PASSWORDLESS && loginHint
            },
            loginProvider: provider
          });

Let us know if you need any other detail.

Thanks

2

@yashovardhan - Gentle Reminder about the issue!

3

@web3auth-team - tagging web3 auth team.

4

Hey @keval.shah

As I see your code snippets are looking fine. We have been investigating this problem for a while now, but are unable to reproduce it internally. If you can give us any logs while this error occurs it will be very helpful. Some other developers are facing this as well and we’re unable to reproduce on our end till now.

The error you’re seeing on the screen is a very generic error and can happen due to the cache settings in the browser as well. The real error still lies in the console, which you can find while debugging this in safari in a simulator.

Any how, we’re launching our next version of the SDK in the coming weeks, which should hopefully resolve this issue. Sorry for the delay from our side.

5

Thank you so much @yashovardhan for your response. I will try to capture console logs when I get that error again.
This is intermittent issue, but we have seen it with many users.

6

If you get this error once again, just please refresh the page, and you will see a “!” button on the right hand top corner of the page. Pressing that will reveal the logs of the error. Please feel free to share those logs with us here.

7

Got it. Thank you. I will pass on those details when I encounter that issue again.

8

Hi @yashovardhan and team, we again got this error after long but getting this multiple times in a single device

image
image744×1494 47.4 KB

Also, recently auth approval email for our gmail ids are sent to spam folder, is that a known issue?

9

@keval.shah Thanks for your recent communication.

It seems you might be hitting the email rate limit. You cannot have more than 2 unverified emails per 24 hours. An IP cannot request more than 2 emails per 5 mins.

Could you please provide the console logs from the error page Something went wrong

10

Got it! thanks for the information. We will make sure of that scenario before noting down the error now onwards.
Moreover, going email into spam folder is related to this error? because I was trying on my personal gmail account which worked at first time but email was sent to my Gmail > Spam folder.

11

Potentially, in your tests you can use multiple accounts under the rate limits to avoid the scenario.

Regarding the issue with email going to Spam folder. Is it happening with multiple accounts?

12

Yes @vjgee , it happens with multiple accounts.

13

@keval.shah Our team made some changes and the email should no longer go to Spam folder. Please check.

14

Ok. Thanks @vjgee for solution. We will monitor emails and let you know in case of any issues.

1 Like