3 ms·
• Very likely the files are only .zip files for network portability, and when in their native environment (iOS?) they’re unzipped document bundles (see e.g. the
by derefr 9y ago
• Very likely the files are only .zip files for network portability, and when in their native environment (iOS?) they’re unzipped document bundles (see e.g. the RTFd format)
• Likely this file isn’t literally a PList, but the output of a data storage framework (e.g. CoreData) that uses PLists as one possible backend. In the code, it just looks like adding annotations to native data structures to make them “storable” within a database-like object.
• Only the text-formatted PLists contain base64’ed binary data. The binary-formatted PLists just contain length-prefixed binary data. There isn’t the “binary in base64 in XML in binary” that you’re imagining.
- jvns 9y agothanks for this!! I've never worked with iOS so I was definitely fumbling in the dark. the CoreData hypothesis explains why the PList file looks like a huge weird unstructured array! So in the code there's just some object with all the data in it and then CoreData serializes that object? This explains the feeling throughout of "this doesn't feel like a format the app developer designed".