cache:// #716

Merged
merged 2 commits into from Sep 5, 2012

Conversation

Projects
None yet
3 participants
Contributor

clarketus commented Nov 4, 2011

Hey guys

I just got an app rejected saying I was storing information in the /Documents folder that I should be storing in the /Library/Caches folder

From their rejection notice:
"For example, only content that the user creates using your app, e.g., documents, new files, edits, etc., may be stored in the /Documents directory - and backed up by iCloud. Other content that the user may use within the app cannot be stored in this directory; such content, e.g., preference files, database files, plists, etc., must be stored in the /Library/Caches directory."

So this is fine, I went to move the locations where my application stored files, but I then noticed I was displaying some of these files inside a TTPhotoViewController. I was previously using documents:// to access the files, and had no easy way to access them now they were in the /Library/Caches folder

So, I have added cache:// to the provided URL protocols. This could be a candidate for pulling into three20? If I should be doing this a different way, let me know.

Thanks!

Contributor

jwang commented Nov 5, 2011

Yea. that new change is going to catch a lot of people now. Thanks will take a look at this. :)

jwang was assigned Nov 15, 2011

Contributor

clarketus commented Sep 4, 2012

Hey

Is there any chance this can get merged? Or should I close this.

Thanks

Contributor

diederich commented Sep 5, 2012

Hi thanks for the pull request. There are some minor formatting changes in the diff, but I guess that's okay.
Merging...

@diederich diederich added a commit that referenced this pull request Sep 5, 2012

@diederich diederich Merge pull request #716 from clarketus/development
In addition to documents:// add an internal cache:// URL which allows easy fetching of data from ~/Library/Caches
1ce03bc

@diederich diederich merged commit 1ce03bc into facebookarchive:development Sep 5, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment