Re: Crash at iOS App Startup - What Could Have Gone Wrong?
FWIW, I successfully used for years svn on a file:// repository with the directory pointing to Dropbox. It works and you can check it out from different machines (I happened to have a desktop and a laptop). But I also suggest to move to git... > Il giorno 22/apr/2015, alle ore 00:17, Alex Zavatone ha > scritto: > > You can set up the server locally! > > On Apr 21, 2015, at 4:04 PM, Michael Crawford wrote: > >> I'm adept with svn. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
I have it mostly working now. Thanks for your help. tl;dr: my .xib's were really messed up, it probably should never have worked but the problems became more apparent when I refactored a single large, rather messy source file. In the beginning I did not use a Navigation Controller; I "added" that later however I left in a .xib that I should have deleted. In addition I implemented the Nav. Con. only for iPhone, it was when I went to add support for iPad that everything went south. It was helpful and informative to validate my IBOutlets with assertions. Now my code has lots of assertions, I can leave them there maybe they'll find trouble later. I found what I believe to be an XCode 6.2 bug, I will file a report after I regress it a but more. I had a custom called called "LifeIPhoneViewController", but when I entered the name, it was always saved as "UIViewController". Once I noticed the problem I was completely unable to get the exact text "LifeIPhoneViewController" to stick; "LifeIPhone" was OK, as was any length of string that started with an alphabetic character. "LifeIPhoneViewControlle" without the final "r" would be saved. Not noticing this for quite a long time was a good part of my problem. I moved back to XCode 6.0.1 until I resolved it. I renamed that class to "LifePhoneViewController". I think the text field is attempting to validate the entered text but getting very confused somehow; or maybe it is inappropriate code reuse, in that something that wasn't meant to validate really is. I managed to borrow the $99.00 for The Apple Tax. I'm going to a job fair tomorrow with twenty potential employers; I hope to demo Warp Life running on my iPad: http://www.warplife.com/life/ It is my take on the Cellular Automaton known as Conway's Game of Life; I've been into it since 1972. Thanks Again, Mike -- Michael David Crawford, Consulting Software Engineer mdcrawf...@gmail.com http://www.warplife.com/mdc/ Available for Software Development in the Portland, Oregon Metropolitan Area. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
> On 21 Apr 2015, at 21:43, Michael Crawford wrote: > > It's not stopping in the debugger anymore, but instead of getting my > navigation controller I'm just getting a black screen. That sounds like a good time to use Xcode’s view debugger to find out what’s actually onscreen. I’m going to hazard a guess you’ve got a blank window with no other content. > > 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 > mdcrawf...@gmail.com > http://www.warplife.com/mdc/ ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
You can set up the server locally! Your local box is the server and you just use time machine back up your repo, or just host the repo on a file share from another machine, mount the volume and use that as the repo. On Apr 21, 2015, at 4:04 PM, Michael Crawford wrote: > I'm adept with svn. > > What I didn't want to do was set up a server; it simply didn't occur > to me to have a local repository. > > I've configured svn repositories a few times, it is a PITA. > Michael David Crawford, Consulting Software Engineer > mdcrawf...@gmail.com > http://www.warplife.com/mdc/ > > Available for Software Development in the Portland, Oregon Metropolitan > Area. > > > On Tue, Apr 21, 2015 at 1:00 PM, Alex Zavatone wrote: >> >> On Apr 21, 2015, at 3:43 PM, Michael Crawford wrote: >> >>> It's not stopping in the debugger anymore, but instead of getting my >>> navigation controller I'm just getting a black screen. >>> >> >> And this points to your first view controller being the problem. >> >> It appears that you now have a nav controller that loads an empty view >> controller - or nothing at all. >> >>> 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 >>> mdcrawf...@gmail.com >>> 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 >>> wrote: > On 21 Apr 2015, at 19:13, Michael Crawford 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 (Cocoa-dev@lists.apple.com) >>> >>> 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: >>> https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com >>> >>> This email sent to z...@mac.com >> > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com > > This email sent to z...@mac.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
> On Apr 21, 2015, at 1:04 PM, Michael Crawford wrote: > > I've configured svn repositories a few times, it is a PITA. Me too, and I agree. Leave SVN behind and learn Git or Mercurial; they are so much nicer to use. There’s a bit of a learning curve* but they will save you so much time and aggravation in the long run. —Jens * slightly more so with Git, but on the other hand the Xcode integration is handy, and Git is more popular so it’s easier to get help. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
I'm adept with svn. What I didn't want to do was set up a server; it simply didn't occur to me to have a local repository. I've configured svn repositories a few times, it is a PITA. Michael David Crawford, Consulting Software Engineer mdcrawf...@gmail.com http://www.warplife.com/mdc/ Available for Software Development in the Portland, Oregon Metropolitan Area. On Tue, Apr 21, 2015 at 1:00 PM, Alex Zavatone wrote: > > On Apr 21, 2015, at 3:43 PM, Michael Crawford wrote: > >> It's not stopping in the debugger anymore, but instead of getting my >> navigation controller I'm just getting a black screen. >> > > And this points to your first view controller being the problem. > > It appears that you now have a nav controller that loads an empty view > controller - or nothing at all. > >> 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 >> mdcrawf...@gmail.com >> 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 >> wrote: >>> On 21 Apr 2015, at 19:13, Michael Crawford 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 (Cocoa-dev@lists.apple.com) >> >> 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: >> https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com >> >> This email sent to z...@mac.com > ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
On Apr 21, 2015, at 3:43 PM, Michael Crawford wrote: > It's not stopping in the debugger anymore, but instead of getting my > navigation controller I'm just getting a black screen. > And this points to your first view controller being the problem. It appears that you now have a nav controller that loads an empty view controller - or nothing at all. > 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 > mdcrawf...@gmail.com > 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 wrote: >> >>> On 21 Apr 2015, at 19:13, Michael Crawford 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 (Cocoa-dev@lists.apple.com) > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com > > This email sent to z...@mac.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
Hell, Xcode sets Git up for you for free, but I wrote the docs on how to set up and use SVN. If he wants, I'll be happy to send the SVN docs, but the Git tutorials are more than good and Git is a good step forward. On Apr 21, 2015, at 2:15 PM, Marco S Hyman wrote: > On Apr 21, 2015, at 5:35 AM, Michael Crawford wrote: >> >> The reason I haven't been using version control is that I prefer to >> operate my own servers - but then I have to set them up, and it's >> quicker just to roll a tarball. > > Huh? Nothing about a version control system limits your use of your own > servers. Pick one you can live with and use it. git, svn, mercurial, cvs, > old rcs, whatever. Doesn’t cost anything more than the time to download > and install. With Xcode you’ve already got git (and svn?). > > Use of version control make answering the “what the hell did I change that > caused that to happen” question trivial to answer. Commit early and often. > > Roland King wrote > >> Have you set an exception breakpoint which fires at the time the exception >> is thrown, if there is an exception? That helps sometimes. > > And if you do have exception breakpoints enabled check to be sure that you are > only breaking on Objective-C breakpoints. > > Marc > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com > > This email sent to z...@mac.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
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 mdcrawf...@gmail.com 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 wrote: > >> On 21 Apr 2015, at 19:13, Michael Crawford 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 (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
> On 21 Apr 2015, at 19:13, Michael Crawford 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 (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
On Apr 21, 2015, at 5:35 AM, Michael Crawford wrote: > > The reason I haven't been using version control is that I prefer to > operate my own servers - but then I have to set them up, and it's > quicker just to roll a tarball. Huh? Nothing about a version control system limits your use of your own servers. Pick one you can live with and use it. git, svn, mercurial, cvs, old rcs, whatever. Doesn’t cost anything more than the time to download and install. With Xcode you’ve already got git (and svn?). Use of version control make answering the “what the hell did I change that caused that to happen” question trivial to answer. Commit early and often. Roland King wrote > Have you set an exception breakpoint which fires at the time the exception is > thrown, if there is an exception? That helps sometimes. And if you do have exception breakpoints enabled check to be sure that you are only breaking on Objective-C breakpoints. Marc ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
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. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
> On Apr 21, 2015, at 5:35 AM, Michael Crawford wrote: > > The reason I haven't been using version control is that I prefer to > operate my own servers - but then I have to set them up, and it's > quicker just to roll a tarball. You don’t have to have a server to use Git. In fact it’s only going to use a server if you explicitly tell it to. Your project’s Git repository is local (in a “.git” directory in your project’s top level directory) and nearly all Git operations work directly with that embedded repository. You can commit revisions, diff, revert, branch, merge, etc. all within that local repo. (All of the above is also true of Mercurial, btw. Some people prefer it. In particular, the command syntax and feature set are more familiar if you’re used to SVN or CVS. Git has more of a learning curve.) **It is a no-brainer to use Git (or Mercurial) for everything.** If you create a project with Xcode, it’s just a checkbox to enable a Git repo. If you start a task using something else, it just takes one shell command (“git init”) to create the repo. Xcode has an OK GUI for working with Git, and the free app SourceTree has a better and more comprehensive one, so you barely ever need to use the command line if you don’t want to. —Jens PS: Even if you want to use Git with a server, it doesn’t take much setup. Any box you can SSH into, which also has the Git command-line tools installed, will work. There’s no special “Git server” to set up. About all you have to do is (a) create a directory on the box to put your repos into, (b) figure out the right URL to use to point to that directory, and (c) learn how to use a few Git commands to set up a “remote” and push to it. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
> > Please do understand that I don't expect you to actually debug my code > from my vague descriptions. I'm just looking for encouraging words as > well as any kind of general principles like my own "use assertions > before using debuggers". If there’s an exception thrown in UIApplicationMain() there has to be *some* kind of stack trace. Just checking you do have the “hide all the bits of the stack trace which contain any useful information” slider all the way over to the right, right, so it shows everything and doesn’t try to guess what you want to see, usually incorrectly. Have you set an exception breakpoint which fires at the time the exception is thrown, if there is an exception? That helps sometimes. Clean build, in fact really clean build with the Cmd key to blow everything away. Old NIBs stick around and can be a sod to get rid of. Similarly resetting the simulator to wipe your app off it entirely gets you a known base state. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
I expect you are correct, however this project is so old it doesn't have a storyboard, it has a half-dozen .xibs for each of the iPhone and iPad. Checking for nil IBOutlets with assert() is helpful. Some of my code, I know it worked once but when I look at it now it doesn't make any sense at all. That would be OK but my plan is to release my source as Free Software, so that it will demonstrate my expertise to potential employers. If the program simply worked but I was going to close the source, that would be OK. But if the program works yet my code sucks, no one is going to want to hire me so I feel compelled to refactor it, and that lead to catastrophe. Please do understand that I don't expect you to actually debug my code from my vague descriptions. I'm just looking for encouraging words as well as any kind of general principles like my own "use assertions before using debuggers". -- Michael David Crawford, Consulting Software Engineer mdcrawf...@gmail.com http://www.warplife.com/mdc/ Available for Software Development in the Portland, Oregon Metropolitan Area. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
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 > mdcrawf...@gmail.com > http://www.warplife.com/mdc/ > > Available for Software Development in the Portland, Oregon Metropolitan > Area. > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com > > This email sent to z...@mac.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
I'm betting you 5 bucks it's in your storyboard. If the crash happens and the debugger doesn't point to things useful, it's likely in setting up the storyboard and in that, your first screen. 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 > mdcrawf...@gmail.com > http://www.warplife.com/mdc/ > > Available for Software Development in the Portland, Oregon Metropolitan > Area. > ___ > > Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) > > 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: > https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com > > This email sent to z...@mac.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
The reason I haven't been using version control is that I prefer to operate my own servers - but then I have to set them up, and it's quicker just to roll a tarball. My source code isn't so bad but looking over my .xibs just now, some of them don't make a whole lot of sense, I expect because they grew organically. I don't get a useful stack trace. I think what I should do is refactor my .xibs. Whatever that means. Thanks. -- Michael David Crawford, Consulting Software Engineer mdcrawf...@gmail.com http://www.warplife.com/mdc/ Available for Software Development in the Portland, Oregon Metropolitan Area. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
> On 21 Apr 2015, at 12:43, Michael Crawford wrote: > > Yes I feel quite foolish even asking this here. I reckon, regardless of our experience, that we have all been there from time to time. I know I have. My current approach is: 1. Use git even for trivia. 2. Use time machine and a NAS. 3. Use SourceTree (it’s free). 4. Use BitBucket (it’s free for small teams). This setup has seen me wiggle out of most of my screw ups. Jonathan ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Crash at iOS App Startup - What Could Have Gone Wrong?
> On 21 Apr 2015, at 13:43, 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. Golden rule of asking for debugging help here: post the stack traces etc. for your crash/exception/whatever. Otherwise we’re shooting blind. > > 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 Seriously, you call yourself a software engineer, but don’t use version control?! ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
