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
As hinted here I can confirm that messages containing spaces in the "address" field are not imported by the current version 2.4.0.
For me this was quite a big issue, as lots of messages had their addresses formatted like "0123 4567890".
I'm submitting it as a separate issue so people can find it easier via the search function.
Here's the workaround that worked for me:
Extract messages.ndjson for the .zip file created by the backup function
Search and replace with a matching regex. I used search for ([0-9]{3,6}) ([0-9]{6,10}) and replace by \1\2 in xed.
Save the file and zip it again together with the "data" folder from the original zip.
Import this newly created zip file
Would love to see this fixed in an upcoming version.
The text was updated successfully, but these errors were encountered:
dnfoo
changed the title
Import not complete, some messages missing depending on phnone number format
Import not complete, some messages missing depending on phone number format
Aug 24, 2024
Don't skip messages whose addresses contain spaces upon insertion.
Commit 2f07074 (don't insert SMS messages whose addresses contain
spaces, since they're assumed to be group SMS messages which we don't
know how to handle correctly) introduced a regression of single
recipient SMS messages whose addresses contain spaces being skipped upon
insertion. Revert this change.
Addresses: #159, #205, #128
As hinted here I can confirm that messages containing spaces in the "address" field are not imported by the current version 2.4.0.
For me this was quite a big issue, as lots of messages had their addresses formatted like "0123 4567890".
I'm submitting it as a separate issue so people can find it easier via the search function.
Here's the workaround that worked for me:
Would love to see this fixed in an upcoming version.
The text was updated successfully, but these errors were encountered: