You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when Signal is writing its backup, it first creates a temporary file and then renames it. This rename dance appears to throw off some tools, namely Nextcloud and DAVx5's WebDAV share function. The result is Signal aborting the backup and partially uploaded files. I tested both apps on a recent Android 15 device, both failed to allow Signal/Molly to finish its backup . Now it's possible that both of these tools are simply buggy, but Signal is definitely not innocent either.
This is a known issue that has been around for years. Despite numerous affected people, Signal does not seem interestd in fixing it.
The fix could be as simple as:
Not create a temporary file, write into the final filename directly
or create the temporary file in a different location and then copy it over
or tweaking the timings to avoid whatever confuses these sync tools
Would Molly be interested in tackling this? Thanks a lot!
The text was updated successfully, but these errors were encountered:
Hello! Signal is overhauling their backups system and it seems they will be selling cloud storage. Not to worry, Molly plans to continue to allow local backups and make it practical for use with any cloud provider: mollyim#20.
Is there an existing request for this?
Feature description
Hello,
when Signal is writing its backup, it first creates a temporary file and then renames it. This rename dance appears to throw off some tools, namely Nextcloud and DAVx5's WebDAV share function. The result is Signal aborting the backup and partially uploaded files. I tested both apps on a recent Android 15 device, both failed to allow Signal/Molly to finish its backup . Now it's possible that both of these tools are simply buggy, but Signal is definitely not innocent either.
This is a known issue that has been around for years. Despite numerous affected people, Signal does not seem interestd in fixing it.
The fix could be as simple as:
Would Molly be interested in tackling this? Thanks a lot!
The text was updated successfully, but these errors were encountered: