Import Failed
Troubleshoot data import issues and successfully restore your cycle history.
Quick Fix
Most import failures are caused by using an unsupported file format or a corrupted file. Make sure you're using an .lova or .json file exported from Lova, and that Lova is updated to the latest version.
1 Supported Import Formats
Lova can restore data from this source:
Lova backup (JSON)
A backup file created by Lova itself
Other apps
2 Common Error Messages
| Error | Solution |
|---|---|
| File format not supported | Ensure file is .lova or .json format |
| Corrupted backup file | Try a different backup or older version |
| Incompatible version | Update Lova to the latest version |
| Insufficient storage | Free up space on your device |
| Permission denied | Grant Lova access to files/storage |
3 Step-by-Step Troubleshooting
- 1
Verify the file format
Check that your file has .lova or .json extension
- 2
Update Lova
Ensure you have the latest version from your app store
- 3
Check file permissions
Grant Lova access to files/storage in device settings
- 4
Free up storage
Ensure you have at least 100MB free space
- 5
Try a different backup
If available, use an older backup file
4 Encrypted Backup Issues
If importing an encrypted .lova backup:
Wrong password
Double-check the password you used when creating the backup. Passwords are case-sensitive.
Forgotten password
Unfortunately, encrypted backups cannot be recovered without the password. This is by design for your privacy.
Password Recovery
5 Alternative Import Methods
If file import doesn't work, try these alternatives:
QR Code Sync
Transfer data directly from another device running Lova using QR code pairing
Manual Entry
If you have limited history, manually enter your recent cycle dates
Still Not Working?
If import still fails:
- Share the backup file and error message on GitHub
- Include your device model and Lova version
- We may be able to help recover your data