Alex Lance

Ah ok - then the newer version I just patched isn't going to be much good for you. Revert back to the original one here: https://raw.githubusercontent.com/alexlance/signal-message-exporter/master/signal-message-exporter.py Feel free to post...

I think maybe the parent application signalbackup-tools didn't extract those attachments into files for some reason.

signalbackup-tools pulls out all the file attachments (MMSes) and dumps them as files into the `bits` folder. It sounds like it skipped over those 56 files for some reason...?

Unfortunately I'm not sure how groups are modelled in MMSes - it's possible that someone could perform a standard sms/mms export via SMS Backup and Restore, then find some group...

Perfect thank you! I've pushed a change which should make the `address` field a tilda-separated list of phone numbers and the `contact_name` field a comma-separated list of names. No guarantee...

This was the change I added: https://github.com/alexlance/signal-message-exporter/blob/90d5ca5598fd427ad704b8c11584ca8184ac7e50/signal-message-exporter.py#L142

Re 1. I've just pushed some code which removes a bit of error suppression - if you download the latest version and run it again - an error will occur...

There's something a bit weird with determining who the sender is when it comes to group messages. There's a field on each MMS and it states who receives the message....

> Just the same errors with attachments as before. This is definitely the same "older" backup file that we were working with earlier? No file attachments at all? Quite sure?...

Anecdotally: we got bitten by this recently. We have a task definition that comprises of one container serving web requests (the "essential" container), and several worker containers that weren't marked...