How to reproduce:
1. Open the ‘TestHingeJointOniOS.zip' project
2. Open the ‘SampleScene’ scene
3. In the Hierarchy select the dropdown ‘floor’ menu
4. Delete the 'editorCreatedDoor’ GameObject
5. Build for iOS
6. Open the “Unity-iPhone.xcodeproj“ in Xcode
7. Build to a device
8. Open the app
9. Observe the console

Expected result: The app launch successfully
Actual result: The app crashes as soon as it launches with error ‘EXC_BAD_ACCESS’

Reproducible with: 2022.3.69f1, 6000.0.63f1, 6000.2.14f1, 6000.3.0f1 (d1870ce95baf), 6000.4.0a5, 6000.5.0a2

Reproducible environment: macOS 26.0.1 (M1 Max)
Not reproducible environment: No other environment tested

Reproducible with these devices:
VLNQA00416, iPhone 13 Pro (MLVA3ET/A), CPU:  Apple A15 Bionic, OS: 17.6.1
VLNQA00543, iPad mini 4 (WiFi) (MK9N2B/A), CPU: Apple A8, OS: 15.8.3
VLNQA00358, iPhone 12 (MGJ93ET/A), CPU: Apple A14 Bionic, OS: 26.0.1
VLNQA00632, iPhone 16e (MD1Q4QN/A), CPU: Apple A18 Pro, OS: 18.3
VLNQA00612, Samsung Galaxy S24 (SM-S921B), CPU: Exynos 2400, OS: Android 15

Workaround: Add a ‘RigidBody' component to the 'scriptedDoor’ GameObject

First few lines of the stack trace:
0x000000010b0771bc UnityFramework`Unity::Joint::AwakeFromLoad(AwakeFromLoadMode) + 84
0x000000010aec5840 UnityFramework`GameObject::FinalizeAddComponentInternal(Unity::Component, bool, AwakeFromLoadQueue) + 96
0x000000010aec58e0 UnityFramework`GameObject::AddComponentInternal(Unity::Component, bool, AwakeFromLoadQueue) + 92
0x000000010afae7b4 UnityFramework`AddComponentUnchecked(GameObject&, Unity::Type const, ScriptingClassPtr, MonoScript, core::basic_string<char, core::StringStorageDefault<char>>, AwakeFromLoadQueue) + 284
0x000000010afaf31c UnityFramework`AddComponentByPtr(GameObject&, Unity::Type const, MonoScript, ScriptingClassPtr, core::basic_string<char, core::StringStorageDefault<char>>, AwakeFromLoadQueue, char const, core::vector<Unity::Component, core::allocator<Unity::Component, 0ul>>) + 360