Kakao, Apple login not working (react-native)

Help - Plug n Play PnP React Native SDK
1

When the app is installed and the user attempts to log in using KakaoTalk or Apple, the following error inevitably occurs the first time. From the second attempt onward, it works normally. There were no activities such as pressing the back button or navigating to other screens during the login process.

This issue matches the symptoms described in the question linked below (no answer appears to have been provided yet). - https://web3auth.io/community/t/react-native-login-apple-failed/5411

I first contacted Auth0 and thoroughly checked the settings on my Auth0 dashboard. They confirmed there were no issues on their end and advised me to contact Web3Auth instead.

IMG_DC17C0222E36-1
IMG_DC17C0222E36-11179×2556 86.5 KB

2

Thank you for providing detailed information about your issue with the PnP React Native SDK and the login problems with Kakao and Apple on the first attempt. I see you’ve also included a screenshot and referenced a related community post.

Here’s a summary of your issue for the support team:

Issue Summary

  • SDK Details: PnP React Native SDK
  • Platform: React Native (mobile)
  • Login Providers Affected: Kakao, Apple
  • Issue: On first login attempt after app installation, login via KakaoTalk or Apple fails with an error. From the second attempt onwards, login works as expected. No navigation or back button is involved during the process.
  • Auth Provider: Auth0 (settings confirmed correct by Auth0 support)
  • Reference: Related Community Post
  • Screenshot Provided: Yes (attached in the original message)

Next Steps / Additional Information Needed

To help the support team investigate further, could you please provide:

  1. SDK Version Number: Which version of the PnP React Native SDK are you using?
  2. Web3Auth Initialisation & Login Code Snippets: If possible, please share the code you use for initializing Web3Auth and triggering the login.
  3. Error Message Details: The screenshot is helpful, but if you have the full error message (in text), please paste it here.
  4. Any Custom Auth Settings: Are you using custom verifiers or any special configuration for Kakao/Apple with Auth0?

Possible Solution / Suggestions

  • This issue may be related to how the SDK handles session or redirect URIs on the first launch. There have been similar reports in the community, and sometimes updating to the latest SDK version or adjusting the redirect URI configuration resolves it.
  • Please review the React Native SDK integration guide to ensure all redirect URIs and deep linking settings are correctly configured.
  • Double-check your Auth0 integration steps with Web3Auth.

Once you provide the additional details, the support team can assist you more efficiently. Thank you for your patience!

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

const ethereumPrivateKeyProviderInstance = new EthereumPrivateKeyProvider({
config: { chainConfig },
});

const web3authInstance = new Web3Auth(WebBrowser, EncryptedStorage, {
clientId: web3AuthConfig.clientId,
redirectUrl: ‘chainwithdev://auth’,
network: web3AuthConfig.network,
privateKeyProvider: ethereumPrivateKeyProviderInstance,
loginConfig: {
line: {
verifier: ‘chainwith-app-dev’,
verifierSubIdentifier: ‘chainwith-dev-line’,
typeOfLogin: ‘line’,
clientId: ‘my client id’,
jwtParameters: {
domain: ‘my domain’,
verifierIdField: ‘email’,
isVerifierIdCaseSensitive: false,
},
},
kakaoCustom: {
verifier: ‘chainwith-app-prod-custom-kakao’,
verifierSubIdentifier: ‘chainwith-app-prod-custom-kakao’,
typeOfLogin: ‘jwt’,
clientId: ‘my clientid’,
jwtParameters: {
domain: ‘https://dev-31zum6u30mrudlmz.us.auth0.com’,
verifierIdField: ‘email’,
isVerifierIdCaseSensitive: false,
connection: ‘Kakao’,
},
},
},
});

await web3authInstance.init();

// handleSignBtn

await web3auth.login({
loginProvider:
type === ‘kakao’ ? ‘kakaoCustom’ :
type === ‘line’ ? LOGIN_PROVIDER.LINE :
type === ‘google’ ? LOGIN_PROVIDER.GOOGLE :
LOGIN_PROVIDER.APPLE,
});

if (web3auth.connected) {
const provider = web3auth.provider;
const idToken = web3auth.userInfo()?.idToken;
} else {
console.log(‘:x: Web3Auth not connected’);
}

4

I have informed our dev team about this issue, they will be looking into it.

1 Like
5

Are you currently working on this?

To be honest, this issue is quite serious from a business perspective. The company is even considering not using Web3Auth if it can’t be resolved, so it’s a major concern for me. I truly hope this can be resolved.

6

any update?

@yashovardhan

7

I still haven’t received a response to this inquiry.
This is an important issue, and I hope it can be resolved quickly.

@maharshi

8

@yashovardhan @maharshi

9

Hey @develop

I see you are an enterprise customer, is there a telegram group created between our teams? This particular issue was fixed a while ago I believe. Sorry for missing the messages here. It will be ideal to connect on telegram directly.