# \[Archive\] Web3Auth Error - "Unable to Detect Device Share" React Native

**URL:** <https://builder.metamask.io/t/archive-web3auth-error-unable-to-detect-device-share-react-native/1813>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [April 12, 2023, 10:49am UTC](https://builder.metamask.io/t/archive-web3auth-error-unable-to-detect-device-share-react-native/1813 "2023-04-12T10:49:12Z")\
**Posts on this page:** 14\
**Page:** 1

<div class="post-metadata">

**Author:** ![keval.shah](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@keval.shah](https://builder.metamask.io/u/keval.shah)\
**Post date:** [April 12, 2023, 10:49am UTC](https://builder.metamask.io/t/archive-web3auth-error-unable-to-detect-device-share-react-native/1813/1 "2023-04-12T10:49:12Z")

</div>

> **🏛 Archived Content from Web3Auth Community**
> 
> This topic was originally posted by **keval.shah** on 4/12/2023.  
> This content has been migrated from our previous community forum to preserve valuable discussions.

* * *

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](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/a/a52242f340bf8317287fa85d9820549343d2c1b0.jpeg)
image640×1278 63.4 KB
](https://community.web3auth.io/community/community/uploads/default/original/1X/438a720630cb8582cbe389d3a2be42659cee5080.jpeg "image")

Code details.

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

```auto
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
});

```

Let us know if you need any other detail.

Thanks

---

<div class="post-metadata">

**Author:** ![keval.shah](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@keval.shah](https://builder.metamask.io/u/keval.shah)\
**Post date:** [May 3, 2023, 1:11pm UTC](https://builder.metamask.io/t/archive-web3auth-error-unable-to-detect-device-share-react-native/1813/2 "2023-05-03T13:11:15Z")

</div>

@yashovardhan - Gentle Reminder about the issue!

---

<div class="post-metadata">

**Author:** ![keval.shah](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@keval.shah](https://builder.metamask.io/u/keval.shah)\
**Post date:** [May 18, 2023, 4:15am UTC](https://builder.metamask.io/t/archive-web3auth-error-unable-to-detect-device-share-react-native/1813/3 "2023-05-18T04:15:23Z")

</div>

[@web3auth-team](https://builder.metamask.io/groups/web3auth-team) - tagging web3 auth team.

---

<div class="post-metadata">

**Author:** ![yashovardhan](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/yashovardhan/32/1526_2.png) [@yashovardhan](https://builder.metamask.io/u/yashovardhan)\
**Post date:** [May 24, 2023, 7:56am UTC](https://builder.metamask.io/t/archive-web3auth-error-unable-to-detect-device-share-react-native/1813/4 "2023-05-24T07:56:18Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![keval.shah](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@keval.shah](https://builder.metamask.io/u/keval.shah)\
**Post date:** [May 24, 2023, 8:45am UTC](https://builder.metamask.io/t/archive-web3auth-error-unable-to-detect-device-share-react-native/1813/5 "2023-05-24T08:45:10Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![yashovardhan](https://yyz1.discourse-cdn.com/flex011/user_avatar/builder.metamask.io/yashovardhan/32/1526_2.png) [@yashovardhan](https://builder.metamask.io/u/yashovardhan)\
**Post date:** [May 30, 2023, 2:38pm UTC](https://builder.metamask.io/t/archive-web3auth-error-unable-to-detect-device-share-react-native/1813/6 "2023-05-30T14:38:49Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![keval.shah](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@keval.shah](https://builder.metamask.io/u/keval.shah)\
**Post date:** [May 30, 2023, 3:21pm UTC](https://builder.metamask.io/t/archive-web3auth-error-unable-to-detect-device-share-react-native/1813/7 "2023-05-30T15:21:47Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![keval.shah](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@keval.shah](https://builder.metamask.io/u/keval.shah)\
**Post date:** [August 11, 2023, 5:41pm UTC](https://builder.metamask.io/t/archive-web3auth-error-unable-to-detect-device-share-react-native/1813/8 "2023-08-11T17:41:50Z")

</div>

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

[![image](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/a/a4591769083d30698874e07a655037db8d29388e.jpeg)
image744×1494 47.4 KB
](https://web3auth.io/community/uploads/default/original/2X/5/5740fa616abc70423e7851630be1cacb477c2632.jpeg "image")
  
Also, recently auth approval email for our gmail ids are sent to spam folder, is that a known issue?

---

<div class="post-metadata">

**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\
**Post date:** [August 12, 2023, 4:33am UTC](https://builder.metamask.io/t/archive-web3auth-error-unable-to-detect-device-share-react-native/1813/9 "2023-08-12T04:33:52Z")

</div>

@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`

---

<div class="post-metadata">

**Author:** ![keval.shah](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@keval.shah](https://builder.metamask.io/u/keval.shah)\
**Post date:** [August 12, 2023, 4:48am UTC](https://builder.metamask.io/t/archive-web3auth-error-unable-to-detect-device-share-react-native/1813/10 "2023-08-12T04:48:10Z")

</div>

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.

---

<div class="post-metadata">

**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\
**Post date:** [August 12, 2023, 5:15am UTC](https://builder.metamask.io/t/archive-web3auth-error-unable-to-detect-device-share-react-native/1813/11 "2023-08-12T05:15:44Z")

</div>

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?

---

<div class="post-metadata">

**Author:** ![keval.shah](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@keval.shah](https://builder.metamask.io/u/keval.shah)\
**Post date:** [August 12, 2023, 9:24am UTC](https://builder.metamask.io/t/archive-web3auth-error-unable-to-detect-device-share-react-native/1813/12 "2023-08-12T09:24:38Z")

</div>

Yes @vjgee , it happens with multiple accounts.

---

<div class="post-metadata">

**Author:** ![vjgee](https://avatars.discourse-cdn.com/v4/letter/v/b5e925/32.png) [@vjgee](https://builder.metamask.io/u/vjgee)\
**Post date:** [September 3, 2023, 12:12am UTC](https://builder.metamask.io/t/archive-web3auth-error-unable-to-detect-device-share-react-native/1813/13 "2023-09-03T00:12:30Z")

</div>

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

---

<div class="post-metadata">

**Author:** ![keval.shah](https://avatars.discourse-cdn.com/v4/letter/k/50afbb/32.png) [@keval.shah](https://builder.metamask.io/u/keval.shah)\
**Post date:** [September 3, 2023, 4:21am UTC](https://builder.metamask.io/t/archive-web3auth-error-unable-to-detect-device-share-react-native/1813/14 "2023-09-03T04:21:29Z")

</div>

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