-
Notifications
You must be signed in to change notification settings - Fork 86
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
Problem syncing tasks with taskserver #324
Comments
Would any of you, @JangamRuthvik, @its-me-abhishek, or @vkprogrammer-001, be willing to investigate this issue? |
@Pavel401 noted will get back to you. I may take more time because from this Monday I have my mid semester exams but if issues still persist I will definitely contribute |
@Pavel401, I will work on resolving the issue. If I find a solution, I’ll notify you promptly. |
Sure, I'll try to find a fix for this |
Any update on this? |
@Pavel401 I will start working on this |
@JangamRuthvik and I attempted to reproduce the issue but it worked fine and didn't have any issues. Therefore, we are closing this for now. |
Describe your issue
There is a Problem with syncing tasks with a taskserver. As far as I can tell, the sync key is not correctly saved.
I've attached the taskserver log to be able to troubleshoot as I don't see any logs when running the app with flutter.
Also I've noticed that tasks created on the PC (before setting up the app, as after setting up the app is the same problem as above) are not shown in the app after the first sync even if the taskserver did send every task.
Steps to reproduce
What was the expected result?
Normally I would expect the app to be able to sync task changes that are not made in the app since this is the whole point of a taskserver.
Put here any screenshots or videos (optional)
Here are the logs from the taskserver, with explanations what is being done: (IPs are redacted)
How can we contact you (optional)
No response
Would you like to work on this issue?
No
By submitting this issue, I have confirmed that:
The text was updated successfully, but these errors were encountered: