Comments on: MKDotBounceAnimation animationDidStop bug

By: LKRaider

LKRaider — Fri, 12 Aug 2011 04:27:09 +0000

@TheoJohn:
To call removeAllAnimations you need to add QuartzCore.framework to your project and import CALayer.h to gain access to it.

By: Nils

Nils — Sat, 06 Aug 2011 22:09:08 +0000

It’s “programmatically” not “problematically”, though.

By: Tuyen Nguyen

Tuyen Nguyen — Thu, 23 Jun 2011 16:58:19 +0000

Thanks so much. This works for me.

By: TheoJohn

TheoJohn — Tue, 14 Jun 2011 14:35:30 +0000

None of these solutions work, just like 99.9% of all answers people give on the internet. removeAllAnimations is not a method that exists for MKMapView, not sure how anyone could say that one is working. Performing the delayed release only gives the trying to release an already released resource.

By: Joshua

Joshua — Tue, 25 May 2010 04:09:57 +0000

Nick actually disabling user location allows the user location annotation to be added when you repopulate the annotations. Thats good stuff!

By: Nick

Nick — Mon, 03 May 2010 15:34:46 +0000

Rather than a specific layer this should just pull all you annotations. Turning of showsUserLocation afterward might border on superstition but I do it anyway.

[self.mapView removeAnnotations:self.mapView.annotations];
self.mapView.showsUserLocation = NO;

By: Will

Will — Fri, 30 Apr 2010 05:40:46 +0000

great idea Jayant! Not nearly as hacky as my workaround.

By: jer

jer — Thu, 29 Apr 2010 06:56:14 +0000

@jayant: your code works great!

By: Jayant

Jayant — Mon, 22 Mar 2010 17:34:26 +0000

Has anyone tried?

- (void)viewWillDisappear:(BOOL)animated {
[mapView.layer removeAllAnimations];
}

By: Alexander Osipov

Alexander Osipov — Tue, 16 Feb 2010 18:50:46 +0000

Perfect article, allowed me to save same problem but a bit different way
My case was following: I leave screen with mapView, screen deallocs and in short after this (screen already destroyed) timer routine attempts to do this animation on deleted screen
setting mapview delegate to nil sure doesn’t help: timer routine is already scheduled

Solution: delay destruction of screen object exact the way you suggested
- (void)dealloc {

if(false) [super dealloc];
[super performSelector:@selector(dealloc) withObject:nil afterDelay:4.0f];
}