ps it is with
> useLayoutToLayoutNavigationTransitions? I haven't used that before.
>
> Anyway that should get you started.
>
> On May 20, 2015, at 7:45 AM, cocoa-dev-requ...@lists.apple.com wrote:
>
> >
> > ------
-
>
> Message: 1
> Date: Tue, 19 May 2015 23:46:28 -0500
> From: Luther Baker
> To: Cocoa Developers
> Subject: Collection Views Breaking
> Message-ID:
>
> Content-Type: text/plain; charset=UTF-8
>
>
On Wed, May 20, 2015, at 01:12 PM, Alex Zavatone wrote:
> Whaaa?
>
> The app throws an exception, but setting an exception breakpoint never
> gets triggered?
EXC_BAD_ACCESS is a hardware exception. It has nothing to do with a
software exception (the kind thrown by @throw or +[NSException raise],
Whaaa?
The app throws an exception, but setting an exception breakpoint never gets
triggered?
Anyway, you may find these helpful.
http://loufranco.com/blog/understanding-exc_bad_access
http://www.touch-code-magazine.com/how-to-debug-exc_bad_access/
Enabling NSZombies may help you track that d
Thanks Alex,
I have set an exception breakpoint but it never fires - and I will
experiment with popping the second view controller programmatically and
scrolling up.
I think this has to do with my elementary understanding of how
UICollectionViews are reused in this type of transition animation -
What if you issue the back programatically and then scroll up?
It would be interesting to see just what gets unwired here.
Have you set an exception breakpoint to tell you exactly what is breaking?
On May 20, 2015, at 12:46 AM, Luther Baker wrote:
> I've got a simple iOS project consisting of 2
I've got a simple iOS project consisting of 2 collection view controllers
and a navigation controller.
Tapping any item in the first collection view simply pushes the second
collection view on the stack.
Problem is, when I tap "< Back" and then manually scroll up ... the app
crashes with a EXC_BA
