-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
User see different Gaia data with the same private key on different browsers #664
Comments
Hi @pradel, Thanks for reporting this issue to us! we did recently migrate our gaiahub hostname, which may explain the difference in data seen between xverse versions, but theoretically all your data should have also been migrated by Hiro. more info on the hiro migration here: https://forum.stacks.org/t/gaia-hub-data-archival-and-migration/15281 if your users have missing data, it could be that the data migration had some issues from the Hiro side |
@teebszet I think the problem reported on this issue is different. This user uses the same Xverse version in his 2 browsers (0.22.0). However logging in with the same private key and account on each browser produces a different result. |
@pradel I'm not sure I know how to reproduce this. are your users still seeing this behaviour? |
@teebszet yes they are, what kind of logs or others would you need? |
hi @pradel , do you have any sort of reproduction steps?
Can you explain a bit more the flow of how Sigle uses Xverse to inject the Gaia Sigle URL?
where does hubUrl come from in this JSON? |
I never managed to reproduce it myself, but multiple users reported this issue in the past and they were all using Xverse, Leather users never reported it.
It's not something we are injecting, it's a URL that is injected by Xverse/Leather when a user login with any app along with other user information like an app private key to interact with the user Gaia bucket.
All the JSON is available in the local storage, my guess is that Xverse is sending some data on Auth and the Stacks.js library saves it to the local storage. |
hi @pradel, just want to revisit this and see if your users are still reporting this issue? |
Hi @teebszet, yes I am still seeing that issue coming up |
@pradel would you be able to have the affected users output their chrome local storage state to help debug this? let's open up a telegram group, if we don't have one already. I DM'd your X handle |
Component
On Chrome:
On Arc:
Severity
Major (Unable to proceed on a journey)
Summary
Jay Jay from Liquidium reported an issue when connecting on Sigle with Xverse on 2 different browsers. The content he sees in his drafts is different in both browsers.
I suspect that Xverse is not injecting the correct Gaia Sigle URL and thus 2 buckets were created. You can see in the 2 following JSON that the Gaia URL for other apps are differents too.
Here is the content of blockstack-session for the chrome one (the one which is up to date)
Here is the content of blockstack-session for the arc one (the one which is not up to date)
Reproduce steps
This is the tricky part, I haven't been able to reproduce the behavior on my side. However it's not the first time a user reported losing access to his content. What I saw is that the Gaia hub where files were stored always changed for these users.
Expected result
Jay Jay should see the same Gaia hub on both browsers
Actual result
He gets 2 differents Gaia buckets for Sigle.
Remark
Let me know if you need more info from my side or Jay Jay side.
The text was updated successfully, but these errors were encountered: