Crash with Fabric/New Architecture in 11.0.0-alpha

[JamieScanlon]

Describe and reproduce the Bug

I am seeing crash reports from New Relic. Stack Trace:

CoreFoundation
__exceptionPreprocess (CoreFoundation)
libobjc.A.dylib
objc_exception_throw (libobjc.A.dylib)
CoreFoundation
-[__NSArrayM insertObject:atIndex:] (CoreFoundation)
MapQuest
-[MLRNMapView insertReactSubview:atIndex:] (MLRNMapView.m:0)
MapQuest
RCTLegacyViewManagerInteropComponentView.mm line 252 in -[RCTLegacyViewManagerInteropComponentView finalizeUpdates:] (RCTLegacyViewManagerInteropComponentView.mm:252)
MapQuest
std::__1::__function::__func<-[RCTMountingManager performTransaction:]::$_1, std::__1::allocator<-[RCTMountingManager performTransaction:]::$_1>, void (facebook::react::MountingTransaction const&, facebook::react::SurfaceTelemetry const&)>::operator()(facebook::react::MountingTransaction const&, facebook::react::SurfaceTelemetry const&) (RCTMountingManager.mm:0)
MapQuest
TelemetryController.cpp line 40 in facebook::react::TelemetryController::pullTransaction(std::__1::function<void (facebook::react::MountingTransaction const&, facebook::react::SurfaceTelemetry const&)> const&, std::__1::function<void (facebook::react::MountingTransaction const&, facebook::react::SurfaceTelemetry const&)> const&, std::__1::function<void (facebook::react::MountingTransaction const&, facebook::react::SurfaceTelemetry const&)> const&) const (TelemetryController.cpp:40)
MapQuest
function.h line 397 in -[RCTMountingManager performTransaction:] (function.h:397)
MapQuest
RCTMountingManager.mm line 247 in -[RCTMountingManager initiateTransaction:] (RCTMountingManager.mm:247)
libdispatch.dylib
_dispatch_call_block_and_release (libdispatch.dylib)
libdispatch.dylib
_dispatch_client_callout (libdispatch.dylib)
libdispatch.dylib
_dispatch_main_queue_drain.cold.5 (libdispatch.dylib)
libdispatch.dylib
_dispatch_main_queue_drain (libdispatch.dylib)
libdispatch.dylib
_dispatch_main_queue_callback_4CF (libdispatch.dylib)

When googling this issue I saw that the react-native-maps library seemed to have a very similar issue

@maplibre/maplibre-react-native Version

11.0.0-alpha.4

Which platforms does this occur on?

iOS Device

Which frameworks does this occur on?

Expo

Which architectures does this occur on?

New Architecture

Environment

expo-env-info 2.0.7 environment info:
    System:
      OS: macOS 15.6.1
      Shell: 5.9 - /bin/zsh
    Binaries:
      Node: 22.14.0 - ~/.asdf/installs/nodejs/22.14.0/bin/node
      Yarn: 1.22.22 - ~/.asdf/shims/yarn
      npm: 10.9.2 - ~/.asdf/installs/nodejs/22.14.0/bin/npm
    Managers:
      CocoaPods: 1.16.2 - /Users/jamie.scanlon/.asdf/shims/pod
    SDKs:
      iOS SDK:
        Platforms: DriverKit 24.5, iOS 18.5, macOS 15.5, tvOS 18.5, visionOS 2.5, watchOS 11.5
    IDEs:
      Android Studio: 2024.2 AI-242.23726.103.2422.12816248
      Xcode: 16.4/16F6 - /usr/bin/xcodebuild
    npmPackages:
      expo: 53.0.18 => 53.0.18 
      react: 19.0.0 => 19.0.0 
      react-dom: 19.0.0 => 19.0.0 
      react-native: 0.79.6 => 0.79.6 
      react-native-web: ^0.20.0 => 0.20.0 
    npmGlobalPackages:
      eas-cli: 16.10.1
    Expo Workflow: bare