New wallets generated

[tyler]

I have tried asking for a call for months now with the Web3Auth team, to no avail.

I allow several social logins, and only with twitter do users receive new wallets, effectively losing their funds which I’ve had to refund. Over $10K. I can’t see it being an issue on my end as only for Twitter does this problem occur for a small subset of users.

Searching the forums I see other posts that seem to be unresolved.

I am asking for Web3Auth to set up a call with me and your development team to debug with my devs, this week. If I can’t get on a call with you this week, I will move away from Web3Auth to another provider, write about this experience on Twitter and make sure I never recommend Web3Auth to other teams.

It is insane that after months of trying to set up a call, no one at Web3Auth sees the urgency in users losing access to their funds.

[w3abot]

Hi @time,

I’m sorry to hear about the issues you’re facing with Twitter logins and I understand the urgency given the financial impact and user experience concerns.

For us to assist you better, could you please provide the following details:

• Web3Auth Initialisation & Login Code Snippets: This will help us identify if there’s any specific issue during the setup process.
• Browser Console Screenshots: If there are any errors or warnings in the console, these might provide clues about the problem.

It’s odd that the issue occurs only for Twitter logins while other social logins work fine. This might be specific to the Twitter verifier configuration or how Twitter manages user sessions.

As for setting up a call, I’ll escalate this to our support team and ensure they get in touch with you promptly. We aim to resolve issues like this swiftly and effectively.

Thanks for raising your concern. Someone from our team will reach out to you for further assistance.

---

This response was generated by the Web3Auth Bot and a person from the Web3Auth team will come and give answer to your query as well.

[tyler]

Snippets:

const web3auth = new Web3Auth({
clientId: web3AuthClientId,
web3AuthNetwork: WEB3AUTH_NETWORK.SAPPHIRE_MAINNET,
privateKeyProvider,
uiConfig: {
appName: “X”,
loginMethodsOrder: [“google”, “twitter”, “discord”, “apple”],
},
})

const modalConfig = {
[WALLET_ADAPTERS.OPENLOGIN]: {
label: “openlogin”,
loginMethods: {
// google: { showOnModal: false },
facebook: { name: “facebook”, showOnModal: false },
// twitter: { showOnModal: false },
reddit: { name: “reddit”, showOnModal: false },
// discord: { showOnModal: false },
twitch: { name: “twitch”, showOnModal: false },
// apple: { showOnModal: false },
line: { name: “line”, showOnModal: false },
github: { name: “github”, showOnModal: false },
kakao: { name: “kakao”, showOnModal: false },
linkedin: { name: “linkedIn”, showOnModal: false },
weibo: { name: “weibo”, showOnModal: false },
wechat: { name: “wechat”, showOnModal: false },
email_passwordless: { name: “email”, showOnModal: false },
farcaster: { name: “farcaster”, showOnModal: false },
},
},
}

export const wagmiConfig = createConfig({
chains: [base],
transports: {
[base.id]: http(process.env.BASE_RPC_URL),
},
connectors: [Web3AuthConnector({ web3AuthInstance: web3auth, modalConfig })],
})

As I said in my first message (and others in the forum) our code doesn’t matter because Web3Auth works fine for other social providers. It’s only for Twitter that this issue occurs. This means it’s likely an issue on your end.

[yashovardhan]

Sorry for your experience. Please schedule a call with me here: https://calendar.app.google/a2KZR6FQEtmS2SkSA