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.

Sign up for GitHub

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

Jump to bottom

Reddit PM transport can get out of sync when using previously used accounts #10

Open
Und3rf10w opened this issue Jan 26, 2018 · 1 comment
Open

Reddit PM transport can get out of sync when using previously used accounts #10

Und3rf10w opened this issue Jan 26, 2018 · 1 comment
Assignees
@Und3rf10w
Labels
backlog Issues that are not planned to be worked on in the near future; considered of low(er/est) priority bug transport

Comments

@Und3rf10w
Copy link
Owner

If the account(s) configured to be used for the transport have been used for this purpose before (i.e. there's previous c2 messages in the inbox(es)), it's possible to trigger a bug where the server and client can get out of sync. Usually, this can be fixed by restarting the server, and disabling the staging process.
@Und3rf10w Und3rf10w self-assigned this Jan 26, 2018
@Und3rf10w Und3rf10w added the bug label Jan 26, 2018
@Und3rf10w Und3rf10w added the backlog Issues that are not planned to be worked on in the near future; considered of low(er/est) priority label Jun 7, 2018
@Und3rf10w
Copy link
Owner Author

Adding to backlog for now, will revisit after beta release, see #23 and Milestone 3.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Und3rf10w Und3rf10w

Labels
backlog Issues that are not planned to be worked on in the near future; considered of low(er/est) priority bug transport
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@Und3rf10w