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

Potential Error: Sending XRP #23

Closed
jovincroninwilesmith opened this issue Jan 10, 2018 · 6 comments
Closed

Potential Error: Sending XRP #23

jovincroninwilesmith opened this issue Jan 10, 2018 · 6 comments

Comments

@jovincroninwilesmith
Copy link

I have tried to send XRP to multiple accounts and keep getting hit with the error "An error occurred when trying to make your payment. Most likely lack of funds in the account you are sending from. ( The network requires a minimum account balance.) This error can also be caused by an invalid or not activated destination address or if the Ripple network is overloaded."

I have tried multiple addresses including the address for sending tips and nothing seems to progress.

Additionally, I have ample XRP in the address I am sending from.
screen shot 2018-01-10 at 3 38 59 pm

Please let me know if you have any idea why this may be happening.

@jovincroninwilesmith
Copy link
Author

Lastly, I have used the account explorer to validate there are funds.
screen shot 2018-01-10 at 3 44 28 pm

@denizdogan
Copy link

denizdogan commented Jan 10, 2018

I have the exact same error. Very frustrating, but relieved to see I'm not the only one.

EDIT: Works now, about 30 minutes later!

EDIT 2: Actually, I got a success message, but no transaction showed up in an online explorer and no transaction in the Toast Wallet list. I tried again, got a new success message, but nothing else indicating that a transaction has actually been made...?

@jmannanc
Copy link

This is most likely because of Ripple Gateway congestion, an update is coming soon to help fix this.

@jovincroninwilesmith
Copy link
Author

@denizdogan what was the timeframe in which you waited before it worked? I am still experiencing the same issue.

@ToastWallet
Copy link
Owner

The gateway cycling update has been pushed to the repo. It's being rolled out now. This should largely fix this issue.

@jovincroninwilesmith
Copy link
Author

Confirmed fix :) Thanks so much

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

No branches or pull requests

4 participants