Home/ Questions/Q 97685
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-11T00:03:08+00:00

From what I understand of the SDK, this exception is raised when the bindings

  • 0

From what I understand of the SDK, this exception is raised when the bindings in IB are not proper. But in my case, the view is loaded fine for the first two times. I then move back from the view using the NavigationController.

The third time when I try to open the view, I get this exception. The fact that it opens correct the first two times, means the bindings are correct and the view is fine! But then why does it fail the third time?

Any pointers? Thanks.

I am calling -initWithNibName:bundle: to initialize the view which is created in IB. Not calling the -loadView method.

It is not getting garbage collected. AFAIK, there is no garbage collection in iPhone SDK and we need to dealloc stuff explicitly.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. You may be running low on memory, which forces the system to send out low-memory messages to instantiated view controllers. The default implementation of -didReceiveMemoryWarning clears out the view member variable. In theory, then next time the view is required, it should be re-instantiated, but you may have overridden something that’s preventing that.

    • 0