Skip to content
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

Return error during requestSignIn if contractId is invalid #195

Closed
kcole16 opened this issue Jan 22, 2020 · 2 comments · Fixed by #527
Closed

Return error during requestSignIn if contractId is invalid #195

kcole16 opened this issue Jan 22, 2020 · 2 comments · Fixed by #527
Assignees
Labels
bug Something isn't working P1 Very important

Comments

@kcole16
Copy link

kcole16 commented Jan 22, 2020

Similar to near/near-wallet#219.

Expected behavior
When entering an invalid (non-existent) contractId argument in nearlib.WalletAccount.requestSignIn, the developer should receive an error.

@janedegtiareva janedegtiareva added bug Something isn't working P1 Very important labels May 26, 2020
@behaviary
Copy link
Contributor

@kcole16 is this just in wallet? Is this solved? Not really sure how to fix this on near-api-js side right now.

@kcole16
Copy link
Author

kcole16 commented Jun 30, 2020

We've implemented a fix on the wallet side, but I do think we should generalize this somewhere, as this is really an error on the app developer's side and could occur with any wallet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working P1 Very important
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants