EXC_BAD_ACCESS on Swift 2.0

[yalantis]

EXC_BAD_ACCESS on Swift 2.0

[Bashta]

Had the same problem. Resolved by selecting the kolodaView in interface builder then in the identity inspector set the Class of the view to "KolodaView" and the Module to "Koloda"

[Bashta]

I have not such a problem. I am setting the delegate in code and all the delegate methods are being called properly.

[Bashta]

This is not the appropriate place.

[AEugene]

I updated Koloda repository to proper Swift 2.0 integration. I checked last version and there is no issues like this.

[Bashta]

Thank you will give it a try asap as i am currently using Koloda in one of my projects.

[Bashta]

Working fine on 7.0! Thank you a lot!

[RayanSaeed]

kolodaView.delegate = self

I have this line very clearly and 100% surely in my code.. But still the delegate methods are not getting called. Why is that?????

[AEugene]

1. Check outlets
2. Check the delegate methods
   You can see example in repository

[RayanSaeed]

1. Outlets checked.. Like literally a million times... The cards are showing up, so the dataSource is connected. But delegate methods are not getting called...

2. I've added println() statements inside this function
   func cardTapped(card: DraggableCardView) {
   let index = currentCardNumber + find(visibleCards, card)!
   println("The card was tapped and delegate is (delegate)")
   delegate?.kolodaDidSelectCardAtIndex(self, index: UInt(index))
   }

and this is what prints out when I tap the card.. "The card was tapped and delegate is nil"

[RayanSaeed]

@AEugene I've attached a screenshot in the last comment also.. I will be really thankful. If you could just just take out 5 minutes. Please

[AEugene]

@RayanSaeed Issues should be fixed with #41

[RayanSaeed]

@AEugene Okay.. That's good but actually I'm using Xcode 6.4 as of now, and can't update to Koloda 2.0.1.... So can you please suggest me what to do now?? or how can I update my project so that this issue is fixed and project doesn't break...

[AEugene]

@RayanSaeed I didn't encounter this issue on versions for swift 1.2. And you're writing in unrelated to your issue thread.

[RayanSaeed]

@AEugene So should I create another issue for this?? Will you reply there?? Because I don't know if I'll get hold of someone from Yalantis because you can understand and solve my problem like no one else...

[Kourghan]

Hello @RayanSaed!
Yes, it's better to create another issue for your problem.
However soon we are going to drop support issues on swift version under 2.0 (starting from Xcode 7.0).

[RayanSaeed]

@Kourghan Okay then actually I'm already downloading Xcode 7 (1.64/3.59GB done).

But can you help me with #40 ??

[Kourghan]

@RayanSaeed Sure, I'll check it.
Closing this one.