multiversx / mx-sdk-js-web-wallet-provider

Signing provider for dApps: MultiversX (Web) Wallet.
Other
0 stars 1 forks source link

Are we forced to use NativeAuthToken or is it a bug? #24

Closed juliancwirko closed 1 year ago

juliancwirko commented 1 year ago

Problem:

Question: Are we forced to use NativeAuthToken logic, or is it something else?


xPortal for Android v2.0.29 web wallet provider v2.4.0

andreibancioiu commented 1 year ago

Reproduced.

https://wallet.multiversx.com/hook/login?token=example-auth-token&callbackUrl=https://localhost:8080/index.html 
-> "Invalid loginToken. You may be trying to decode a nativeAuthToken. Try using decodeNativeAuthToken method instead"

https://devnet-wallet.multiversx.com/hook/login?token=example-auth-token&callbackUrl=https://localhost:8080/index.html 
-> no error

https://testnet-wallet.multiversx.com/hook/login?token=example-auth-token&callbackUrl=https://localhost:8080/index.html 
-> no error

Fix will be published on the Web Wallet.

Thank you :pray:

arhtudormorar commented 1 year ago

A fix was deployed today. Please re-check

juliancwirko commented 1 year ago

Yes, the error in the console is gone.

The only thing left in my case is that when I do the first transaction after signing in using web wallet + xPortal, I only land in the web wallet. The popup with sign info doesn't show, but when I go back to my app (where I am already signed in) and do the same transaction once again, the popup shows up, and I can sign it in xPortal. I've also tried a hard refresh in my app after sign-in redirection and the same result. The first transaction redirection doesn't trigger the signing process, but the second try does.


Tested on the devnet. xPortal for Android v2.0.29 web wallet provider v2.4.0 At: https://multiversx-nextjs-dapp.netlify.app/

juliancwirko commented 1 year ago

It seems to work ok now with xPortal 2.0.30 for Android