-
Notifications
You must be signed in to change notification settings - Fork 429
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
Transaction broadcast error.
on posting/commenting
#1871
Comments
Users are still having this issue as of today.
|
Very glad you all are working on this. :) I noticed this again tonight the last time I submitted a root post. Doesn't seem to happen on comments. I was just poking around at Here's what I saw in the console in case that's helpful:
|
This happened to me today, and I didn't even realize that the blog post had published four times before I came here to see if the submission error I was getting was a known issue or not. So now I have four copies of my blog post submitted to the blockchain. You should at least put a notification or something on the 'Post' page to let people know that if they receive this error message that it's likely their post actually published and they should check their blog page. |
Happens to me with every root post I create. Could we get an update from the developers on when this might be resolved? Thanks! |
It's being worked on. Sorry, no ETA as of yet. |
Good luck. Please fix it. This is happening to me every post. I post 1-4 times a day. My friends have been having the same problem too. This issue started 3 weeks ago and is still happening now. |
I believe, this is still an issue: Live recording: https://youtu.be/tkLdqM0xrNI Errors from console:
@roadscape, @john-g-g: please re-open this issue. |
@noisy the issue is still open. |
This was fixed in https://github.com/steemit/jussi and deployed a few hours ago. |
Recently there have been reports of
Transaction broadcast error.
when submitting a post/comment. Users resubmit the form and find it has been double-posted.The text was updated successfully, but these errors were encountered: