[BUG]Crash with preloadPaywalls method

[artemshyianov-art]

New issue checklist

• I have reviewed the README and documentation
• I have searched existing issues and this is not a duplicate
• I have attempted to reproduce the issue and include an example project.

General information

• Superwall version: 4.14.0
• iOS version(s): 26.5
• CocoaPods/Carthage version (if applicable):
• Xcode version:
• Devices/Simulators affected:
• Reproducible in the demo project? (Yes/No):
• Related issues:

Describe the bug

On Firebase Crash reports we see crash:

ConfigManager.swift:622
specialized NativeSet.filter(:) + 622

imote.tv.remote.control_issue_7160cb94db9e9fb918a7daa28ee4413a_crash_session_d6f5a21f375a4b40b06a1f7d9117231f_DNE_0_v2_stacktrace.txt

[linear]

SW-5404

[artemshyianov-art]

[artemshyianov-art]

The crash EXC_BAD_ACCESS KERN_INVALID_ADDRESS at ConfigManager.swift:622 is caused by a threading concurrency bug (Race Condition) inside the SDK.The Cause: While a background global queue (com.apple.root.default-qos.cooperative) is executing a data-filtering loop (_NativeSet.filter), another thread is mutating or clearing that same list of objects.The Result: Swift tries to decrement the reference count (doDecrementSlow) on an object that has already been deallocated from a separate thread, attempts to read from a null memory address (0x0000000000000000), and crashes immediately.The Trigger: Frame line 6 (Superwall.gamepadValueChanged) reveals that this memory breakdown is specifically triggered by Superwall's integrated game controller tracking features.

[artemshyianov-art]

@superwall-team @yusuftor Please let me know how to resolve this crash. It happens inside of Superwall SDK