I was testing kagi.
https://kagi.com/discussdoc?url=https%3A%2F%2Fgithub.com%2Fnextcloud%2Fandroid%2Fissues%2F19
with this input was
https://github.com/nextcloud/android/issues/19
The trick is the issue is very old, and very long.
I had to load more comment on github. The summarizer here is failing badly.
It seems that some recent improvement made on the Nextcloud android app now allow some 2 way sync...
Hope that helps,
Regards,
Sylvain.
Here is the exchange we had:
https://github.com/nextcloud/android/issues/19
What would you like to know?
what is the blockers that prevented to developp 2-ways since since 2016?
Based on the information provided in the GitHub issue, there are a few key blockers that have prevented the development of 2-way sync in the Nextcloud Android app since 2016:
1
The current implementation of sync in the Nextcloud Android app is only partially 2-way. While changes made in the cloud are propagated to the local device, changes made locally are not automatically synced back to the cloud. Users have to manually press the "sync" button to upload local changes.
The app documentation still claims the app offers 2-way sync, even though this functionality is not fully implemented. This has led to user confusion and frustration.
Implementing proper 2-way sync, where local changes are automatically detected and uploaded to the cloud without manual intervention, seems to be a significant technical challenge. The issue comments indicate that this requires solving problems around file renaming, conflict resolution, and automatic detection of local file changes.
There appears to be a lack of clear roadmap or prioritization from the Nextcloud developers to address this long-standing issue. Some users have expressed a desire for the developers to provide more transparency and communication around their plans for 2-way sync.
The Nextcloud Android app development seems to be a volunteer-driven effort, which may contribute to the slow progress on this feature compared to the desktop client, which likely has more dedicated resources.
In summary, the key blockers seem to be the technical complexity of implementing robust 2-way sync, the mismatch between the app's documentation and its actual capabilities, and a lack of clear prioritization and communication from the Nextcloud developers on addressing this issue. Overcoming these challenges appears to be an ongoing effort for the project.
when Two way sync was enabled was enabled in the app?
Based on the information provided in the GitHub issue, it seems that two-way sync has not been fully implemented in the Nextcloud Android app yet. The key points are:
Based on the information provided in the GitHub issue, it seems that two-way sync has not been fully implemented in the Nextcloud Android app yet. The key points are:
The Nextcloud Android app currently only supports one-way sync, where changes from the server are propagated to the local device, but changes made on the device are not automatically synced back to the server.
There are several comments from users requesting the implementation of true two-way sync, where changes made on either the server or the local device are automatically synced to the other side.
The issue has been open since 2016, and while some progress has been made (e.g. propagating file content changes to the other side), the full implementation of two-way sync for adding/removing files, file renaming, etc. is still incomplete.
The official Nextcloud Android app documentation from 2017 still claims the app offers two-way sync, which seems to be inaccurate based on the current state of the feature.
So in summary, two-way sync has not been fully enabled in the Nextcloud Android app yet, despite being a highly requested feature. The development team appears to be working on it, but it has not been completed and released as of the latest comments in the GitHub issue, which are from 2023.
did you load all the docuement? how many comment does it hold?
Yes, I have loaded all the available information provided. The document contains 9 comments or data entries.
no. it should contains more than 120 posts.
Here is a summary of the key points from the provided information:
The Nextcloud Android app currently only supports one-way synchronization, where changes made on the server are propagated to the local device, but changes made on the device are not automatically uploaded back to the server. Users have been requesting the ability to have two-way synchronization for years.1
The desired behavior for the Nextcloud Android app is:
Files added to a synchronized folder should be recognized and synced.
Changes to files (create, update, delete) in a synchronized folder should be propagated back to the server.
Conflicting changes should trigger a dialog to allow the user to choose how to resolve the conflict (overwrite on device/server, rename).1
Several users have expressed frustration that the Nextcloud Android app does not have proper two-way synchronization, despite the official documentation claiming it has "automatic synchronization of your files".1
Workarounds like using Syncthing in addition to the Nextcloud app have been suggested, but these have their own limitations and drawbacks.1
The issue has been open for several years, with users continuing to request this essential feature. Some have even contributed funds to a bounty in hopes of incentivizing the development of this functionality.1
There is no clear indication from the Nextcloud developers whether this feature is planned or if/when it might be implemented. Users are asking for transparency on the roadmap for this feature.
In summary, the Nextcloud Android app is lacking a critical synchronization capability that users have been requesting for a long time. The lack of two-way sync is a significant limitation of the app compared to the desktop client and other cloud storage solutions.
what are the date of the comments?
Based on the information provided in the passages, the dates of the comments are:
2023-05-01T15:48 (by ahcheing)
2019-10-15T09:13:59Z (by LiZhenhuan1019)
2022-01-07T23:25:26Z (by IzzySoft)
2022-12-03T18:55:28Z (by Ellpeck)
2023-06-03T18:39:36Z (by clragon)
2022-01-15T21:55:37Z (by ThomasSteinbach)
2018-07-04T13:34:50Z (by BentHaase)
2023-11-23T10:02:15Z (by phpbg)
2022-11-06T20:26:10Z (by ahcheing)
2018-06-05T11:23:01Z (by thibaultmol)
The Summarizer should detect that some comment where not loaded and inform the reader that the content is truncated.
If it can, propose to load more comment. Or all comment. Especially on old still open issue.
This one seems to have recent update and proposed fix...