Crash on [AWSMQTTSession publishDataAtLeastOnce:onTopic:retain:onMessageIdResolved:] function

[09chen1998]

Describe the bug
Our app occasionally crashes, some of which occur after calling subscribeToTopic, some after calling publishData, and some during other operations.

To Reproduce
Steps to reproduce the behavior:
There is no fixed reproducibility procedure, and crashes occur at irregular intervals.

Code Snippet
Please provide a snippet of the code causing the issue or how you are using the service that has the bug.

Unique Configuration
If you are reporting an issue with a unique configuration or where configuration can make a difference in code execution (i.e. Cognito) please provide your configuration. Please make sure to obfuscate sensitive information from the configuration before posting.

Areas of the SDK you are using (AWSMobileClient, Cognito, Pinpoint, IoT, etc)?

Screenshots

Environment(please complete the following information):

• SDK Version: [2.37.0]
• Dependency Manager: [Cocoapods]
• Swift Version : [5.9.2]
• Xcode Version: [15.2 ]

Device Information (please complete the following information):

• Device: [iPhone8, iPhone13, iPhone13 pro max]
• iOS Version: [IOS 16.5, IOS 17.5.1, IOS 17.6.1]

Logs

``` ```

Could it be caused by multiple threads accessing the same resource?

[vincetran]

Thanks for your crash report, one of our team members will do some investigation on this as soon as possible

[09chen1998]

@vincetran that's newest screenshot when app crash:

[phantumcode]

@09chen1998 Instead of screenshots, can you provide a full crash log that includes the crashing thread along with all of the other running threads?

[09chen1998]

@phantumcode The complete crash log is the screenshot of the log I provided above. The latest screenshot I sent is not a crash in the production/test environment, so there is no complete log left. However, judging from the code execution sequence, it is caused by the same problem as the log under "Logs" I provided.

[phantumcode]

@09chen1998 A complete crashlog would include the stack trace of the thread with the crash as well as all of the running threads at the time of the crash. Having a full crash log is helpful in determining crashes caused by threading issues.