Thread sanitizer issue - Githubissues

Iterable / iterable-swift-sdk

Iterable's iOS SDK. Receive and track pushes to Iterable from your iOS app.

https://iterable.com/

MIT License

87 stars 74 forks source link

Thread sanitizer issue #840

Open woosiki-prestolabs opened 1 month ago

woosiki-prestolabs commented 1 month ago

I tried to check our project using Thread sanitizer and I found issue from IterableSDK.

version: 6.5.6
Location: Pending.swift:47
I just call IterableAPI.setUserId to update JWT one time, but access race is occurred inside of SDK.

woosiki-prestolabs commented 1 month ago

Could you check this?

Ayyanchira commented 1 month ago

Hi @woosiki-prestolabs , thanks for reporting this issue. We will definitely take a look. Meanwhile, would you be able to provide additional steps to reproduce this scenario:

Is the user already logged in? Or logging in first time? Is it reproducbile everytime just by calling setUserID with jwt or does it follow certain behavior? And also, have you tried IterableAuthDelegate to try to pass jwt instead of using setUserID?

Let us know. Thanks.

woosiki-prestolabs commented 1 month ago

Hi @Ayyanchira , it occurs only when a app just started and a user already logged in. In my environment, this issue is occurred 20% (3/15). Also we didn't pass jwt by IterableAuthDelegate when this issue is occurred. We send jwt using IterableAuthDelegate only jwt is already memory cached, but we don't use disk cache for this.