CODEWITHSUNDEEP
iosiphoneobjective-cnsstring
deanWombourne
deanWombourne

Reputation: 38475

NSString stringWithContentsOfFile failing with what seems to be the wrong error code

I'm trying to load a file into a string. Here is the code I'm using:

NSError *error = nil;
NSString *fullPath = [[NSBundle mainBundle] pathForResource:filename 
                                                     ofType:@"html"];
NSString *text = [NSString stringWithContentsOfFile:fullPath 
                                           encoding:NSUTF8StringEncoding 
                                              error:&error];

When passed in @"about" as the filename, it works absolutely fine, showing the code works. When passed in @"eula" as the filename, it fails with 'Cocoa error 258', which translates to NSFileReadInvalidFileNameError. However, if I swap the contents of the files over but keep the names the same, the other file fails proving there is nothing wrong with the filename, it's something to do with the content.

The about file is fairly simple HTML but the eula file is a massive mess exported from Word by the legal department.

Does anyone know of anything inside a HTML file that could cause this error to be raised?

Much thanks,

Sam

Upvotes: 17

Views: 29031

Answers (6)

Shailesh
Shailesh

Reputation: 3118

I ran into the same error.

When I played around a bit, it appeared that I was not including the file in copy bundle resources of the target.

I did that and it worked fine.

But, have to say -- error is quite misleading for such a simple cause. Just a bad guess from Xcode

Upvotes: 0

baowuwolf
baowuwolf

Reputation: 51

I had the same error with you ,use file name with [[NSBundle mainBundle] pathForResource:@"pageList" ofType:@"txt"]] good luck!

Upvotes: 4

Olie
Olie

Reputation: 24675

Don't know if this is your problem, but I just had a similar thing (stringWithContentsOfFile, no JSON), and the problem was that the file had CRLF (windows) line-endings and Western-whatever-it's-called encoding. I used SubEthaEdit to convert to LF and UTF-8, and everything works fine.

Upvotes: 0

Eli
Eli

Reputation: 4932

I've just spent 45 minutes with this problem, only in my case the solution was stupid and the problem slightly different.

  • I had a file called Playlist.txt in my resources directory. It was loading just fine.
  • The file was modified at one point, from within XCode.
  • The file stopped loading properly, with the same error as above. However, it had never been moved nor had its encoding type been changed.
  • I did a command-I (Get Info) on the file in the XCode directory, it told me it was UTF-8 (as expected).
  • I tried the "usedEncoding" way of reading files, no dice. Same error, encoding was return null.
  • Finally, I erased the file from XCode, dragged it in again, and did a Clean All. That fixed the problem.

This is not the first time that XCode magically caching things (incorrectly) has caused me hours and hours of wasted time. If you have an error like this which doesn't make sense, try removing and replacing files and cleaning all targets.

Upvotes: 10

Peter N Lewis
Peter N Lewis

Reputation: 17811

The error is almost certainly that your file is not in UTF-8, but you're right, that does sound like a bug in the error report.

Open the eula file up with BBEdit (or the free TextWrangler) and see what encoding it uses. Change the encoding to UTF-8 and save it. Diff the two files to see what differences have appeared. Replace the original file with the new one (fixing any glitches).

If that resolves the problem, then use the Apple Bug Reporter to report the bug in the error report.

Upvotes: 8

Naaff
Naaff

Reputation: 9333

The most likely reason that +stringWithContentsOfFile:encoding:error: would fail in this case would be if you provided the wrong encoding. Are you sure that your @"eula" file is UTF8 encoded?

If you're unsure about the encoding of the file, you could always try +stringWithContentsOfFile:usedEncoding:error: instead and see if it works and what encoding it comes up with.

Upvotes: 3

Related Questions