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

Schedule Toot button causes repeated duplicated posts on GoToSocial #4703

Closed
rochacbruno opened this issue Oct 2, 2024 · 3 comments · Fixed by #4705
Closed

Schedule Toot button causes repeated duplicated posts on GoToSocial #4703

rochacbruno opened this issue Oct 2, 2024 · 3 comments · Fixed by #4705
Labels

Comments

@rochacbruno
Copy link

Detailed description

When trying to schedule a post on Tusky connected to a GoToSocial instance (which doesn't support scheduling), instead of erroring, Tusky will post the message repeated indefinitely until Android application is forced stop.

More Context: https://go.rocha.social/@bruno/statuses/01J95XX6VZ3FW5K6GRR7V4H94K

Steps to reproduce the problem

  1. Using Tusky connect to a gotosocial instance (I can provide an account for testing)
  2. Write a post
  3. Click schedule button and set 3 hours ahead
  4. Click post

Expected: Tusky would report "Error scheduling, post is saved as a draft"

What happens: Tusky will post and then indefinitelly repeat the same post, making the timeline to be spammed with multiple posts with the same content.

GTS issues:
superseriousbusiness/gotosocial#1006
superseriousbusiness/gotosocial#2723
...

Debug information

26.2 - Android 11 - From Google Play

@rochacbruno rochacbruno added the bug label Oct 2, 2024
@connyduck
Copy link
Collaborator

Meh its a Json parsing error because GtS replies with a Status object and not a ScheduledStatus.

@tsmethurst
Copy link
Contributor

We don't yet support scheduled statuses, so we can partially fix this on our side by returning an error or something instead of just a normal Status.

@rochacbruno
Copy link
Author

@tsmethurst I suggest rejecting posts with scheduled_at option until the feature is implemented, then the client can manage it by the HTTP 501 returned.

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

Successfully merging a pull request may close this issue.

3 participants