[__NSArrayM insertObject:atIndex:]: object cannot be nil

[iqraKhaliq]

Description
The app crashes on iOS with the following error message:
[__NSArrayM insertObject:atIndex:]: object cannot be nil

Expected Behavior
The app should handle null or undefined objects gracefully and not attempt to insert a nil object into an array.

Actual Behavior
When repeatedly moving between screens (e.g., navigating forward and then back), the app eventually crashes with the error above.

Environment
Platform: iOS
React Native Version: 0.80.2
iOS Version: iOS 18.3
Device: iPhone 16 Pro Simulator
Package version: 3.4.2

Steps to Reproduce

• Launch the app on an iOS device or simulator.
• Navigate from Screen A → Screen B.
• Go back to Screen A.
• Repeat the process a few times.

Observe that the app crashes with the message:
[__NSArrayM insertObject:atIndex:]: object cannot be nil

Crash Log / Stack Trace
*** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[__NSArrayM insertObject:atIndex:]: object cannot be nil'

Crash Video Link
https://drive.google.com/file/d/1orGmmZmEBDKJZhNSpQWhd1QLsAPN1F7Q/view?usp=sharing

[roggyboy]

Hi,

I encountered the same problem on iOS with Expo 53 and react-native-map-clustering 4.0.0.

I created a patch that worked for me, and I'm sharing it here in case you'd like to try it.

react-native-map-clustering+4.0.0.patch

I also had to add some patch logic to react-native-maps+1.20.1.patch where the original [__NSArrayM insertObject:atIndex:]: object cannot be nil' is thrown from.
This combo seems to be working as intended for me.

react-native-maps+1.20.1.patch

[Sweizeur]

Hey @roggyboy, thanks a lot for sharing your patches — they fixed the crash for me as well! 🙏

I'm on Expo SDK 54, react-native-maps 1.20.1, and react-native-map-clustering 4.0.0.

I did make two modifications I wanted to share back:

1. react-native-maps patch — Added nil guard for Apple Maps (AIRMap.m)

Your patch covers AIRGoogleMap.m for the nil check on insertObject:atIndex:, but since my app uses Apple Maps by default on iOS, the crash was actually happening in AIRMap.m. I added the same nil guard there:

// ios/AirMaps/AIRMap.m
- (void)insertReactSubview:(UIView *)subview atIndex:(NSInteger)atIndex {
  if (subview == nil) return;
  // ...
}

Without this, the [__NSArrayM insertObject:atIndex:]: object cannot be nil crash still occurs for anyone not using Google Maps as their provider.

2. react-native-map-clustering patch — Removed two-phase marker update in handleRegionChangeComplete

Your clustering patch uses a clear-then-readd approach on iOS in handleRegionChangeComplete:

updateMarkers([]);                     // phase 1: clear
requestAnimationFrame(() => {          // phase 2: re-add next frame
  updateMarkers(nextMarkers);
});

This prevents the crash, but it causes visible marker flickering on every map pan/zoom because there's always one empty frame between clearing and re-adding markers.

Since the native nil guards in react-native-maps are now handling the root cause (preventing nil insertions), this aggressive two-phase pattern is no longer needed in the region change handler. I simplified it to just:

updateMarkers(nextMarkers);

This keeps the crash fix (via the native patches) while eliminating the flicker. The initial useEffect still uses the two-phase approach for the first render, which is fine.

Hope this helps anyone else running into the same issue!

react-native-map-clustering+4.0.0.patch
react-native-maps+1.20.1.patch