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

NewReceiptValidationError InvalidReceiverId #23

Open
ryancwalsh opened this issue Apr 16, 2022 · 2 comments
Open

NewReceiptValidationError InvalidReceiverId #23

ryancwalsh opened this issue Apr 16, 2022 · 2 comments
Labels
enhancement New feature or request

Comments

@ryancwalsh
Copy link

I'm curious whether this project is now abandoned.

The Telegram group seems to be gone, and I'm experiencing this error (which I've also already reported here.)

I'm trying to set up a Neardrop account. It prompts me to save the 12-word passphrase, confirm one of the randomly-chosen words, and then approve sending 5 N to a new account.

But I hit this error every time:

image

Error
Sorry an error has occurred. You may want to try again.
View FAQ
{"index":0,"kind":{"index":0,"kind":{"NewReceiptValidationError":{"InvalidReceiverId":{"account_id":"<myAccountIdHere>.linkdropv1.near"}}}}}

@ryancwalsh
Copy link
Author

Patrick | NEAR suggested at https://t.me/neardrop/796 that I should try using a named account instead of an implicit account.

Connecting my named account to Neardrop worked!

So, either the functionality for implicit accounts should be fixed, or a validation step could be added to catch people trying to connect an implicit account, and a message would explain to them that it's not allowed.

Thanks!

@agileurbanite
Copy link
Owner

Need to support implicit accounts as some wallets don't have named accounts created

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants