-
Notifications
You must be signed in to change notification settings - Fork 143
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
Update @stacks/[email protected]
, fix bns lookupProfile
#2089
Conversation
446d9fe
to
26637a2
Compare
There is a bug in 3.1.0 hirosystems/stacks.js#1152 |
Thanks @friedger, yes this one is def not to merge yet. Converted to draft. |
@kyranjamie would it be possible to get a new build with 3.1.1 please 🙏 ? |
26637a2
to
a3fe094
Compare
@pradel done, building now |
a3fe094
to
189c7c1
Compare
Amazing thanks! |
Hey there, any update to merge this one? :) |
fcd7655
to
8115583
Compare
@stacks/[email protected]
, fix bns lookupProfile
The changes introduced in this pr are mostly related to how the profile is signed, so I think you need to login to an app using the publish_data scope. You could probably use the TODO app on this branch hirosystems/todos#104. You would have to log in using an account owning a .btc name and you can try to call the |
@kyranjamie I'd like to include this on our next release if possible. I'll move it to "QA" so @Eshwari007 or @timstackblock can pick it up while it's being reviewed. |
@kyranjamie any input on how to test the ticket is much appreciated.Thx in ad |
@Eshwari007 this is how to test it #2089 (comment) |
@kyranjamie Want to run by you if am missing something here.
Used the link from hirosystems/todos#103 |
Hi @pradel, would you be able to help Esh test this PR? if async on the ticket is too slow, we can try on Discord |
@andresgalante happy to help, do you have a channel on discord for this? |
8115583
to
69a946b
Compare
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/blockstack/stacks-wallet-web/9SPM26G5Whw7Nt2tzV8NKPVWL453 |
I uploaded a build from the Todo app pending pr to netlify for you to test more easily https://blissful-agnesi-f97d5f.netlify.app/. Now we just need #2194 to be merged into this branch and get a new build for the wallet in order to finish the testing part :) Edit: The netlify build is not working so I prepared you a Sigle branch in order to test https://sigle-1ljk1nxmn-sigle.vercel.app/login |
|
69a946b
to
8ff2088
Compare
Testing flowDemo link: https://sigle-9i6eqj7dj-sigle.vercel.app/login These are the tests cases with the new Hiro wallet version:
To view your public blog, on the top right corner of the dashboard click on this button 👇 |
@leopradel Somewhat good news. Use case 3 : I was able to login in with .btc address ( bns address visible on the left-hand corner as well), create a blog ,save and publish it. I tried selecting 'view my blog but received 'token issuer error 'https://sigle-9i6eqj7dj-sigle.vercel.app/hiromaintest.btc. However, in the sigle app itself, I was able to view my test blog under the User case 4: I tried login with a new account without username and received the following error on console Note: I dont have an account with bns name as per use case 1 and 2 hence will create one and test the app as well |
Thanks for trying it out! For case 3: the fact that you are seeing the "token issuer error" means that the profile is not signed properly, also meaning that the test failed. const { getAddressFromPublicKey } = require('@stacks/transactions');
console.log(getAddressFromPublicKey('0217ecac7614a7a724f0addfc4241f756129171cc460eef430e895f04a08ff5658'));
// => SP2FB4MP6QZ1JV8JJZTCBYP7P9T6GXB0842YHYVX3 This is the result you would get by logging in with the current Hiro wallet version (without the fix from this pull request) as the profile is signed using the old stacks key. Can I ask you to triple check that the extension you tried does have the changes made in this pull request? #2196 For case 4: it's fine as it's not related to this pull request and the Hiro wallet in general but rather the subdomain registrar (I created an issue in the repo already). |
@pradel Spoke too soon. Findings: Use case 3: the irony is that this partially worked bfr the token error was produced but now with the fix branch am not able to see any actions on the app upon selecting the account with btc on it sigle.btc.account.movUse case 4:I was able to sign in with an account that doesn't have a bns attached to it and it created name.stx for me in the app |
When QA approved, I'll make these changes #2172 (rather than merging this PR), as it'll be a real pain to rebase on. |
@Eshwari007 I did the testing on multiple devices and it worked all the time. Would you mind trying one more time with a clean cache? 🙏 |
@pradel Yay-good news. Test passed -used #2172 |
Thanks a lot @Eshwari007 for testing this PR. Lets get it into the next release after 3.1 |
Pushing @pradel's #2087 PR again so our CI/test builds run.
This PR will fixs the bns
lookupProfile
functionality. @pradel will write up steps we need to follow to QA this. cc/ @andresgalante can you plan when we'll include this in release?