Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Thread sanitizer issue #840

Open
woosiki-prestolabs opened this issue Oct 10, 2024 · 3 comments
Open

Thread sanitizer issue #840

woosiki-prestolabs opened this issue Oct 10, 2024 · 3 comments

Comments

@woosiki-prestolabs
Copy link

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.
스크린샷 2024-10-10 오전 12 08 17
@woosiki-prestolabs
Copy link
Author

Could you check this?

@Ayyanchira
Copy link
Member

Ayyanchira commented Oct 18, 2024

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
Copy link
Author

woosiki-prestolabs commented Oct 28, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants