-
Notifications
You must be signed in to change notification settings - Fork 199
Cannot log in to any apps #2053
Comments
Describe the bug
To Reproduce
Expected behavior Screenshots Desktop (please complete the following information):
|
Related question: Is the native app even supported now? E.g., is the direction to a mode where the user has to expose their private keys to a web-based service? That would handily defeat the utility of Blockstack, imo. |
The existing native install for the Blockstack Browser is still available though deprecated. We'll continue to support it only with critical patches until Summer 2021. The direction is towards a mode in which users authenticate with an installed web browser extension instead of a desktop app since it creates better affordances (e.g. for transaction signing with Stacks 2.0) while maintaining client-side self-sovereignty. Users don't need to expose their private keys to any web-based service with the extension, which you can find here: https://www.blockstack.org/install |
@markmhx That completely answers my question. Might be off-topic but in case not: This could be made easier to find in the documentation/etc materials. |
I'm glad to hear that! And you have a point – our documentation is lacking in this regard. We're working on updating user-facing information about the browser extension / authenticator generally ahead of a new release next month. I'll make a point to include these details in it. 🙏 |
I have tried using three different apps: Lander, Sigle, and BlockSurvey. I have not been able to successfully login to any of them.
Lander:
Sigle:
BlockSurvey (did not show an error message, just took me back to the home page and prompted me to log-in again)
Normally I'd assume this was a problem with the app and report the problem to the app developer but since I can't login to any of the apps I tried I figure this might be a Blockstack Browser issue.
Blockstack Browser version: 0.37.0
Web browser: Firefox 74.0
OS: Linux Mint 18.3 (based on Ubuntu 16.04 LTS)
The text was updated successfully, but these errors were encountered: