Using the constant NSDocumentDirectory
will in fact get you /var/mobile/Documents when running a jailbreak app. It would be bad policy to dump your app's documents directly in there, even if you think they're named uniquely.
If you look at the contents of the /var/mobile/Library/ folder, you'll see that many apps have their data stored there, including jailbreak apps. It's not clear to me whether there's a handy constant like NSDocumentDirectory
that you can use to get that. But, you can always hardcode your source to look for files in @"/var/mobile/Library/APPNAME"
. It's unlikely that this folder will change (and if it does, it's probably going to break other apps, and is certainly an easy fix to make).
If you look at the document you link to, it does specify:
Appstore app has a Documents folder that is created by the
installation process. Jailbroken app does not. It is up to the app to
create its own folder. Should you need this type of folder, you must
create this with a simple mkdir command in your
applicationDidFinishLaunching function. Just add a simple function:
mkdir(“/var/mobile/Library/YOURAPPNAME”, 0755); If the folder already
exists, no harm done. You want to do this because the install process
runs as user root and the app runs as user mobile. If Cydia does this
for you then the folder will have the incorrect permissions.
... so you need to create that subdirectory yourself. It won't be there if you don't.
In my experience, writing jailbreak apps simply involves some of these slightly stinky coding practices (hardcoding paths and creating them ourselves) ... it might just be something we have to deal with.
Update: make sure to see Saurik's comment below.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…