Following up on this topic, we haven’t identified the root cause yet. Could you please check using the Firebase UID 54gXma2B7FRDLuLNTryNPc9rRCJ3
?
Thanks for following up, Felipe! I see you’re referencing the Plug n Play SDK and continuing the discussion from your previous topic about the wallet address change issue. You’ve also provided the Firebase UID: 54gXma2B7FRDLuLNTryNPc9rRCJ3.
To help the support team investigate further, could you please share:
- The specific initialization and login code snippets you’re using with Plug n Play?
- Any relevant browser console logs or screenshots showing the issue (if applicable)?
- If you’re using custom authentication (e.g., a custom verifier or your own authentication backend), please provide the verifier name and method of login.
This information will help us pinpoint the root cause more efficiently. In the meantime, if you haven’t already, please review the Plug n Play troubleshooting guide for common issues.
Let us know if you can provide those details, and we’ll make sure this gets the attention it needs!
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
const privateKeyProvider = new EthereumPrivateKeyProvider({
config: { chainConfig },
});
const web3authNoModalOptions: IWeb3AuthCoreOptions = {
clientId,
chainConfig,
privateKeyProvider,
uiConfig: {
appName,
appUrl: websiteUrl,
mode: "dark",
logoDark,
theme: { primary: "#FC4141" },
},
enableLogging: !isProd,
web3AuthNetwork: isProd
? WEB3AUTH_NETWORK.SAPPHIRE_MAINNET
: WEB3AUTH_NETWORK.SAPPHIRE_DEVNET,
sessionTime: 86400 * 7,
};
const web3AuthInstance = new Web3AuthNoModal(web3authNoModalOptions);
const authAdapter = new AuthAdapter({
privateKeyProvider,
loginSettings: {
mfaLevel: "none",
},
adapterSettings: {
clientId,
uxMode: UX_MODE.REDIRECT,
loginConfig: {
jwt: {
verifier: "custom-verifier-jwt-firebase",
typeOfLogin: "jwt",
clientId: web3AuthClientId,
},
},
},
});
const defaultWcSettings = await getWalletConnectV2Settings(
CHAIN_NAMESPACES.EIP155,
[
chain["Ethereum"].chainId,
chain["Sepolia"].chainId,
chain["Arbitrum"].chainId,
chain["ArbitrumSepolia"].chainId,
],
walletconnectProjectId
);
const walletConnectModal = new WalletConnectModal({
projectId: walletconnectProjectId,
});
const walletConnectV2Adapter = new WalletConnectV2Adapter({
adapterSettings: {
qrcodeModal: walletConnectModal,
...defaultWcSettings.adapterSettings,
},
loginSettings: { ...defaultWcSettings.loginSettings },
});
const injectedAdapters = await getInjectedAdapters({
options: web3authNoModalOptions,
});
injectedAdapters.forEach((adapter: any) => {
web3AuthInstance.configureAdapter(adapter);
});
web3AuthInstance.configureAdapter(authAdapter);
web3AuthInstance.configureAdapter(walletConnectV2Adapter);
await web3AuthInstance.init();
await web3Auth.connectTo<AuthLoginParams>(WALLET_ADAPTERS.AUTH, {
loginProvider: "jwt",
extraLoginOptions: {
id_token: idToken,
verifierIdField: "sub",
domain: websiteUrl,
},
});
await web3Auth.authenticateUser();
- There are no browser console logs
- Verifier name is
custom-verifier-jwt-firebase
, and the login method wasemail
via jwt
There is only one wallet address that I see corresponding to that FireBase UiD. I have DM’D you the only address that I see. Please have a look.