Number 1: I would suggest to have the user solve any conflict issues and use time stamps down to the second, if using timestamps. That is the reason I came over to this app. I have already experienced issues with apps not working on newer versions of Android with no possibilities of updates.
Only my 5 cent, I hope I'm not completely wrong and I'm upset that I can't program and help.Īh, I was thinking that it would just stop working for some reason inside the code. Option 1 or a similar solution should be implemented with #1309. => Disadvantage: If you have no access to cloud storage the MMEX app can not be used. But also that has been so far.ĭo not use a local version of the mmd file, only the one stored in the cloud. Ii) If the clock of a device is going wrong it is not work anymore. I) In any case, there is a risk of losing changes, because not the content, but only the change date is compared. For me it looks like the app detects a conflict between the locally stored mmd (/storage/emulated/0/MoneyManagerEx/test.mmd) and the mmd file in the cloud and can't handle it.įrom my point of view there are two possibilities:Ī) app detect that local file is more actual as the cloud version => copy local file to cloud folderī) app detect that cloud file is more actual as the local version => copy file from cloud folder to local folderĬ) app detect that both files are equal up to date => show message and ask which version (local or cloude) should be used
0 kommentar(er)
