I have two methods that toggle the right bar button items in a view controller's UINavigationItem. It's basically to show a search bar in the navigation bar when the search button is tapped, and to hide the search bar when the user executes a search
- (void)displaySearchUI
{
[self.mainNavigationController.topViewController.navigationItem setRightBarButtonItems:[self searchOpenItems] animated:YES];
[self.searchBar becomeFirstResponder];
}
- (void)dismissSearchUI
{
[self.mainNavigationController.topViewController.navigationItem setRightBarButtonItems:[self searchClosedItems] animated:YES];
}
- (NSArray *)searchClosedItems
{
return #[[self someCustomItem],
[self someOtherItem],
[self searchButtonItem],
];
}
- (NSArray *)searchOpenItems
{
return #[[self someCustomItem],
[self someOtherItem],
[self searchBarItem],
];
}
the item returned from searchButtonItem uses a UIBarButtonItem with an image, while the item returned from searchBarItem has a custom view of a UISearchBar. the other items in each are identical in each search state.
When I call displaySearchUI, the searchbar becoming the first responder opens a popover to show some search suggestions. When the popover is dismissed by the user, dismissSearchUI is called via the popoverControllerDidDismissPopover: delegate method. However at that point, often the app encounters a crash within UINavigationBar:
-[CALayer enumerateObjectsUsingBlock:]: unrecognized selector sent to instance 0x7de9ac80
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[CALayer enumerateObjectsUsingBlock:]: unrecognized selector sent to instance 0x7de9ac80'
*** First throw call stack:
(
0 CoreFoundation 0x056f0946 __exceptionPreprocess + 182
1 libobjc.A.dylib 0x05379a97 objc_exception_throw + 44
2 CoreFoundation 0x056f85c5 -[NSObject(NSObject) doesNotRecognizeSelector:] + 277
3 CoreFoundation 0x056413e7 ___forwarding___ + 1047
4 CoreFoundation 0x05640fae _CF_forwarding_prep_0 + 14
5 UIKit 0x03ba38aa -[UINavigationBar _setLeftViews:rightViews:] + 3774
6 UIKit 0x03b8f77e -[UINavigationItem updateNavigationBarButtonsAnimated:] + 186
7 UIKit 0x03b901a0 -[UINavigationItem setObject:forLeftRightKeyPath:animated:] + 600
8 UIKit 0x03b9100a -[UINavigationItem setRightBarButtonItems:animated:] + 104
9 MyApp 0x0028088b -[DisplayManager dismissSearchUI] + 283
I'm not sure exactly what could be happening here. It seems to happen whether or not setting the items is animated. It also only happens when the user taps outside the popover. If I programmatically dismiss the popover and call dismissSearchUI, there's no crash (I imagine due to the different order in which the animations occur, or due to some state differences in the UI when the user dismisses a popover vs a programmatic dismissal. I've tried to work around it by doing this:
#pragma mark - UIPopoverControllerDelegate
- (BOOL)popoverControllerShouldDismissPopover:(UIPopoverController *)popoverController
{
[self dismissSearchSuggestionsUI];
return NO;
}
- (void)dismissSearchSuggestionsUI
{
[self.popoverController dismissPopoverAnimated:YES];
[self.displayManager dismissSearchUI];
}
But I get an EXC_BAD_ACCESS crash instead here, (with a similar stack trace that leads me to believe it's the same issue, just a different symptom due to timing).
Has anyone encountered something like this, and is there a way to work around this without having to disable manual user popover dismissals altogether?
Bah, i figured it out right after posting. By ammending dismissSearchUI's method to do this:
- (void)dismissSearchUI
{
[self.searchBar resignFirstResponder]
[self.mainNavigationController.topViewController.navigationItem setRightBarButtonItems:[self searchClosedItems] animated:YES];
}
I resolved the issue. I figured that the search bar would resign its own first responder when the user executed a search, but that doesn't happen automatically when the user manually cancels the search which causes the bar button item it's in to be removed from the nav bar.
Related
In our app we have a UITableViewController that has a UISearchController:
searchController = [[UISearchController alloc] initWithSearchResultsController:nil];
self.searchController.searchResultsUpdater = self;
[self.searchController.searchBar sizeToFit];
self.tableView.tableHeaderView = self.searchController.searchBar;
self.showFooterView = YES;
self.searchController.delegate = self;
self.searchController.dimsBackgroundDuringPresentation = NO; // default is YES
self.searchController.searchBar.delegate = self;
self.definesPresentationContext = YES;
The table view controller is also a UISearchBarDelegate
and UISearchControllerDelegate.
#pragma mark - UISearchBarDelegate
- (void)searchBarSearchButtonClicked:(UISearchBar *)searchBar {
[searchBar resignFirstResponder];
}
- (void)searchBarCancelButtonClicked:(UISearchBar *)searchBar {
self.contacts = self.allContacts;
[self.tableView reloadData];
}
Now everything works as expected, but there are occasions when a user starts a search, types in a few characters in the search bar, results are returned, and the user cancels the search and then this happens:
Fatal Exception: NSInvalidArgumentException
-[_UIFullscreenPresentationController adaptivePresentationController]: unrecognized selector sent to instance 0x147c81ce0
Fatal Exception: NSInvalidArgumentException
0 CoreFoundation 0x1842b4f48 __exceptionPreprocess
1 libobjc.A.dylib 0x198d77f80 objc_exception_throw
2 CoreFoundation 0x1842bbc5c __methodDescriptionForSelector
3 CoreFoundation 0x1842b8c00 ___forwarding___
4 CoreFoundation 0x1841bccac _CF_forwarding_prep_0
5 UIKit 0x18a1ba084 -[UISearchController _searchPresentationController]
6 UIKit 0x189e7d10c -[_UISearchControllerTransplantSearchBarAnimator animateTransition:]
7 UIKit 0x189b9fa90 __56-[UIPresentationController runTransitionForCurrentState]_block_invoke
8 UIKit 0x189af856c _runAfterCACommitDeferredBlocks
9 UIKit 0x189b054bc _cleanUpAfterCAFlushAndRunDeferredBlocks
10 UIKit 0x189839984 _afterCACommitHandler
11 CoreFoundation 0x18426bbd0 __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__
12 CoreFoundation 0x184269974 __CFRunLoopDoObservers
13 CoreFoundation 0x184269da4 __CFRunLoopRun
14 CoreFoundation 0x184198ca0 CFRunLoopRunSpecific
15 GraphicsServices 0x18f3d4088 GSEventRunModal
16 UIKit 0x1898b0ffc UIApplicationMain
We have never been able to reproduce this error, although it gets reported by Fabric on production.
This problem looks similar to this: Selecting cell after search doesn't segue visually, but loads next view Swift Xcode but no real answer has been given there yet.
I have started looking into presentation controllers but we have no special functionality that would require setting up presentation controllers in a specific way.
Any ideas on how to fix this?
Thanks
I've faced the same problem on Swift.
The problem is Searchbarcontroller still hold the reference(delegate) of your ViewController.
So all you have to do is manually remove the reference when view dealloc or disappear
Something like this:
- (void)dealloc {
self.searchController.searchResultsUpdater = nil;
self.searchController.searchBar.delegate = nil;
self.searchController.delegate = nil;
self.searchController = nil;
}
Try cleaning all your references as given below.
-(void)dealloc{
if (_searchController) {
_searchController.searchResultsUpdater = nil;
_searchController.searchBar.delegate = nil;
_searchController.delegate = nil;
}
}
Utilize UISearchContainerViewController as Main ViewController and wrap your SearchController inside it.
A view controller that manages the presentation of search results in your interface.
Although you can present a search controller object modally, you should never push one onto a navigation controller’s stack or use one as a child of another container view controller. Instead, embed an instance of this class and let it manage the presentation of the search controller’s content.
https://developer.apple.com/documentation/uikit/uisearchcontainerviewcontroller
Installed Xcode 7.1 Beta and tested my app on iOS 9.0 and got below error. I went thorough different questions here.
I am using IIViewDeckController for left menu and PullRefreshTableViewController. In app delegate I register to different notification and give webservice call to get data for view controllers of VC1(Menu1) and VC2(Menu2), both inherits PullRefreshTableViewController. VC1 is displayed at first. When user navigates to VC2 the view gets loaded with data pulled but crashes with below exception.
*** Terminating app due to uncaught exception 'NSInternalInconsistencyException', reason: 'An instance 0x7fa8c541eaf0 of class UIView was deallocated while key value observers were still registered with it. Current observation info: (
Context: 0x0, Property: 0x7fa8c1d1b470>
)'
*** First throw call stack:
(
0 CoreFoundation 0x0000000110d7df65 __exceptionPreprocess + 165
1 libobjc.A.dylib 0x00000001107f5deb objc_exception_throw + 48
2 CoreFoundation 0x0000000110d7de9d +[NSException raise:format:] + 205
3 Foundation 0x000000010f6528c1 NSKVODeallocate + 294
4 libobjc.A.dylib 0x000000011080a0b8 _ZN12_GLOBAL__N_119AutoreleasePoolPage3popEPv + 488
5 CoreFoundation 0x0000000110c6b956 _CFAutoreleasePoolPop + 22
6 CoreFoundation 0x0000000110c9f8d1 __CFRunLoopRun + 2081
7 CoreFoundation 0x0000000110c9ee28 CFRunLoopRunSpecific + 488
8 GraphicsServices 0x00000001134e4ad2 GSEventRunModal + 161
9 UIKit 0x000000010e12eca1 UIApplicationMain + 171
10 SeeMyRadiology 0x000000010d0d507e SeeMyRadiology + 16510
11 libdyld.dylib 0x000000011126992d start + 1
)
libc++abi.dylib: terminating with uncaught exception of type NSException
**NOTE:**Same code works on iPad without error
- (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions
{
UIStoryboard* mainStoryboard = [UIStoryboard storyboardWithName:#"MainStoryboard" bundle: nil];
UIViewController* menuController = [mainStoryboard instantiateViewControllerWithIdentifier:#"LeftSideMenu"];
UINavigationController* navigationController = (UINavigationController *) self.window.rootViewController;
self.viewDeckController = [[IIViewDeckController alloc] initWithCenterViewController:navigationController leftViewController:menuController rightViewController:nil];
self.window.rootViewController = self.viewDeckController;
}
OR
https://github.com/edgecase/ECSlidingViewController
Just in case unable to solve problem.
If your table is reloaded it's possible that you loose your views, I mean, they are deallocated. If there are some connections beetwen deallocated views and values somewhere it causes the crash. You need to stop observing values before deallocating in order to avoid crash. Check this scenerio.
This worked for me.
The problem was while pushing view over the IIViewDeckController.
AppDelegate *appDelegate = (AppDelegate *)[[UIApplication sharedApplication] delegate];
UINavigationController *centerController = [[UINavigationController alloc] initWithRootViewController:appDelegate.viewController];
[appDelegate.viewDeckController closeLeftViewBouncing:^(IIViewDeckController *controller)
{
appDelegate.viewDeckController.centerController = centerController;
}];
Thank you your input guys. :)
I have a situation where I am trying to resolve these Crashlytics issues and I have this crash log
Thread : Crashed: com.apple.main-thread
0 libobjc.A.dylib 0x34217f46 objc_msgSend + 5
1 UIKit 0x29a2d5a3 -[UIWebView webView:decidePolicyForNavigationAction:request:frame:decisionListener:] + 182
2 CoreFoundation 0x2630cad4 __invoking___ + 68
3 CoreFoundation 0x26239645 -[NSInvocation invoke] + 300
4 CoreFoundation 0x2623d0c7 -[NSInvocation invokeWithTarget:] + 50
5 WebKitLegacy 0x326d9261 -[_WebSafeForwarder forwardInvocation:] + 224
6 CoreFoundation 0x2630b62f ___forwarding___ + 354
7 CoreFoundation 0x2623d008 _CF_forwarding_prep_0 + 24
8 CoreFoundation 0x2630cad4 __invoking___ + 68
9 CoreFoundation 0x26239645 -[NSInvocation invoke] + 300
10 WebCore 0x31c02729 HandleDelegateSource(void*) + 100
11 CoreFoundation 0x262cefbf __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 14
12 CoreFoundation 0x262ce461 __CFRunLoopDoSources0 + 364
13 CoreFoundation 0x262cca35 __CFRunLoopRun + 772
14 CoreFoundation 0x2621a3b1 CFRunLoopRunSpecific + 476
15 CoreFoundation 0x2621a1c3 CFRunLoopRunInMode + 106
16 GraphicsServices 0x2d801201 GSEventRunModal + 136
17 UIKit 0x2988443d UIApplicationMain + 1440
18 abc 0x0030dcd7 main (main.m:14)
I can understand that its some callback on webview delegate and bad excess has occurred, so to rectify this I handled the delegates via
[self.webview stopLoading];
self.webview.delegate =nil;
in all the classes, yet I can see this crash. Can you enlighten me what's possibly going wrong and some approach to rectify this?
The following might be the case here
The user is presented a screen with UIWebView
The UIViewController sets self as the delegate Web page starts downloading
The User quits screen
UIViewController gets deallocated UIWebView finishes loading and sends I am finished loading message to its delegate
or
some other delegate method gets called when the webview object is no more.i.e dangling pointer effect
1.Always make sure you stop loading the webView and remove the delegate before leaving the view
Before releasing an instance of UIWebView for which you have set a
delegate, you must first set its delegate property to nil. This can
be done, in your dealloc method
Here is the reference
// If ARC is used
- (void)dealloc {
[_webView setDelegate:nil];
[_webView stopLoading];
}
// If ARC is not used
- (void)dealloc {
[webView setDelegate:nil];
[webView stopLoading];
[webView release];
[super dealloc];
}
// ARC - Before iOS6 as its deprecated from it.
- (void)viewWillUnload {
[webView setDelegate:nil];
[webView stopLoading];
}
2.Make sure you are not stopLoading and setDelegate to nil in viewWillDisappear
if the ViewController is a child of a another ViewController, u can
trigger the removal of the ViewController's view from the parent
ViewController's view with an animation. At the same time, u can
remove the ViewController from its parent and nil out its reference.
at this point ViewController will be nil and viewWillDisappear
will never be called, meaning the WebView delegate will never be
cleaned up
Use dealloc and ensure that your WebView is always cleaned up.
3.Make sure you set the ContentOffset of the subviews of webview to CGPointZero without animation
In iPad in some versions while webview is scrolling if you close the parent
viewcontroller without setting ContentOffset to CGPointZero this
kind of problems will come
so its better to you call the following code of in parent viewcontroller before closing it
for (id subview in webView.subviews){
if ([[subview class] isSubclassOfClass: [UIScrollView class]]){
[subview setContentOffset:CGPointZero animated:NO];
}
}
Hope this helps.Feel free to ask your doubts.
4.Generally speaking You should not embed UIWebView objects in UIScrollView objects. If you do so, unexpected behavior can result because touch events for the two objects can be mixed up and wrongly handled.
Here is the reference
Try disabling your UIWebView's scrolling behaviour before the ViewController deallocs it
for (id subview in webView.subviews){
if ([[subview class] isSubclassOfClass: [UIScrollView class]]){
[subview setContentOffset:CGPointZero animated:NO];
}
}
p.s. Dipen Chudasama's approach is correct, according to Apple's documentation, you should really set the delegate property to nil before releasing the webview, assuming you have released the webview correctly inside dealloc function but not viewWillDisappear
UIWebViews delegate uses assign and not weak. So you need to nullify the delegate when the webView's controller gets deallocated.
Example:
- (void)dealloc
{
self.webview.delegate =nil;
}
Are you adding a web view within your subclass of a web view? Generally that's the problem and if so, changing the superclass to a UIView would solve the problem.
Use visa versa means first nil your delegate and then after stop loading web view may be help you.
like this.
[_webView setDelegate:nil];
[_webView stopLoading];
As per apple document : Important Before releasing an instance of UIWebView for which you have set a delegate, you must first set its delegate property to nil.
Use [listener use] instead, to tell your UIWebView to handle clicked URL.
-(void)webView:(WebView *)webView decidePolicyForNavigationAction:(NSDictionary *)actionInformation request:(NSURLRequest *)request frame:(WebFrame *)frame decisionListener:(id )listener
{
[listener use]
}
Since upgrading to XCode 5/iOS 7, I'm getting the following error when calling a function which is supposed to present the Redlaser SDK barcodepickercontroller:
Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: 'Application tried to present a nil modal view controller on target .'
* First throw call stack:
(
0 CoreFoundation 0x02ef25e4 __exceptionPreprocess + 180
1 libobjc.A.dylib 0x028dd8b6 objc_exception_throw + 44
2 UIKit 0x006e817a -[UIViewControllerpresentViewController:withTransition:completion:] + 4879
3 UIKit 0x006e8caf -[UIViewController presentViewController:animated:completion:] + 130
4 UIKit 0x006e8cef -[UIViewController presentModalViewController:animated:] + 56
5 Extinguishers 0x0000b703 -[LoginViewController scanPressed] + 1299
And here's my method which causes it:
-(IBAction) scanPressed
{
if (overlayController.parentPicker == nil)
{
BarcodePickerController * picker = [[BarcodePickerController alloc] init];
[picker setOverlay:overlayController];
[picker setDelegate:self];
// Initialize with portrait mode as default
picker.orientation = UIImageOrientationUp;
// The active scanning region size is set in OverlayController.m
}
// Update barcode on/off settings
[overlayController.parentPicker setScanUPCE:YES];
[overlayController.parentPicker setScanEAN8:YES];
[overlayController.parentPicker setScanEAN13:YES];
//[overlayController.parentPicker setScanSTICKY:YES];
//[overlayController.parentPicker setScanQRCODE:YES];
[overlayController.parentPicker setScanCODE128:YES];
[overlayController.parentPicker setScanCODE39:YES];
[overlayController.parentPicker setScanITF:YES];
// Data matrix decoding does not work very well so it is disabled for now
[overlayController.parentPicker setScanDATAMATRIX:NO];
// hide the status bar
[[UIApplication sharedApplication] setStatusBarHidden:YES];
// Show the scanner overlay - THIS LINE CAUSES THE CRASH
[self presentModalViewController:overlayController.parentPicker animated:TRUE];
}
I've also tried upgrading to the latest version of the Redlaser SDK, and the error is still the same. I did not have this problem before switching to iOS 7 as the base SDK.
The only thing I can think of is that picker(the parent) might be going out of scope and getting deallocated. Put a test right before the buggy line to check if the parent still exists: if(overlayController.parentPicker == nil) NSLog(#"Parent is nil");
If it really is nil (like your original error is saying), try declaring picker before that first if statement.
BarcodePickerController *picker;
if(overlayController.parentPicker == nil)
{
picker = [[BarcodePickerController alloc] init];
//...
The child might only have a weak pointer to the parent, so you may need to declare the parent as a #property or somewhere where it won't be deallocated before your viewController is popped off the stack.
I've gotten several crash reports related to a UICollectionView in iOS 7. I'm not able to consistently recreate this crash.
Exception Type: SIGSEGV
Exception Codes: SEGV_ACCERR at 0x91c4392b
Crashed Thread: 0
Application Specific Information:
*** Terminating app due to uncaught exception '', reason: ''
Thread 0 Crashed:
0 libobjc.A.dylib 0x39dd2b26 objc_msgSend + 6
1 UIKit 0x31fd5eef -[UICollectionView cellForItemAtIndexPath:] + 111
2 UIKit 0x32060bfd -[UICollectionView _unhighlightItemAtIndexPath:animated:notifyDelegate:] + 149
3 UIKit 0x32383947 -[UICollectionView _unhighlightAllItems] + 151
4 UIKit 0x3205f9fb -[UICollectionView touchesBegan:withEvent:] + 367
5 UIKit 0x31fcb101 forwardTouchMethod + 233
6 UIKit 0x31fcb101 forwardTouchMethod + 233
7 UIKit 0x31e3be4b _UIGestureRecognizerUpdate + 5523
8 UIKit 0x31e73c41 -[UIWindow _sendGesturesForEvent:] + 773
9 UIKit 0x31e735e7 -[UIWindow sendEvent:] + 667
10 UIKit 0x31e48a25 -[UIApplication sendEvent:] + 197
11 UIKit 0x31e47221 _UIApplicationHandleEventQueue + 7097
12 CoreFoundation 0x2f69e18b __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 15
13 CoreFoundation 0x2f69d6e1 __CFRunLoopDoSources0 + 341
14 CoreFoundation 0x2f69be4f __CFRunLoopRun + 623
15 CoreFoundation 0x2f606ce7 CFRunLoopRunSpecific + 523
16 CoreFoundation 0x2f606acb CFRunLoopRunInMode + 107
17 GraphicsServices 0x342f4283 GSEventRunModal + 139
18 UIKit 0x31ea8a41 UIApplicationMain + 1137
19 JackThreadsIpad 0x000922b7 main (main.m:16)
The UICollectionViewCells in the app share a common superclass that manages highlighting. When the cell is highlighted the alpha changes.
- (void)setHighlighted:(BOOL)highlighted {
[super setHighlighted:highlighted];
if (highlighted) {
self.alpha = 0.8;
} else {
self.alpha = 1.0;
}
}
Could calling [super setHighlighted:highlighted] cause a crash like this? The app was compiled and submitted with XCode 4 and is only happening on iOS 7. Any other suggestions to figure out where this is happening. Thanks for your help.
Edit:
I was able to catch this in the debugger, but it still is not consistently reproducible. The crash is:
[NSIndexPath section] message sent to deallocated instance XXXXXXXX
If you are calling reloadData while the user is dragging the view, that might be the reason.
I had crashes related to this with similar crash reports and "fixed" the issue by delaying the reloadData call until after the user has finished scrolling the view. E.g. create a wrapped method instead of calling reloadData directly.
- (void)updateData {
if (self.collectionView.isTracking) {
self.updateDataOnScrollingEnded = YES;
} else {
[self.collectionView reloadData];
}
}
Then when scrolling ends, call the updateData method (if needed) from the scroll view's delegate methods.
- (void)scrollViewDidEndDragging:(UIScrollView *)scrollView willDecelerate:(BOOL)decelerate
{
if (!decelerate) {
[self scrollViewStopped:scrollView];
}
}
- (void)scrollViewDidEndDecelerating:(UIScrollView *)scrollView
{
[self scrollViewStopped:scrollView];
}
- (void)scrollViewStopped:(UIScrollView *)scrollView
{
if (self.updateDataOnScrollingEnded) {
[self updateData];
self.updateDataOnScrollingEnded = NO;
}
}
My guess is that there is a weak reference to the highlighted cell's indexPath somewhere inside of the collectionView, and that calling reload will dealloc that indexPath. When the collectionView then tries to unhighlight the cell, it crashes.
EDIT:
As mentioned in comments below, this "solution" has some flaws. While investigating the issue further, it seems that in my case the problem had to do with multiple reloadData calls being queued on the main thread during the dragging of the collection view. When there was only one reloadData call, everything was fine, but whenever there was more than one – crash!
Since I always had exactly one section in my collectionView i replaced the reloadData call with
reloadSections:[NSIndexSet indexSetWithIndex:0]
However, this causes the cells to quickly fade out and back in again which I avoided with the following method (it would probably be better off as a category on the collection view)
- (void)reloadCollectionView:(UICollectionView *)collectionView animated:(BOOL)animated
{
[UIView setAnimationsEnabled:animated];
[collectionView performBatchUpdates:^{
[collectionView reloadSections:[NSIndexSet indexSetWithIndex:0]];
} completion:^(BOOL finished) {
[UIView setAnimationsEnabled:YES];
}];
}
So far, this has worked well for me and it also allows for the data to actually be updated while scrolling.
Not sure after identifying only this piece of code. But as crash signal (SIGSEGV) seems due to memory leak. You just go to your Xcode setting and inside Edit Scheme jsut enable Zombie option and then try to reproduce your crash. It will show you the controller class name of method or any crash related information inside console of Xcode.
And also just try to modify you condition below:-
- (void)setHighlighted:(BOOL)highlighted {
//just comment this line or write this line to the below and check
//[super setHighlighted:highlighted];
if (highlighted) {
self.alpha = 0.8;
} else {
self.alpha = 1.0;
}
[super setHighlighted:highlighted];
}
I had this problem, though slightly different crash. Fixed by holding off any reloadData until the highlight is cleared. While toostn's suggestion would fix the issue, it is useful to be able to reloadData whilst scrolling, but doesn't make much sense when highlighting - as you have your finger on a cell.
implement the following UICollectionViewDelegate methods:
- (BOOL)collectionView:(UICollectionView *)collectionView shouldHighlightItemAtIndexPath:(NSIndexPath *)indexPath {
self.allowReload = NO;
return YES;
}
- (void)collectionView:(UICollectionView *)collectionView didUnhighlightItemAtIndexPath:(NSIndexPath *)indexPath {
self.allowReload = YES;
[self reloadIfNecessary]; // calls reloadData if it is necessary to do so!
}
I also had this crash in _unhighlightAllItems in a collection view where I used a long press recognizer that changes the state of cells (but not their number) and then called [collectionView reloadData]. In my case, the solution from #toostn (using performBatchUpdates) works great.
I also found that using reloadItemsAtIndexPaths: instead of reloadData also avoids the crash.