The problem with data synchronization and the cloud service is not the most frequent, but one of the most unpleasant is for sure. In this post, I will list the most likely problems and their solutions.
Information that is synchronized:
- * _db.db – database file
- preferences.xml – settings file
- time_last_changes.txt – file with brief information about the data – the number of records and the date of the last change. Information for displaying the synchronization status is taken from this file.
Problem #1 – the application shows that there are records in the cloud, but nothing appears during synchronization
By default, the application has entries (templates, categories, types of fuel) that are already stored in the database and their number is also considered.
- If you see that there are 76 (or so) entries in the cloud / on the device – you should know that these are standard entries.
- If more records are displayed, but nothing is synchronized anyway, the information file does not match the database file. This can happen when the synchronization is interrupted or the empty DB file is accidentally pushed into the clouds (from the second device, for example).
You should roll back the database file to the state when it was with a large number of records. This is possible through the web interface of the cloud (Dropbox or Google Drive both provide this option only through the browser). Here is an example procedure for the example of Dropbox.
When accessing a previous version of a file, you can do two things:
Roll back in the cloud and try to sync in the application on the device again
Copy the database file to the device in a specific folder and import through the application settings.
Problem #2 – the application crashes immediately when starting and starting synchronization
Turn off mobile Internet and Wi-Fi. The application at startup before trying to synchronize to check the availability of the network and in its absence will not try to synchronize anything.
Immediately after opening the application, the Internet can be turned on and off in the synchronization settings and disabled (then log in again, check the availability of the cloud profile in general).
In a particularly difficult case, you will have to start the synchronization settings with the Internet turned off, disconnect everything and restart the application.
Problem #3 – the application crashes when you exit it and try to synchronize data
For starters, you should check if the application has permissions to access memory (it also wants to work with backup files).
If everything is OK, you should check whether you can manually push data into the cloud through the synchronization settings.
If everything is pushed through the synchronization settings, but not automatically after exiting the application, the reason may be in the overly vigilant application manager of the device – it nails the synchronization process of the application that you just closed. He doesn’t know that the process is temporary and closes immediately after synchronization, he thinks that he is doing a good job and saves the device from an overly gluttonous process that consumes a battery in the background.