Re: Crash at iOS App Startup - What Could Have Gone Wrong?
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
- Subject: Re: Crash at iOS App Startup - What Could Have Gone Wrong?
- From: Michael Crawford <email@hidden>
- Date: Tue, 21 Apr 2015 12:43:18 -0700
It's not stopping in the debugger anymore, but instead of getting my
navigation controller I'm just getting a black screen.
I think all these problems arose by starting with an app that did not
use a nav controller, then - incorrectly - refactoring it so it did
use one. It looks like I left some stale configuration in there.
When I tried to fix that, that's when I started getting the crashes.
Now I'm backing up, trying to recreate the navigation controller at
the beginning.
Michael David Crawford, Consulting Software Engineer
email@hidden
http://www.warplife.com/mdc/
Available for Software Development in the Portland, Oregon Metropolitan
Area.
On Tue, Apr 21, 2015 at 12:36 PM, Mike Abdullah <email@hidden> wrote:
>
>> On 21 Apr 2015, at 19:13, Michael Crawford <email@hidden> wrote:
>>
>> OK I'll set up a git repository, but I'd like to fix this first.
>>
>> I think my MainWindow.xib got misconfigured or corrupted, so I made a new one.
>>
>> I have a UINavigationController with a custom class inside it called
>> LifeIPhoneViewController. Inside the latter is a LifeView as well as
>> some controls - to start and stop the animation etc.
>>
>> If I don't assign a root view controller to the initial window I get a
>> blank white screen as well as an NSLog that informs me that a root
>> view controller is expected by the end of startup.
>>
>> If I assign either the UINavigationController or the
>> LifeIPhoneViewController to be the window's root view controller I get
>> a crash.
>>
>> I'm going to try replacing the LifeIPhoneViewController with a plain
>> vanilla UIViewController that doesn't do anything.
>>
>> My .xibs are a mess because they evolved organically. What I'd like
>> to get out of this is not so much a running application as a neatly
>> designed and implemented one.
>
> You're clutching at straws, hoping you can just guess what the problem is. Stop.
>
> Xcode is clearly showing you there's an issue, yes? What exactly is that issue? Are you stopping in the debugger? If so, what's the stack trace there? Is there anything in the console?
>
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden