DZNEmptyDataSet
DZNEmptyDataSet copied to clipboard
Crashing while insert elements [[self tableView] endUpdates];
I'm getting these error while insert elements on my tableView, it's happens while insert elements using the main_threed_queqe, but your library always crash on these method:
void dzn_original_implementation(id self, SEL _cmd){ Class baseClass = dzn_baseClassToSwizzleForTarget(self); NSString *key = dzn_implementationKey(baseClass, _cmd);
NSDictionary *swizzleInfo = [_impLookupTable objectForKey:key];
NSValue *impValue = [swizzleInfo valueForKey:DZNSwizzleInfoPointerKey];
IMP impPointer = [impValue pointerValue];
// We then inject the additional implementation for reloading the empty dataset
// Doing it before calling the original implementation does update the 'isEmptyDataSetVisible' flag on time.
[self dzn_reloadEmptyDataSet];
// If found, call original implementation
if (impPointer) {
((void(*)(id,SEL))impPointer)(self,_cmd);
}
}
+1. Having the same issue with some users on Fabric. It's a rare one but it's out there.
+1
+1
+1
+1
+1
+1 @cbedoy will reload tableview entirely instead do insert get crash too? I got same issue and hard to reproduce and want to know if tableView reloadData
can be a workaround
+1
+1
+1
Well the problem still happen sometimes, but I didn't find any solution :(
Any update on this? Seems like a common issue. How are people solving it?
Any update on this issue? Facing same.
I have the same problem just in iOS 9+ and I don't have it in iOS 10.
We're still having on.
+1
+1
same issue
+1. please help me, thank you everybody.
For anyone still have this problem, I just solved this issue after hours investigation. The crash is not caused by this library actually. The crash is caused by a bug in iOS 10. And the bug has been fixed in iOS 10.3 and up. So no more crash for user with iOS 10.3 and up.
The REASON of the crash: If you are using UITableViewAutomaticDimension for your row height, and the height that returned in estimatedHeightForRowAt and heightForHeaderInSection methods are not precision, then calling method reloadData and endUpdates will leads an unexpected scrolling of your tableview, and this caused a shifting could either be up or down depends on the height you returned in estimatedHeightForRowAt and heightForHeaderInSection methods.
The SOLUTION: Instead of returning UITableViewAutomaticDimension or a random number in estimatedHeightForRowAt and heightForHeaderInSection methods, try to figure out a more precision height for your table view's row height and section header.
For anyone still have this problem, I just solved this issue after hours investigation. The crash is not caused by this library actually. The crash is caused by a bug in iOS 10. And the bug has been fixed in iOS 10.3 and up. So no more crash for user with iOS 10.3 and up.
The REASON of the crash: If you are using UITableViewAutomaticDimension for your row height, and the height that returned in estimatedHeightForRowAt and heightForHeaderInSection methods are not precision, then calling method reloadData and endUpdates will leads an unexpected scrolling of your tableview, and this caused a shifting could either be up or down depends on the height you returned in estimatedHeightForRowAt and heightForHeaderInSection methods.
The SOLUTION: Instead of returning UITableViewAutomaticDimension or a random number in estimatedHeightForRowAt and heightForHeaderInSection methods, try to figure out a more precision height for your table view's row height and section header.
but I give a precision heigh and also crash with the same reason.My secreen is delete all datas and do this [self.tableView deleteRowAtIndexPath:indexPath withRowAnimation:UITableViewRowAnimationAutomatic];
For anyone still have this problem, I just solved this issue after hours investigation. The crash is not caused by this library actually. The crash is caused by a bug in iOS 10. And the bug has been fixed in iOS 10.3 and up. So no more crash for user with iOS 10.3 and up. The REASON of the crash: If you are using UITableViewAutomaticDimension for your row height, and the height that returned in estimatedHeightForRowAt and heightForHeaderInSection methods are not precision, then calling method reloadData and endUpdates will leads an unexpected scrolling of your tableview, and this caused a shifting could either be up or down depends on the height you returned in estimatedHeightForRowAt and heightForHeaderInSection methods. The SOLUTION: Instead of returning UITableViewAutomaticDimension or a random number in estimatedHeightForRowAt and heightForHeaderInSection methods, try to figure out a more precision height for your table view's row height and section header.
but I give a precision heigh and also crash with the same reason.My secreen is delete all datas and do this [self.tableView deleteRowAtIndexPath:indexPath withRowAnimation:UITableViewRowAnimationAutomatic];
Could you confirm if this crash happens in iOS 10.3 and up as well?
I have the same problem on iOS 10.3.3