[Archive] Apple Login Fails with Error: "Oops! Something went wrong"

Embedded Wallets (Web3Auth)
1

:classical_building: Archived Content from Web3Auth Community

This topic was originally posted by yurii.o on 7/14/2025.
This content has been migrated from our previous community forum to preserve valuable discussions.

Details:

Issue Description:

We are integrating Web3Auth in our React Native application. On iOS devices, we’ve encountered a recurring issue where users are unable to log in with Apple on their very first attempt. This issue occurs only on the initial attempt and only on iOS.

After some investigation, we found that disabling “Prevent Cross-Site Tracking” in device settings can help in some cases. However, this workaround is not practical for end users.

Initialization:

import Web3Auth, { LOGIN_PROVIDER } from '@web3auth/react-native-sdk';
import { WEB3AUTH_NETWORK, getEvmChainConfig } from '@web3auth/base';
import * as WebBrowser from '@toruslabs/react-native-web-browser';
import { EthereumPrivateKeyProvider } from '@web3auth/ethereum-provider';

const clientId = <KEY>;

const newChainConfig = getEvmChainConfig(0x01, clientId)!;


const privateKeyProvider = new EthereumPrivateKeyProvider({

config: { chainConfig: newChainConfig },

});


export const web3auth = new Web3Auth(WebBrowser, EncryptedStorage, {

clientId,

redirectUrl,

network: WEB3AUTH_NETWORK.SAPPHIRE_MAINNET,

privateKeyProvider,

});

Login Flow:

 await web3auth.login({
   loginProvider,
   redirectUrl: redirectUrl
 });

Additional Observations:

We switched to using @swan-io/react-native-browser as the in-app browser module, which improved the situation for most users.

However, the login process can still take up to 30 seconds to complete. This delay seems to be related to the Web3Auth server response time.

Although switching the browser has reduced visible errors, there is no guarantee that this solution will work reliably for all users without a clear understanding of the underlying issue.

Questions:

  • It seems like this issue has existed for a few years. Are there any proven, 100% reliable solutions available?
  • Is this a known limitation of Web3Auth + Apple login on iOS?
  • Could it be related to in-app browser handling or deep linking?

Any advice or insights would be greatly appreciated. Thank you!

3

I solved this problem by adding https to Info.plist:

	<key>LSApplicationQueriesSchemes</key>
	<array>
        ...
		<string>https</string>
	</array>

My Issue

1 Like
4

Thanks a lot for letting us know the fix for this issue. We will refer to this for future references as well.

Thanks for contributing to the community :raising_hands: