iMessage » blog.haraldkraft.de

Free iPhone text message extractor works with iOS 6

Life and People, Technical No Responses »

Oct 042012

Actually, the updated version of the SMS extractor for iPhone was already rolled out on September 25th, but I haven’t gotten around to blogging about this, so here goes.

Apple made a lot of changes to the SQLite container (especially field names and references) so I also had to apply a few changes to the extraction software. Unfortunately it is on a path of getting cluttered because there are many special cases. However atm I don’t have the time and motivation to turn this into a very clean program. For the time being it’s doing its job: extracting every single text message for free :).

XML support for free iPhone SMS extractor

Life and People, Technical No Responses »

Aug 152012

Even though this piece of software is doing a good job, it got a little rusty and features needed to be added. Also I had to do some small fixes.

The SMS extractor is now able to output the extracted text messages into an XML formatted file. The following example will show the format that is being used:

<?xml version="1.0" ?>

<messages>
	<message type="SMS">
		<address>0123 45678910</address>
		<time>09.05.2012 20:09:19</time>
		<text>This is an example text message.</text>
	</message>
	<message type="iMessage">
		<address>+49 123 45678910</address>
		<time>06.08.2012 18:54:17</time>
		<text>This is an example iMessage.</text>
	</message>
</messages>

<?xml version="1.0" ?>

<text>This is an example text message.</text>

</message>

<text>This is an example iMessage.</text>

</message>

</messages>

SMS extractor for iPhone now supports iMessages correctly

General, Life and People No Responses »

Mar 132012

It took me a while until I would finally face the issue about iMessages (and their date). The latest released version of the SMS extractor was able to deal with iOS 5 containers and would already also extract iMessages – however with a wrong date.

In order to fix this, I had to treat iMessages as a special case. Thing is, in order to still be able and deal with container files prior to iOS 5 (and the program stay universal), the fact whether iMessages can appear needs to be determined before the actual message retrieval is done. So far I’ve been too lazy to approach this issue, that’s why it took a while. (And yes, I hate legacy support, but I hate it even more when users are left out who don’t or can’t update for some reason!)