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
Restore all backed up SMS from a 4.x Android to a new and empty 10 Android (LineageOS, /e/), using custom IMAP server.
Actual behaviour
When restoring, identification step passed, then stopped with a UID SEARCH 1:* (HEADER X-SMSSYNC-DATATYPE "SMS") UNDELETED; response: #4# [BAD,UID SEARCH bad parameters] message
Steps to reproduce the behaviour
Save all SMS from the 4.x Android phone with custom IMAP configuration in the "SMS" folder (the save settings left as it is)
Install the app on the new phone (/e/ OS on Fairphone 3)
Configure IMAP settings
Launch recovery
Please specify the following:
Android version : 10 (Lineage OS /e/)
Phone model / brand : Fairphone 3+
SMS Backup+ version installed : 1.5.11
Messaging app : (please specify the software that you usually use to read & send SMS & MMS messages)
sms_backup_plus/.log is empty
The text was updated successfully, but these errors were encountered:
Have you set the IMAP "folder" (Gmail "label") to match the previous installation that you want to restore from?
If not, it's likely that there are no messages in the folder/label that's actually used, so that the range 1:* is invalid, because there's no message numbered "1".
I have a similar problem, where the server logs show: Error: FTS Xapian: Unknown header 'x-smssync-datatype'.
Perhaps it would be useful to support iterating items without relying on this header being searchable.
Expected behaviour
Restore all backed up SMS from a 4.x Android to a new and empty 10 Android (LineageOS, /e/), using custom IMAP server.
Actual behaviour
When restoring, identification step passed, then stopped with a
UID SEARCH 1:* (HEADER X-SMSSYNC-DATATYPE "SMS") UNDELETED; response: #4# [BAD,UID SEARCH bad parameters]
messageSteps to reproduce the behaviour
Please specify the following:
sms_backup_plus/.log is empty
The text was updated successfully, but these errors were encountered: