On Jun 20, 2011, at 8:21 AM, Jeff Kelley wrote:
> If you’re creating the web view in -viewDidLoad, you should probably release
> it and nil the pointer to it in -viewDidUnload, not -dealloc.
You need to do both. You aren't guaranteed that your -viewDidUnload method will
ever be called, so if yo
If you’re creating the web view in -viewDidLoad, you should probably release
it and nil the pointer to it in -viewDidUnload, not -dealloc.
Jeff Kelley
On Sat, Jun 18, 2011 at 12:19 PM, Matt Neuburg wrote:
> >"Important: Before releasing an instance of UIWebView for which you
> >have set a dele
>"Important: Before releasing an instance of UIWebView for which you
>have set a delegate, you must first set the UIWebView delegate
>property to nil before disposing of the UIWebView instance. This can
>be done, for example, in the dealloc method where you dispose of the
>UIWebView."
>
>The delega
On Jun 16, 2011, at 7:15 PM, G S wrote:
> The delegate for the UIWebView is set up in the XIB file; it's pretty
> hokey to have to intervene in code to then disassociate the view from
> its delegate. Also, there is no "dealloc method where you dispose of
> the UIWebView", because that's done auto
On Jun 16, 2011, at 7:15 PM, G S wrote:
> The delegate for the UIWebView is set up in the XIB file; it's pretty
> hokey to have to intervene in code to then disassociate the view from
> its delegate.
If the delegate object is being dealloced, it needs to clear the delegate
reference to it. I d
My app is crashing after the user presses the Back button in the
navbar to dismiss a page that has a UIWebView on it, before the Web
view has finished loading. The Web view subsequently tries call its
delegate to say that the content has finished loading. In the Apple
docs I see this:
"Important
