• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Crash at iOS App Startup - What Could Have Gone Wrong?


  • Subject: Re: Crash at iOS App Startup - What Could Have Gone Wrong?
  • From: Alex Zavatone <email@hidden>
  • Date: Tue, 21 Apr 2015 09:19:29 -0400

To see if it is a storyboard issue, try setting the storyboard for the one that crashes to the one for the other device that doesn't crash.

Launch the app.  If it doesn't crash, then bingo, storyboard issue.  Fix your first view controller.  Look for empty IBOutlets or IBOutlets that point to more than one item.

If it still crashes, then GREAT!  It's not your storyboard and you can go back to looking in the code that gets called when the app gets started up.

I'm betting it's a storyboard issue.

GL.

Alex Zavatone


On Apr 21, 2015, at 7:43 AM, Michael Crawford wrote:

> I screwed something up.  If I can't fix it I can restore from backup.
> I'm too cheap to use git but I make regular tarballs.
>
> I spent some time monkeying around with Interface Builder.  My iPhone
> .xibs were mostly complete but my iPad quite incomplete, as a while
> back I ripped everything out to replace my original UI with a
> UINavigationController.
>
> Now I get a crash at startup.  It looks like an exception is thrown
> inside UIApplicationMain.
>
> The reason that I'd like to fix this rather than just backing out my
> code is that I haven't done much iOS coding for a while, and would
> like to come back up to speed.  What better way than screwing up my
> project?
>
> I can see that stuff like awakeFromNib and some other code is getting
> called here and there.  I speculate that an IBOutlet is nil; I've been
> adding assertions which has helped in the past but not yet for this.
>
> I will try guard malloc later.
>
> Yes I feel quite foolish even asking this here.
>
> --
> Michael David Crawford, Consulting Software Engineer
> email@hidden
> http://www.warplife.com/mdc/
>
>   Available for Software Development in the Portland, Oregon Metropolitan
> Area.
> _______________________________________________
>
> 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


_______________________________________________

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


  • Follow-Ups:
    • Re: Crash at iOS App Startup - What Could Have Gone Wrong?
      • From: Michael Crawford <email@hidden>
References: 
 >Crash at iOS App Startup - What Could Have Gone Wrong? (From: Michael Crawford <email@hidden>)

  • Prev by Date: Re: Crash at iOS App Startup - What Could Have Gone Wrong?
  • Next by Date: Re: Crash at iOS App Startup - What Could Have Gone Wrong?
  • Previous by thread: Re: Crash at iOS App Startup - What Could Have Gone Wrong?
  • Next by thread: Re: Crash at iOS App Startup - What Could Have Gone Wrong?
  • Index(es):
    • Date
    • Thread