[TEALIUM SWIFT BUG]: Bad memory access crash

[hr147]

Your Environment
Fill out as appropriate.
iOS Version(s) [e.g. 12.1]: iOS 15 and above
Xcode version [Xcode> About Xcode e.g. 10.1 (10B61)]: xCode 15, 16
Swift version [e.g. 4.2]: 5.9
Tealium Swift library version [e.g. 1.6.7]: 2.14.0
Dependency manager [None/Carthage/CocoaPods]: SPM
Dependency manager version:

Describe the bug
We have been encountering random crashes in the TealiumDelegateProxy.handleContinueUserActivity(_:) method for a long time, as reported in Crashlytics. Unfortunately, we have been unable to reproduce the issue so far. Please find attached images of the stack trace for further investigation.

Title

Crash Stack Trace

Does a workaround exist?
it's randomly producible, We don't have its solution

To Reproduce
Steps to reproduce the behavior. If applicable, please attach sample code showing how to reproduce the bug. Remember to keep your Tealium account details private, and only post generic code. Additional code or crash logs may be shared with us privately on [email protected].

Unfortunately, we don't know the steps to reproduce.
...

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

[craigrouse]

@hr147 sorry you're experiencing this issue. We haven't had any other reports of this recently, so assume there may be something in your app that's triggering it. Looking at the call stack, I can see you have an implementation of the Google Utilities library's App Delegate Swizzler. We are also proxying some of the same methods in TealiumDelegateProxy.swift, and I suspect that there's a race condition somewhere between the 2 implementations that's causing the crash in certain circumstances.

There are potentially some areas we can try to make our code safer, which will hopefully prevent this from happening, so we'll look into this. If you want to solve the problem immediately, you can prevent our SDK from proxying by settings TealiumAutotrackingDeepLinkEnabled to NO in your Info.plist file. Once this is set, Tealium will no longer automatically gather information about deep links, which will prevent our QR code debugging feature from working if you're using that. To disable proxying while still tracking deep links, you'll need to call the handleDeepLink method on your Tealium instance.