yes , that’s ok. You can update all the web3auth packages to v8.6.2 if you want to.
Also Can you share with me some code snippets?
yes , that’s ok. You can update all the web3auth packages to v8.6.2 if you want to.
Also Can you share with me some code snippets?
const selectedChain = 0;
const chainConfigs = [
{
chainNamespace: CHAIN_NAMESPACES.EIP155,
chainId: “0x89”,
chainCode: 137,
rpcTarget: process.env.NEXT_PUBLIC_RPC_MATIC,
displayName: “Polygon”,
blockExplorerUrl: “https://polygonscan.com/”,
ticker: “MATIC”,
tickerName: “Polygon”,
userRegistry: “0x55986780342c3683C654384d76c815ACfB9292a9”,
paymasterKey: process.env.NEXT_PUBLIC_PAYMASTER_KEY_MATIC,
bundler: process.env.NEXT_PUBLIC_BUNDLER_MATIC
},
{
chainNamespace: CHAIN_NAMESPACES.EIP155,
chainId: “0xC4”,
chainCode: 196,
rpcTarget: process.env.NEXT_PUBLIC_RPC_X_MAIN,
displayName: “Layer X Mainnet”,
blockExplorerUrl: “X Layer Explorer | Blockchain Explorer | OKLink”,
ticker: “OKB”,
tickerName: “OKB”,
userRegistry: “0x2f5CC68ad8E94cFC68F71A34Da7E606AF43c498e”,
paymasterKey: process.env.NEXT_PUBLIC_PAYMASTER_KEY_X_MAIN,
bundler: process.env.NEXT_PUBLIC_BUNDLER_X_MAIN,
}
];
const web3authInstance = new Web3Auth({
privateKeyProvider: privateKeyProvider,
clientId: process.env.NEXT_PUBLIC_WEB3AUTH_CLIENTID,
web3AuthNetwork: process.env.NEXT_PUBLIC_WEB3AUTH_NETWORK,
sessionTime: (86400 * 7),
uiConfig: {
appName: “Lazy Games”,
mode: “dark”,
loginMethodsOrder: [“google”],
logoLight: “https://web3auth.io/images/web3auth-logo.svg”,
logoDark: “https://web3auth.io/images/web3auth-logo---Dark.svg”,
defaultLanguage: “en”,
loginGridCol: 3,
primaryButton: “socialLogin”,
},
});
const adapters = await getDefaultExternalAdapters({ options: {
clientId: process.env.NEXT_PUBLIC_WEB3AUTH_CLIENTID,
chainConfig : { …chainConfigs[selectedChain], chainNamespace : CHAIN_NAMESPACES.EIP155},
privateKeyProvider: privateKeyProvider,
web3AuthNetwork: process.env.NEXT_PUBLIC_WEB3AUTH_NETWORK,
} });
adapters.forEach((adapter) => {
web3authInstance.configureAdapter(adapter);
});
// web3authInstance.configureAdapter(metamaskAdapter);
await web3authInstance.initModal();
if (!web3authInstance) {
return
}
let web3authProvider = web3auth.provider;
if (!web3authInstance.connected) {
try {
web3authProvider = await web3authInstance.connect();
} catch (error) {
if (error.message === "User closed the modal") {
console.error("User closed the modal. Please try again.");
return;
} else {
console.error("An error occurred:", error);
return;
}
}
}
Also demo example from web3auth is also not working on the mobile metamask connect with walletconnect v2. I have scanned QR code from metamask and it results in the same error
Hi @lazygamestech,
Thank you for reporting this issue. It is working fine with Rainbow wallet, but it is throwing an error with mobile Metamask. I will address this with our team and provide an update soon.
Thanks
Also is there any way we can connect to mobile metamask from the mobile browser ?
Using regular metamask adapter works on system and not on mobile so we are kind of stuck at that level and for that reason we used walletconnect and walletconnect also has issue.
So is there any workaround to it ?
hi @lazygamestech,
I believe your best option currently is to use WalletConnect.
While our team is addressing the issue, Is it possible for you to use the Rainbow wallet on your mobile device?
Any TAT for the fixes ? We are using it on production and needs to be addressed soon
We are looking to integarate the Walletconnect ourselves outside web3auth to resolve this issue.
If you provide TAT for the fix, we will take a decission to continue with the implementation walletconnect outside or wait for it
It is critical for us and we are looking to go big on the marketing and promotion
Any update on this please
@lazygamestech Thanks for your patience.
Please give me sometime to check back with our Dev team and provide an update.
Hi @lazygamestech,
We estimate that it will be resolved by Tuesday.
Is that suitable for you?
Thanks for the patience.
Thanks, Let me know once it is updated
Any update on this please
The issue has been resolved and the PR is waiting to be tested and approved.
I’ll let you know when it’s released
Thanks for the patience
Any TAT for this to go into production ?
I cannot provide an ETA, but I will do my best to expedite the process.
Any progress on this ticket please
I regret to inform you that I do not have any information yet about the estimated time for the approval of this PR.
This is solved now. Please update to latest alpha version
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.