Closed jonsnowpt closed 1 year ago
NOTES
WalletConnect not working with the
tutorial
from Moralis.Depreciated packages and not working
npm modules
fromWalletConnect
with aV2
migration are required to get the code working, however, noNEWποΈ
guide exists onV2
Wallet connect support.
Asking around forums discord-link and other sources, can't seem to get it working either.
Aim to get this sorted with
mobile
connection, and find a solution.
@migbash
Did you submit a request to Moralis support?
@jonsnowpt Yes, but no response as of yet. I will follow up.
@migbash
You have a chat available on the client area. They were very fast with me.
@jonsnowpt yes, but no response yet. Waiting to hear - used the chat
feature also.
NOTES
DEPENDENCY npm package | WEB3-PROVIDER
GUIDE | moralis - authetication V1
GUIDE | walletconnect - wallet | V2
GUIDE | walletconnect - html modal | V2
HOW-TO | connect web3 mobile (1)
HOW-TO | connect web3 mobile (2)
HOW-TO | connect web3 mobile (3)
UPDATE [#1]
Root of the issue identified as the
SvelteKit
&vite
compiler issue - that do not work with thenpm
packages ofWalletConnect
. Raising issues on deployment, with errors like such as:
Module "buffer" has been externalized for browser compatibility. Cannot access "buffer.Buffer" in client code.
Discord Moralis Ticket Discussion
MY OPENED ISSUE
| https://github.com/vitejs/vite/issues/12102 Opened an issue with VITE
FROM VITE: We recommend avoiding Node.js modules for browser code to reduce the bundle size, although you can add polyfills manually. If the module is imported from a third-party library (that's meant to be used in the browser), it's advised to report the issue to the respective library. source-error
π οΈ Possible solution(s):
StackOverflow | Vite Config Bundle
GIST FIX
Stackoverflow - Buffer Access
GitHub | Vite issues
β βοΈ Fix applied (of-sorts)
19/02
solution
UPDATE [#2]
New issue detected after solving the previous issue of the
Vite
compiler issue not importing and crashing the#1
issue (above).Now the
WalletConnect
works and opens theconnection
for the QR-code scanning on (desktop) and the MetaMask mobile application on (mobile). However, on (mobile), both inV1
andV2
of theWalletConnect
SDK the MetaMask does nothing after the intent of opening the application - and does not prompt to sign in the user and neither redirects the user back to the website.
Polling infinite loop - desktop (interject) error (1)
Polling infinite loop - desktop (interject) error (2)
This is a very common issue and has been reported and seen many times - with no response from
WalletConnect
since many months. (check discord link below).
Moving away from
WalletConnect
as the testing of both theMetaMask
connection formobile
application usingV1
andV2
does not work, and no fix is looking to be in place. Instead theofficial | BETA
version of the MetaMask SDK is used to access theMetaMask
application and retrieve theusers
wallet address and log them in.
βοΈHas its own issues
=>IOS
user must have theMetaMask
application open in the background andsigned in
for theMetaMask SDK
to work every-time onMobile
@migbash
Not working on Connect wallet in the user settings section.
@migbash
The Button size is now incorrect:
π Introduction:
The MetaMask wallet connection is working on the Desktop version but does not work on the MetaMask app has a Dapp. It seems that to get this working; we need to add Wallet Connect into the loop.
π Details:
The goal is to allow the Dapp to work on the MetaMask App; for this, we have the following resources:
https://forum.moralis.io/t/authentication-in-mobile-app/20949/2
https://docs.moralis.io/authentication-api/how-to-sign-in-with-walletconnect
This requirement was confirmed by the Moralis support guys.
π Steps to Reproduce:
Enter the MetaMask App, and using the browser, try to access scores. Betarena and then Connect.
π€ Expected Behavior:
Connect the MetaMask wallet.
π₯ Actual Behavior:
Nothing happens.
π‘ Additional Information:
We already have an account on Wallet Connect and a Betarena Project. Access details are available upon request.