From dbda739b625945d92a65e9c29d99dba62b3eac00 Mon Sep 17 00:00:00 2001
From: Fabio Milano <fabiomilano@meta.com>
Date: Fri, 19 May 2023 13:40:51 -0700
Subject: [PATCH] Log critical assert

Summary: Use `IGFailure` to log critical issues

Differential Revision:
D46029468

Privacy Context Container: L1132866

fbshipit-source-id: f642a50310e7a7d7a80e01ba61d382bb9a794496
---
 Source/IGListKit/Internal/IGListBatchUpdateTransaction.m | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Source/IGListKit/Internal/IGListBatchUpdateTransaction.m b/Source/IGListKit/Internal/IGListBatchUpdateTransaction.m
index a71926d4..5bd1d7b6 100644
--- a/Source/IGListKit/Internal/IGListBatchUpdateTransaction.m
+++ b/Source/IGListKit/Internal/IGListBatchUpdateTransaction.m
@@ -231,6 +231,7 @@ willPerformBatchUpdatesWithCollectionView:self.collectionView
             /// with our product team to properly fix their data source changes outside of the -performBatchUpdatesBlock:
             /// IGLisKit processed a new being as an assert that requires investigation,
             /// since it will be processed as invalid data source state that needs a reload.
+            IGFailure(@"The data source returned an invalid number of sections and rows due to updates applied outside of the performBatchUpdates block. This will cause a crash.");
             [self begin];
             return;
         } else {