writeToFile NSData question?

[orange gold]

I was writing and reading files just fine on the simulator.. saving them to my computers HardDrive..

My code:

stringByAppendingPathComponent:@"/savedFile1.txt"];
myString = [[NSString alloc] initWithFormat:@"test"];
[myString writeToFile:path atomically:YES encoding:NSUTF8StringEncoding error:NULL];

When I switched over to the iPhone it wouldn't work so I assumed I had to change the path...

Here is the current code I'm using but I'm having no luck, the app freezes and quits when I try to save:

paths = NSSearchPathForDirectoriesInDomains(NSDocumentDirectory, NSUserDomainMask, YES);
documentsDirectory = [paths objectAtIndex:0];
path = [documentsDirectory stringByAppendingPathComponent:@"savedFile1.txt"];
myString = [[NSString alloc] initWithFormat:@"test"];
[myString writeToFile:path atomically:YES encoding:NSUTF8StringEncoding error:NULL];

And my .h declarations:

NSArray *paths;
NSString *documentsDirectory;
NSString *path;
NSString *myString;

What should I do?
(also are there any frameworks I need for this?)

[smithdale87]

#1. When your app crashes, there should be some info in the debug console. Can you post that please?

#2. The writeToFile: method has an error parameter. You can use it to get more specific info about when the writeToFile fails.

[MattW]

Why are you trying to initialize your myString variable with no data?

[orange gold]

Sorry that was a copy and paste error..

Originally Posted by MattW

Why are you trying to initialize your myString variable with no data?

[MattW]

Originally Posted by orange gold

Sorry that was a copy and paste error..

Then refer to smithdale's post.... also, put a breakpoint in that function; step through and see exactly which line is crashing your app.

[orange gold]

Originally Posted by MattW

Then refer to smithdale's post.... also, put a breakpoint in that function; step through and see exactly which line is crashing your app.

unfortunately my NSLog is broken... when I got the new xCode it stopped working.. I can't display the errors with ease /:

[smithdale87]

How is it possible to break NSLog? Have you tried stepping through your code in the debugger then to see which line makes the app go boom?

[MattW]

Originally Posted by orange gold

unfortunately my NSLog is broken... when I got the new xCode it stopped working.. I can't display the errors with ease /:

I didn't say use NSLog.... I said use a breakpoint. They are invaluable for debugging.

[MattW]

Originally Posted by smithdale87

How is it possible to break NSLog? Have you tried stepping through your code in the debugger then to see which line makes the app go boom?

But yes, good point! How do you break NSLog??!!

[Duncan C]

Originally Posted by orange gold

unfortunately my NSLog is broken... when I got the new xCode it stopped working.. I can't display the errors with ease /:

I bet it's not broken. I bet you can't find the debug console, since just about everything about Xcode 4 is different from Xcode 3, in a different place, works differently, etc.

In XCode 4 you have to show the debug area (Command 5), and then click the right cryptic little symbol at the top of the debug area:

[orange gold]

No, the phone doesn't return anything to my debugger.. it only works for the simulator. but yeah, xcode 4 does have alot of re-arranging... Does anyone know what path I need to use for writeToFile? ....


My 666th post

[MattW]

Originally Posted by orange gold

No, the phone doesn't return anything to my debugger.. it only works for the simulator. but yeah, xcode 4 does have alot of re-arranging... Does anyone know what path I need to use for writeToFile? ....

Put a breakpoint in the function. Step over each line. Check the variables, see what's going on.

[orange gold]

The app freezes when I try to "writeToFile"

[MattW]

Originally Posted by orange gold

The app freezes when I try to "writeToFile"

But what information do you get from the debugger when you step over that line? And, before you step over that line, are the values in your variables what you expect them to be?

[orange gold]

They are the correct values... my debugger isn't working ahhhh this is annoying ahhaha! Maybe I just need to find some source code for writeToFie and copy it...

[MattW]

Originally Posted by orange gold

They are the correct values... my debugger isn't working ahhhh this is annoying ahhaha! Maybe I just need to find some source code for writeToFie and copy it...

Wait a minute... NSLog is 'broken' and your debugger 'isn't working'? This sounds very strange. Are you sure you're running in XCode? And if you are, do you actually know how to use it?

[orange gold]

Haha, yes I am (:0
My phone doesn't send anything back to the computer because when I launch the app ever since I updated to the new xcode it loads it on but never launches it so I have to manually open the app on the phone and by then it is not connected to xcode's debugger anymore...

On another note I followed this example code: http://www.cocoanetics.com/2009/03/g...tandard-paths/

It no longer freezes when I write to file but when I try to load the file nothing comes up which makes me think that it isnt actually writing or my loading method is wrong..

Here is how I load an html file I "wroteTo" using the writeToFile code:

[myWebView loadRequest:[NSURLRequest requestWithURL:[NSURL fileURLWithPath:[[NSBundle mainBundle] pathForResource:@"testHTMLfile1" ofType:@"html"]isDirectory:NO]]];

This worked on the simulator when I was just writing to the hard drive..
Now that I am writing to a file in the resources folder using my "paths" variable it no longer works..
But I still haven't confirmed wether the loading isnt working or the writing isnt working or neither are, all I know is the writing doesnt freeze the app anymore. (by freeze I mean exit sigabrt)


/:

[orange gold]

AHHHH!!! you can't writeToFiles in your resources folder! you have to write to files in your directory! A person answered on another forum and gave example code that worked perfectly!
YAY!

[MattW]

Please heed this advice: find out why your debugger no longer works and fix it. Without a debugger you are going to have a massively uphill struggle while developing any type of software.