-
I first tried using my MacOS backup, but I noticed in my first export that I got lots of "attachment does not exist!" errors in my html files. I had a hunch that maybe my MacOS device (which is new) didn't have my full message history downloaded from iCloud yet, so I switched to using an iOS unencrypted backup, following your instructions to point to the path. Same issue. I ran in diagnostic mode and got the following:
What would cause my database to be missing 33% of files? I understand this is probably not an issue with imessage-exporter but I'm hoping someone here can help me resolve this. My iMessages are backed up in iCloud -- maybe they weren't all downloaded to my device at the time of the backup? Is that something I can change? Or alternately, is there a way to get them all downloaded on my Mac OS system and run the export from that DB? For reference, here's what I see in diagnostic mode using my MacOS chat database. Seems like there are many fewer attachments total…
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Beta Was this translation helpful? Give feedback.
The difference between your macOS and iOS diagnostic data suggests an issue with iCloud sync, sadly there isn't much we can do to fix that. In the iMessage app, if you click the info button for a conversation and scroll down, there is a button to force it to download all of the attachments for that conversation:
On iOS specifically, Messages is probably more aggressive in not taking up storage with old attachments than macOS.
All that said, the issue you are experiencing with "Attachment does not exist!" in the HTML output indicates that you have rows in the
message
table that reference attachments, but there is no matching attachment stored in theattachment
table to insert into those m…