Data Races in QNUserPropertiesManager

[Ralph1300]

We recently experienced some data races in the QNUserPropertiesManager class. We are using Xcode 15 and have the Thread Sanitizer activated for debug builds.

See the attached screenshot for an example. This is usually triggered right after the app start, where we call Qonversion.initWithConfig() from the main thread in the AppDelegate.

As far as I can tell issues are related to

@property (nonatomic, assign, readwrite) BOOL sendingScheduled;
@property (nonatomic, assign, readwrite) BOOL updatingCurrently;

Both properties are read/written to on multiple occasions - sometimes updatingCurrently is wrapped in a synchronization block, but not always. For sendingScheduled this is missing completely.

Thanks for looking into this, and let me know if you need more input!

[suriksarkisyan]

Hi, @Ralph1300
Thanks for the details. We will look deeper into this issue and come back with an update!

[github-actions]

This issue is stale because it has been open 7 days with no activity. Remove stale label or comment or this will be closed in 5 days.

[github-actions]

This issue was closed because it has been stalled for 5 days with no activity.

[Ralph1300]

@suriksarkisyan any news? Issue got closed automatically now.

[suriksarkisyan]

@suriksarkisyan any news? Issue got closed automatically now.

We reopened this issue. It's still in progress. We will try to fix it in the next release. And could you please give me some examples of usage of our properties code?