Skip to content

Complaints of errors in Xcode 4.3 with the NSCachedURLResponse category - #29

Open
samstewart wants to merge 5 commits into
rs:masterfrom
upsight:master
Open

Complaints of errors in Xcode 4.3 with the NSCachedURLResponse category#29
samstewart wants to merge 5 commits into
rs:masterfrom
upsight:master

Conversation

@samstewart

Copy link
Copy Markdown

When using Xcode 4.3, a warning message is raised because of the overridden methods in the category on NSCachedURLResponse.

More Info:
http://www.iphonedevsdk.com/forum/iphone-sdk-development/99057-new-xcode-4-3-compiler-warnings-categories.html

We've written a simple wrapper instead which conforms to the NSCoding and NSCopying protocols and does not use categories. From our limited testing the approach seems to work and alleviates the error.

…onse instead of NSCachedURLResponse category smashing
@samstewart

Copy link
Copy Markdown
Author

After looking over diff a bit closer I noticed some company code. Let me isolate the fix first.

@samstewart

Copy link
Copy Markdown
Author

OK, removed the proprietary naming scheme so should be all ready to go. We included some other small fixes for code clarity, etc.

@samstewart

Copy link
Copy Markdown
Author

Re-added "lowercaseString" code in most recent commit

@samstewart

Copy link
Copy Markdown
Author

The recent commit fixes an error as described below:


The removal of the NSCachedURLResponse category means that NSKeyedArchiver will throw an EXC_BAD_ACCESS when attempting to load NSCachedURLResponse data. This means that this change requires a cache refresh, and a new cache key namespace that will prevent this from happening. Old cache keys will eventually be evicted from the system as new keys are populated.

rs pushed a commit that referenced this pull request May 11, 2012
- Disable SDURLCache at runtime if iOS version is >5 as this version
  now includes disk caching support
- Exchange category with a wrapper to add NSCoder protocol support
  to NSCachedURLResponse
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants