ToastWallet / core

This repo contains the core code for Toast Wallet. It is built for iOS, Android and browser directly from this repository. PC builds are built from the browser version using Electron.
GNU General Public License v2.0
210 stars 80 forks source link

Potential Error: Sending XRP #23

Closed jovincroninwilesmith closed 6 years ago

jovincroninwilesmith commented 6 years ago

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 commented 6 years ago

Lastly, I have used the account explorer to validate there are funds.

screen shot 2018-01-10 at 3 44 28 pm
denizdogan commented 6 years ago

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 commented 6 years ago

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

jovincroninwilesmith commented 6 years ago

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

ToastWallet commented 6 years ago

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

jovincroninwilesmith commented 6 years ago

Confirmed fix :) Thanks so much