-
Notifications
You must be signed in to change notification settings - Fork 40
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
Synchronisation needs to be triggered manually #232
Comments
Problem still occurs with build 232. The full synchronisation should be triggered when:
Maybe a full synchronisation should not be triggered in following cases, as wallabag API supports single entry for these cases:
|
Linked to issue #185 |
Edited second post to add
This is linked to #231 I think this bug should be chased and smashed before releasing the 5.0.0 version to the App Store :) |
After proofreading this proposal the background is very good. In the state it does not work less well than before. But no longer trigger automatic refresh at launch. (A good point in relation to # 185) The manual synchronization action is not practical I recognize it. Regarding each task such as favorites, reading ... they do not trigger full synchronization, but only pushes action on the server The solid bases of the migration to CoreData will make it possible to launch more events depending on the operations and reduce full synchronization. There is still a lot of work on this point. I think that will not be able to launch the application with this synchronization system, but it should be the focus of a next release. |
Steps to reproduce/test case
Add articles to Wallabag. Synchronise it with the app. Open an article an mark it as read.
Kill the app. When launching the app again, the article is not marked as read.
Improvement
Trigger the synchronisation as soon as the "read" button is pressed.
The text was updated successfully, but these errors were encountered: