bad access about toast

[scalessec]

What iOS version? Are you using ARC? I will address it this evening. Thanks

[kraag22]

i'm using ARC. iOS version 5.1

[scalessec]

I was unable to reproduce this crash. Are you using a navigation controller? I loaded a root controller in a navigation controller, displayed a toast message in the root controller's view, and then pushed a new controller without error (iOS 5.1, ARC, simulator and device). I also simulated a memory warning after pushing the controller to unload the root controller's view and still I didn't experience a crash.

Can you give me more details about your implementation?

[kraag22]

I'm not using navigation controller. I'm redirecting with

scAppDelegate *appDelegate = (scAppDelegate *)[UIApplication sharedApplication].delegate;
RMMController *controller = [[RMMController alloc] init];

appDelegate.window.rootViewController = controller;
[appDelegate.window addSubview:[controller view]];
[appDelegate.window makeKeyAndVisible];

[skela]

kraag22: a small tip here, but if u were to add the toast to the app delegate's window instead of a view controllers view, u wont have to worry too much. a view controllers view comes and goes, a window lasts forever (almost :P)

[scalessec]

@kraag22 , your problem is that you're trying to switch screens without some navigation structure. @skela, generally it's bad practice to add directly to the window unless you really need too, because it defeats the purpose of a view hierarchy. But yes, that would work.

[skela]

@scalessec allthough i agree in general that adding to the window directly has to be done with care, but your Toast classes clean themselves away when done + its the only way to guarantee similar behaviour as in android, i.e. when you change screens, the Toast stays visible.