-
-
Notifications
You must be signed in to change notification settings - Fork 6.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deduplicate messages #780
Comments
I would like to see this feature implemented too. I guess a bunch of us have old sms backup files lying around that may contain duplicates and wait to be consolidated by importing. |
If you can afford to lose embedded media like pictures you could try the following route, @devurandom:
If you are now free of duplicates in your SMS app: win. Go ahead erase the messages in |
I'm interessted in that too.Even tried some aproaches... |
@McLoo seems like a good idea |
@McLoo Thanks for taking this on! Deduplicate on import is a very good step in the right direction. If someone wants to deduplicate the existing messages, he could hopefully use your code and submit a patch for an enhanced feature. |
Related user action: "I clicked the import button and while waiting I then clicked on the notification progress bar and it imported again. I assumed the notification bar would bring me to a different screen not kick off a load." https://gist.github.com/1fd6592e5848fb3a4e76163ee0e4da3a (though looks like this log may have been captured too late) |
GitHub Issue Cleanup: |
Currently TextSecure (2.0.1) can only import messages from the default Android SMS application once. Afterwards doing the same again results in duplicate messages. It would be nice to be able to deduplicate them.
I assume that going through the list of messages and comparing from, to, time and text would be sufficient. Then just delete everything except the first occurance.
Please excuse me, if this is a duplicate of another issue. It was hard to find good search terms, since "duplicate" occurs extremely often as "duplicate of issue #...".
The text was updated successfully, but these errors were encountered: