You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using Justnote as an example, when signing in with the Xverse extension, the Xverse app, and the Leather wallet, they return different appPrivateKey, causing different Gaia hub bucket addresses.
Reproduce steps
On the desktop, signing with the Xverse extension
On Chrome, visit justnote.cc
Click the Sign in button
Choose Sign in with a Stacks Wallet
On Android or iOS, signing with the Xverse app
Open Xverse app
Choose the web view tab
Enter justnote.cc in the URL bar
Tap Sign in button
Choose Sign in with a Stacks Wallet
Expected result
They provide the same appPrivateKey, so we have the same Gaia hub bucket address, and users can see the same data.
Actual result
They return different appPrivateKey.
Remark
The leather wallet also returns different appPrivateKey. I'm using [email protected].
The text was updated successfully, but these errors were encountered:
I am also concerned about what would happen to current users. I believe it isn't difficult to fix the appPrivateKey to be the same between the Xverse app, extension, and Leather. But when current users upgrade their apps, they won't be able to access their current data anymore.
Severity
Major (Unable to proceed on a journey)
Summary
Using Justnote as an example, when signing in with the Xverse extension, the Xverse app, and the Leather wallet, they return different appPrivateKey, causing different Gaia hub bucket addresses.
Reproduce steps
On the desktop, signing with the Xverse extension
On Android or iOS, signing with the Xverse app
Expected result
They provide the same appPrivateKey, so we have the same Gaia hub bucket address, and users can see the same data.
Actual result
They return different appPrivateKey.
Remark
The leather wallet also returns different appPrivateKey. I'm using [email protected].
The text was updated successfully, but these errors were encountered: