Congrats - problems with custom backup directory

Andrew Heard shared this problem 8 months ago
Solved

Mixed messages here

18fe8189a9ef2b8dabfe4bcf02eea072

My backup directory HAD been

ea9333c2dcd0399abaf9267b04111b60

But sometime very recently, and since last manual backup, LM4 had got completely confused and changed that directory to below

ce1ef67cddf68873deaeca511111f44b

Easy enough to fix but not sure why LM changed it.

Replies (2)

photo
1

Hello,

Locus didn't change anything, the path of the route really looks like that in real. The previously displayed version is shortened and trimmed, but both mean the same.

Anyway, if the path looks like that, it means that Locus for some reason lost access to this directory. It sometimes happens when you restore a backup on a new device or when the app permissions are removed.

Anyway, the solution is to set the folder again and it should work properly.

About the toast message - yes, that should be "success" only when everything ends with the correct result, we'll take a look at it.

Regards,


Zdenek, Locus team

photo
1

>the path of the route really looks like that in real

content://com.android.provides.downloads.documents/tree/raw:?storage?emulated?0?Download?to-save?Locus?backup/document/raw:?storage?emulated?0?Download?to-save?Locus?backup

is the same as

/storage/emulated/0/Download/to-save/Locus/backup

really? with "Download/to-save/Locus/backup" in the path twice? weird

Anyway, nothing has been changed on the phone for months, so I have no explanation.

Yes, setting the folder again fixed the issue.

Leave a Comment
 
Attach a file