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
Describe the bug
After calling userSession.loadUserData() after the authentication flow, fields like username are not properly populated. I am using the Todos app example. If you use the live demo, you can see that the username field is blank. The username should show in the upper right corner in the live demo but is instead an empty string. I am seeing the same behavior in my own app.
In my wallet, I have a .btc domain that I would expect to be used as my "username". Is my thinking incorrect?
What version of Stacks.js are you using?
Using version 2.0.1 of @stacks/auth Is the bug present in the Stacks.js CLI, Gaia hub, Connect or Blockstack Browser?
In the stacks.js frontend library To Reproduce
Steps to reproduce the behavior:
Go to the Todos example (or any app using hiro connect/auth)
Follow the auth flow
Username is blank
Expected behavior
username should show the one selected from the authorization flow
Desktop (please complete the following information):
Browsers tested: Chrome, Brave
The text was updated successfully, but these errors were encountered:
Describe the bug
After calling
userSession.loadUserData()
after the authentication flow, fields likeusername
are not properly populated. I am using the Todos app example. If you use the live demo, you can see that the username field is blank. The username should show in the upper right corner in the live demo but is instead an empty string. I am seeing the same behavior in my own app.In my wallet, I have a
.btc
domain that I would expect to be used as my "username". Is my thinking incorrect?What version of Stacks.js are you using?
Using version 2.0.1 of
@stacks/auth
Is the bug present in the Stacks.js CLI, Gaia hub, Connect or Blockstack Browser?
In the
stacks.js
frontend libraryTo Reproduce
Steps to reproduce the behavior:
Expected behavior
username should show the one selected from the authorization flow
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: